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.
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?
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
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>openresty</center>
</body>
</html>