mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Can't do library scan if TMDB is unreachable #8008
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Gr3q on GitHub (Jan 10, 2026).
Description of the bug
Some of the content here is outdated, see my comment
TMDB started timing started some time this week, I noticed it happening yesterday, every call to it times out after 100 seconds. I have more metadata providers enabled but they are not tried at all after the timeout (TMDB is the first in my list).
Because I see no related issues I suspect it's my system specifically, in that case I need help tracking down the cause.Things I tried/checked
Disabling TMDB for metadata works for identifying and getting metadata, disabling it for images doesn't make a difference for searching for images, it still hangs forever.
Opening the TMDB plugin configuration also doesn't work ( times out getting the config from TMDB).
I also tried using the TMDB API from my server, I can make curl requests to it.
Reproduction steps
I don't know, there were no changes to usage or configuration
What is the current bug behavior?
Image search, metadata search and identifying times out and none of the other metadata providers are tried after.
What is the expected correct behavior?
Jellyfin Server version
10.11.5
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.11.5
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@Gr3q commented on GitHub (Jan 10, 2026):
Related to https://github.com/jellyfin/jellyfin/issues/15785, IPv6 routing to TMDB doesn't work (at least from my server). The problem doesn't seem to be on my end because other ipv6 domains are resolved and accessible with curl with IPv6.
I will keep this open and rename the issue because I don't think Jellyfin should not be able to scan if TMDB doesn't work:
curls approach could be adopted? - "ibcurl resolves the hostname to the set of addresses it resolves to. Typically this means asking for both IPv4 and IPv6 addresses and there may be a whole set of those returned to libcurl. That set of addresses is then tried until one works, or it returns failure.". As far as I know HTTPClient does this, maybe it doesn't work with timeouts (the server just not responding)?For now I had to disable IPv6 on my server completely to so new media can be identified.
@Gr3q commented on GitHub (Jan 11, 2026):
Based on https://github.com/jellyfin/jellyfin/issues/12899 I should move this to the TMDBlib repo
@Gr3q commented on GitHub (Jan 11, 2026):
Turns out I shouldn't move this there, reopened.