Yesterday, 06:41 PM
(2024-07-29, 03:05 AM)TheDreadPirate Wrote: Is your container using bridge or host networking?
Sorry for the EPIC late reply, the docker is using "bridge" networking. Jellyfin crashed again yesterday with the same "no route to host", every other service on the server is working fine (including all networking). What i can tell, is that the user (remote) simply powered off his Nvidia Shield (ungraceful shutdown of jellyfin client i guess) and that pretty much killed the server whilst watching a TV Show. Docker is 10.10.7 and client is 0.18.11.
It happens so infrequently, hopefully fixed in the upcoming release!
Code:
[2025-08-08 22:08:17.082 +00:00] [WRN] [83] Emby.Server.Implementations.HttpServer.WebSocketConnection: WS "192.168.1.1" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake."
[2025-08-08 22:08:17.084 +00:00] [INF] [83] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" closed
[2025-08-08 22:08:17.082 +00:00] [ERR] [24] Microsoft.AspNetCore.Server.Kestrel: Unexpected exception in TimingPipeFlusher.FlushAsync.
System.Net.Sockets.SocketException (113): No route to host