New movies not added to library anymore and metadata fetch no longer working

[spicer]

Hi!

since yesterday my Jf server (10.10.5) refuses to actually add movies to the library anymore. The logs show nothing unusual - the fprobe commands and Finished ibrary Sync, yet the movies just will not appear. Also, trying to Identify movies doesn't work anymore, only empty results or neverending spinner.
I really don't want to delete and readd the library since I put a lot of work into the metadata etc. Short of that, I did everything I could think of: had Jf create new *.xml files in /config, ran all scheduled tasks, rescanned the library numerous times with every option, went through all my plugins, reconfigured or disabled or enabled them and by now I probably messed things up even more. Everything is working fine as usual except what I described.
How to proceed? Thanks

[TheDreadPirate]

Can you run this command on the host machine? Then share the output.

Code:

curl -vvv https://image.tmdb.org/t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg -o /tmp/futurama.jpg

[spicer]

Can you run this command on the host machine?  Then share the output.

Code:

curl -vvv https://image.tmdb.org/t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg -o /tmp/futurama.jpg

Code:

root@xxx:/# curl -vvv https://image.tmdb.org/t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg -o /tmp/futurama.jpg
  % Total    % Received % Xferd  Average Speed  Time    Time    Time  Current
                                Dload  Upload  Total  Spent    Left  Speed
  0    0    0    0    0    0      0      0 --:--:-- --:--:-- --:--:--    0*  Trying 79.127.216.111:443...
* Connected to image.tmdb.org (79.127.216.111) port 443 (#0)
* ALPN: offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [19 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [3966 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=image.tmdb.org
*  start date: Jan  2 14:14:24 2025 GMT
*  expire date: Apr  2 14:14:23 2025 GMT
*  subjectAltName: host "image.tmdb.org" matched cert's "image.tmdb.org"
*  issuer: C=US; O=Let's Encrypt; CN=R10
*  SSL certificate verify ok.
} [5 bytes data]
* using HTTP/2
* h2h3 [:method: GET]
* h2h3 [:path: /t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg]
* h2h3 [:scheme: https]
* h2h3 [:authority: image.tmdb.org]
* h2h3 [user-agent: curl/7.88.1]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x564af648dce0)
} [5 bytes data]
> GET /t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg HTTP/2
> Host: image.tmdb.org
> user-agent: curl/7.88.1
> accept: */*
>
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [265 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [265 bytes data]
* old SSL session ID is stale, removing
{ [5 bytes data]
< HTTP/2 200
< date: Tue, 28 Jan 2025 17:15:07 GMT
< content-type: image/jpeg
< content-length: 50330
< server: BunnyCDN-DE1-752
< cdn-pullzone: 775336
< cdn-uid: 29af4e0e-bcbd-4fcb-8635-74ddc38a1ebf
< cdn-requestcountrycode: DE
< cache-control: public, max-age=31919000
< etag: "6272f494-c49a"
< last-modified: Wed, 04 May 2022 21:48:04 GMT
< cdn-storageserver: NY-346
< cdn-requestpullsuccess: True
< cdn-fileserver: 266
< perma-cache: HIT
< cdn-proxyver: 1.04
< cdn-requestpullcode: 200
< cdn-cachedat: 08/28/2024 20:02:11
< cdn-edgestorageid: 864
< cdn-status: 200
< cdn-requesttime: 0
< cdn-requestid: 859055e558351721c7c3490200b9a909
< cdn-cache: HIT
< accept-ranges: bytes
<
{ [14480 bytes data]
100 50330  100 50330    0    0  413k      0 --:--:-- --:--:-- --:--:--  416k
* Connection #0 to host image.tmdb.org left intact

[TheDreadPirate]

And this command.

Code:

nslookup api.tmdb.org

And can you share your full jellyfin log via privatebin.net?

[spicer]

And this command.

Code:

nslookup api.tmdb.org

And can you share your full jellyfin log via privatebin.net?

Code:

nslookup

seems to not be available in this particular container sorry

Log from starting the container and then me doing a normal movie library scan while the server talks to Kodi on my TV:  https://privatebin.net/?0d35ed449f28ea55#9NFZ7JE2y58PSHsfHxB7wj1tMc311N89yCEsyuc9VT2G

and thanks btw!

[TheDreadPirate]

It looks like you are using host networking, so running nslookup on the host should show the same result as running it in the container.

But I think the problem is your folder structure. Nesting movies folders is not supported. Your library is pointed at /data/movies, but then there are sub-folders for each letter. That additional folder layer A) is added on to the query Jellyfin sends to TMDB/TVDB and B) can break functionality like support for movie extras.

Your options are to have the movie folders all directly under /data/movies or add each "letter" folder to the library settings.

[spicer]

add each "letter" folder to the library settings.

That's precisely what I am doing -- the movies library has individual folders A..Z added.

Code:

nslookup api.tmdb.org

on the container host:

Code:

root@XXX:~# nslookup api.tmdb.org
Server:        192.168.178.1
Address:        192.168.178.1#53

Non-authoritative answer:
Name:  api.tmdb.org
Address: 18.66.102.75

IMHO I don't think this is a networking problem (except some apis somewhere are totally borked currently? or something like that?) or a filesystem problem, since I changed nothing in the underlying infrastructure hard- or software wise (the container gets auto updates tho but I am pretty certain everything worked fine even after the last update to .5) - I added movies into the monitored folder A..Z, they appear a short time later in the Jf library, I mess with the metadata and images, done. Not anymore🤷‍♂️

Is there an option to remove and clear caches and data of all non-default plugins?

[TheDreadPirate]

According to the last log you shared your library is pointed at /data/movies. And not each of the letter sub-folders inside it.

And it looks like within each letter folder, most of the movies are not in their own folder.

You need to, either, add each letter as a library root instead of /data/movies (you would need to remove this folder before adding each letter) or move all the files up to /data/movies and, preferrably but not required, put each movie in their own folder.

[spicer]

Ah sh*t you're right of course, that was my music lib that had the A..Z folder.. d'oh.. brain completely cooked by troubleshooting this, sorry.

But how could that suddenly produce that problems since I am using this setup for some years now?

But what is even more interesting is that when I checked the library settings just now for what folders are there I discovered ... the movies are now there, but some twice, some with only their filenames. Identification seems to work. Which makes me happy because it somewhat works again but I have even less idea of what is going on here. Glitch in the matrix and I just wait it out or do you have any more ideas?
Thanks

[TheDreadPirate]

I'd imagine a lot of the metadata is incomplete, some may be misidentified, and some may not be present at all. Any changes in scan behavior can be attributed to changes in how Jellyfin parses file and folder names with each new version. My experience, and I'd say the experience of most other users, is that Jellyfin has become less tolerant of unsupported folder structures as time goes on.

Regardless, my suggestions to improve identification consistency is in my last post.