WebSocket Issue Preventing Homepage from Loading

[nxl4]

Ever since the 10.10.3-20 update, I've been unable to load the Jellyfin homepage through the web console or Android apps on multiple devices. When I try to load the homepage, it will spin for several minutes, until the homepage ultimately fails to load in its entirety. Logs consistently show this pattern, with a WebSocketManager request being initiated, and followed by ForceKeepAlive messages to the inactive WebSockets:

Code:

[2024-12-18 12:32:30.557 -05:00] [INF] [82] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.68.119" request
[2024-12-18 12:34:38.665 -05:00] [INF] [75] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
[2024-12-18 12:40:26.987 -05:00] [INF] [25] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
[2024-12-18 12:41:02.660 -05:00] [INF] [42] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.

I completely deleted and re-installed Jellyfin on my NAS (along with all of the dependencies), and additionally deleted and re-installed clients on my Android devices as well. However, the issue persists. I'm running Jellyfin on my Synology NAS through the SynoCommunity package (I'm not using Docker, because my Synology model doesn't support Docker). I'd never had this type of issue prior to the upgrade, and I'm not sure what else to try in terms of troubleshooting or remediation.

Any ideas on other things to try?

[TheDreadPirate]

Can you share your full log via pastebin? And which networking mode is the container using?

[nxl4]

Can you share your full log via pastebin?

Sure, I put everything from the 2024-12-18 and 2024-12-19 log files in this paste.

And which networking mode is the container using?

There are no containers in the process at all (my NAS doesn't support containers).

[TheDreadPirate]

Does the NAS use a non-standard port for Jellyfin?

[nxl4]

Does the NAS use a non-standard port for Jellyfin?

Nope. Everything's served over port 8096. I can get to the homepage, it just doesn't load entirely. All of my libraries will start to load, and then stall somewhere around the halfway point. Once the homepage loading stalls, I typically can't click into any of the libraries or play any files either. This is the same behavior on the web and both Android apps.