2024-07-11, 06:33 PM
2024-07-11, 06:34 PM
(This post was last modified: 2024-07-11, 06:35 PM by TheDreadPirate.)
Can you show me screenshots of how the library is configured?
Also, enable debug logging, restart jellyfin and rescan with "replace all". In the container, /config/config/logging.default.json set the 3 logs levels at the top to "Debug". Code: { The log will be MUCH larger. If it doesn't fit into pastebin, zip the log file and attach it to a forum post.
2024-07-11, 07:11 PM
(2024-07-11, 06:34 PM)TheDreadPirate Wrote: Can you show me screenshots of how the library is configured? Here are the logs: https://pastebin.com/0FxWhHz9 And the screenshot of library config : https://cloud.chapp.dev/s/QzKCeqKreCg3pSn
2024-07-11, 07:27 PM
(This post was last modified: 2024-07-11, 07:27 PM by TheDreadPirate.)
I compared your output with mine when DEBUG was enabled and I'm not seeing any of the TMDB responses for images and metadata. Can you turn off IPv6 in Dashboard > Networking? Also, for testing, can you switch the library's country/region to the United States and rescan?
2024-07-11, 07:37 PM
(2024-07-11, 07:27 PM)TheDreadPirate Wrote: I compared your output with mine when DEBUG was enabled and I'm not seeing any of the TMDB responses for images and metadata. Can you turn off IPv6 in Dashboard > Networking? Also, for testing, can you switch the library's country/region to the United States and rescan? It's already disable...
2024-07-11, 07:49 PM
Interesting. I keep seeing this in the log.
Code: [INF] [156] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "2001:cafe:42::1" closed Normally if the container wasn't able to reach TMDB due to some networking issue, Jellyfin would log that TMDB is unreachable. But I don't see that here. From within the container, are you able to ping api.tmdb.org?
2024-07-11, 09:49 PM
(This post was last modified: 2024-07-11, 10:03 PM by ZoThyx. Edited 1 time in total.)
(2024-07-11, 07:49 PM)TheDreadPirate Wrote: Interesting. I keep seeing this in the log. Indeed, my k3s cluster uses DualStack for IP which means that the Jellyfin container has an IPv4 and an IPv6, although I restrict communication with it... I tried enabling IPv6 in the Jellyfin dashboard and scanning to see if it would work like this, but no luck. So I've disabled IPv6, but I've got the impression that there are still IPv6 requests... The ping command is not installed in the jellyfin image, but with Curl, I get this result: Code: I have no name!@dep-jellyfin-595d87557-27zsp:/$ curl api.tmdb.org
2024-07-11, 10:45 PM
Is there any way to turn off IPv6 entirely for just the Jellyfin container?
2024-07-11, 10:47 PM
2024-07-12, 08:29 AM
|
|
|