Android TV no longer connects

[Swarfega]

I'm not sure what's triggered this but my Android TV no longer connects to my Jellyfin server. I have various LG TV's and an Android Phone which all work fine. Jellyfin sits behind Caddy.

Logs are as follows:

Code:

:34:07.110 +00:00] [WRN] [52] Emby.Server.Implementations.HttpServer.WebSocketConnection: WS "192.168.44.1" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake."
[2025-02-09 19:34:07.111 +00:00] [WRN] [17] Emby.Server.Implementations.HttpServer.WebSocketConnection: WS "192.168.44.1" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake."
[2025-02-09 19:34:07.114 +00:00] [INF] [52] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.44.1" closed
[2025-02-09 19:34:07.120 +00:00] [ERR] [45] Jellyfin.Api.WebSocketListeners.SessionInfoWebSocketListener: Error sending web socket message Sessions
System.Net.WebSockets.WebSocketException (0x80004005): The WebSocket is in an invalid state ('Aborted') for this operation. Valid states are: 'Open, CloseReceived'
  at System.Net.WebSockets.ManagedWebSocket.SendAsync(ReadOnlyMemory`1 buffer, WebSocketMessageType messageType, WebSocketMessageFlags messageFlags, CancellationToken cancellationToken)
--- End of stack trace from previous location ---
  at MediaBrowser.Controller.Net.BasePeriodicWebSocketListener`2.SendDataInternal(TReturnDataType data, ValueTuple`3 tuple)
[2025-02-09 19:34:07.265 +00:00] [INF] [17] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.44.1" closed
[2025-02-09 19:34:09.413 +00:00] [INF] [17] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.44.1" request

Version 0.18.4 client
10.10.5 of Jellyfin
Any ideas?

[Swarfega]

I think the issue is Certificate or TLS related. The TV is from 2015 and not had a firmware update in years.

I've managed to workaround the issue by pointing the client to the local IP of Jellyfin instead of via Caddy and it's connected.

[TheDreadPirate]

Depending on which CA your cert is signed by it is quite possible the TV doesn't trust the certificate.

https://letsencrypt.org/certificates/#root-cas

The X2 root CA was stood up in 2020. Depending on when your TV last received an update, it probably doesn't trust that CA.

Without a firmware update I'm not sure there is much you can do besides what you already did. AFAIK, there is no easy way to side load certificates to the trust store.

One thing you can explore is changing things around in caddy to provide your clients a cross signed certificate chain. Cross signed means that X1 will sign off on certs generated by X2. The link above includes links to download the cross signed certs for the root and intermediate CAs. LE's X1 root authority should still be trusted by TV and a cross signed certificate chain may allow your TV to trust your certificate.