mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
[Issue]: Metadata fetch timeout - IPv6 connectivity broken #6108
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 @Johnny-Ich on GitHub (Jul 11, 2024).
Please describe your bug
When I try to fetch metadata, TheMovieDb and The Open Movie Database always times out.
also see -> https://github.com/jellyfin/jellyfin/issues/9438
Reproduction Steps
ping6 google.deand ping6jellyfin.serverJellyfin Version
10.9.0
if other:
Version: 10.9.7
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@felix920506 commented on GitHub (Jul 11, 2024):
cc @Shadowghost
@Shadowghost commented on GitHub (Jul 12, 2024):
This will need fixing in the plugins I think
@mharj commented on GitHub (Oct 12, 2024):
Looks like this works ok if running on Windows with IPv6 enabled (at least on versions 10.8.11 and 10.9.9), but some reason on docker container (in real Linux) it's not working and causing many issues even on scanning files. Docker image gets nicely list of ipv6 addresses for TheMovieDb api and curl does correcty redirect when tried on endpoint, so network and dns looks to working ok inside of container.
@Arcturuss commented on GitHub (Oct 28, 2024):
it really does not. got same error on Windows with ipv6 enabled and Jellyfin 10.9.11 and 10.10.0.
if you can not reach TMDB over ipv6 (in my case, the ping fails), then Jellyfin can not either.
@Titaniumtown commented on GitHub (Nov 9, 2024):
I can reproduce this bug even with ipv6 is disabled in jellyfin. Had to disable ipv6 on linux system-wide to get jellyfin to work.
Related: https://github.com/jellyfin/jellyfin/issues/8518
@Shadowghost commented on GitHub (Nov 10, 2024):
I think the proper fix would be to implement happy eyeballs for the tmdb plugin's http client. Since we use a library (nowadays maintained by the jellyfin team too), we should make it possible to use the httpclient which already implements it and is provided by Jellyfin.
@Titaniumtown commented on GitHub (Nov 10, 2024):
Is there a way to disable ipv6 for jellyfin specifically? The settings in jellyfin does nothing. Can it be disabled per-process on linux?
@Titaniumtown commented on GitHub (Dec 4, 2024):
This seems to be a result of a broken IPv6 system config. For example, my fix:
71d2bb0cb3After this, connectivity works.
@Shadowghost commented on GitHub (Dec 4, 2024):
Yes, this is usually the case. To handle this kind of issues, the default http client in Jellyfin uses HappyEyeballs to do a greaceful fallback to IPv4 (see #8598). But the TMDb library we are using uses a different HTTP client which does not implement this fallback
@jellyfin-bot commented on GitHub (Apr 4, 2025):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@wolfy1339 commented on GitHub (Apr 4, 2025):
Not stale. Issue should be moved to the appropriate repository and fixed there
@jellyfin-bot commented on GitHub (Aug 3, 2025):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@LeGmask commented on GitHub (Oct 27, 2025):
not stale, I can reproduce
@Kaz0na commented on GitHub (Dec 14, 2025):
Can confirm this issues still persists. Running Jellyfin in a Rootless Podman Container on CachyOS. With IPv6 enabled on the OS level Jellyfin fails to retrieve metadata due to a timeout. If I disable IPv6 completely on the OS level metadata retrieval works succesfully.
As an aside this same issue also occurs when just installing jellyfin natively instead of running it in a container.
@tonibgd commented on GitHub (Dec 16, 2025):
Can confirm the issue as well. Running rootless podman container on Arch.
Only works If I disable IPv6 on the OS level.
@tonibgd commented on GitHub (Dec 16, 2025):
I figured out a workaround for podman:
podman runcommand by adding--network jellyfin-networkVerify you are using IPv4 by checking your public IP:
jellyfin:curlcommand to check your public IPYou should now see your public IPv4 IP from within the container where before you would see your public IPv6 IP.
Running the
curlcommand outside the container should still return your public IPv6 IP.@Kaz0na commented on GitHub (Dec 19, 2025):
Just want to say that this worked like a charm!
@Gr3q commented on GitHub (Jan 11, 2026):
Another person with this issue, most likely my problem is temporary ISP routing issues to TMDB. https://github.com/jellyfin/jellyfin/issues/15989
I will add my comments from my own issue - which I probably should close - that I think would need to be changed to make this problem less impactful as it is now
@Shadowghost commented on GitHub (Jan 11, 2026):
Image proviers are configured separately to metadata providers in the library screen
Should be handled with https://github.com/jellyfin/TMDbLib/pull/551 but somebody would need to test it
@Gr3q commented on GitHub (Jan 13, 2026):
I know, I disabled TMDB for that too. Images will load, after the timeout (so 100secs by default) event if TMDB is disabled for it. A bug in Jellyfin most likely (tested this by adjusting the timeout for the TMDB provider)
On that branch are you using
HappyEyeballsCallbackfile for anything at all? How should I use that branch in jellyfin?and it doesn't seem to make a difference. my branch
@Shadowghost commented on GitHub (Jan 13, 2026):
You can just remove the dependency altogether and add a direct package reference to your local TMDbLib Source code to
MediaBrowser.Providers.csproj:And seems like my last rebase lost the actual usage of the HappyEyeballs callback. Should be fixed now.
@Gr3q commented on GitHub (Jan 13, 2026):
I can confirm that your branch works. Scanning is a bit slow to start off but there are enough issues with the current release around scanning so I'm going to ignore that.
My crude logic I added in jellyfin on the other hand...it just crashes jellyfin on some image downloads
@afeedhshaji commented on GitHub (Feb 1, 2026):
I ran into the same error and had to disable ipv6 to get it to work.