2025-01-24, 12:34 AM
(This post was last modified: 2025-01-24, 01:10 AM by olevelo. Edited 1 time in total.)
TMDB stopped working all of a sudden, either when adding new media, or going to Identify manually. I get a timeout in the logs. Found several threads about this and all of the solutions involved disabling IPv6. I tried this, and it did indeed work. However it's not a long-term solution for me, because my ISP uses CGNAT and so I only have IPv6 for in-bound connections. I could potentially disable IPv6 on just the Jellyfin docker container, but I'm not sure what issues that would cause. But I don't see why I should need to when it worked fine until today (literally was fine yesterday). Surely there's some other solution?
Edit: Did a little more investigation. I can't ping the IPv6 address that api.tmdb.org is resolving to. However, on a remote server I have, I can, and I noticed it has a different address it's resolving. That address I can ping! First time I've seen that. So it seems to not be a Jellyfin specific problem...but also not sure how to fix it. Again, it wasn't an issue yesterday or ever before (not sure if the IPv6 address changed recently, but using Google DNS).
Edit: Did a little more investigation. I can't ping the IPv6 address that api.tmdb.org is resolving to. However, on a remote server I have, I can, and I noticed it has a different address it's resolving. That address I can ping! First time I've seen that. So it seems to not be a Jellyfin specific problem...but also not sure how to fix it. Again, it wasn't an issue yesterday or ever before (not sure if the IPv6 address changed recently, but using Google DNS).