Homepage will load forever when opening web client on host with no network connected

[codenius]

Describe The Bug
When running Jellyfin server on a Windows machine you can't access the homepage of the web UI (loading spinner forever) while not being connected to a network. Although, loading finishes successfully as soon as network is connected (and also when enabling personal hotspot).

You can search, stream media, view favourites and change any settings while you're not connected to a network, only the homepage doesn't load.

Steps To Reproduce

1. Setup Jellyfin (portable in my case), confirm firewall exception for any network type
2. Disconnect all network (disable WiFi, remove Ethernet cable, disable Personal Hotspot: ipconfig shouldn't show any IP addresses)
3. Start Jellyfin
4. Open Jellyfin web UI in the browser (http://localhost:8096) on the same device

Expected Behavior
Homepage loads as it does when the machine is connected to network, i.e. media tiles appear.

Ligitimate Usecase
Using a laptop running a Jellyfin instance to stream on the go without network connection.

Logs
No conspicuous logs in browsers developer console or Jellyfin logs.

System (please complete the following information):

• Platform: Windows
• Browser: Vivaldi, Microsoft Edge
• Jellyfin Version: 10.9.2
• Network settings set to the defaults

[kenthieme]

I did some testing and the issue appears to be present as of the 10.9.0 release. 10.8.13 does not have the issue.

[codenius]

That's useful insight. Maybe one can find the problematic PR or commit by disabling single changes in network implemented in 10.9.0 one at a time and checking if that removes the issue.

Might be caused due to #3655, based on what I found by taking a quick look on changes for 10.9.0.

[willismonroe]

I just downgraded to 10.9.4 (from 10.9.6) and the web client loaded fine.

[jellyfin-bot]

Hi, it seems like your issue report has the following item(s) that need to be addressed:

• This bug report was not filed using the issue template.

This is an automated message, currently under testing. Please file an issue here if you encounter any problems.

[swiftbird07]

Any updates on this? The main reason I use Jellyfin is so I can watch stuff when the internet is down which is now impossible

[swiftbird07]

Btw this also affects the latest Docker build not just Windows

[Jason-Barratt]

I had the same issue with the latest docker image & the LG WebOS app. If I restricted access to the outside internet (via DNS configuration) the home screen wouldn't load. If I enabled access, the home screen would load.

After a lot of restarts to try and find the issue I used the search function and tried to select a show. Shows flickered between blurry thumbnails/default blank icons.
My TV notified me that the app was using a lot of memory, closed the app and switched off the TV. Now, magically, after restarting again, everything works without issue.

[10:43:25] [INF] [28] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 192.168.0.84 request
[10:44:43] [INF] [16] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
[10:44:55] [INF] [16] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
[10:45:07] [INF] [16] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
[10:45:07] [INF] [16] Emby.Server.Implementations.Session.SessionWebSocketListener: Lost 1 WebSockets.
[10:45:11] [INF] [36] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 192.168.0.84 closed
[10:45:55] [INF] [35] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 192.168.0.84 request
[10:46:23] [INF] [32] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 192.168.0.84 closed
[10:46:30] [INF] [27] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 192.168.0.84 request

I have no idea why my LGTV forcing Jellyfin to quit worked but my restarting of jellyfin app/docker image/TV didn't.

[felix920506]

@Jason-Barratt you likely have a different issue.

[gnattu]

https://tanstack.com/query/v4/docs/framework/react/guides/network-mode

This is due to the web query framework will pause all requests until a valid network connection is available.