Jellyfin Forum
Web Browser Client Not Loading - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Web Browser Client Not Loading (/t-web-browser-client-not-loading)



Web Browser Client Not Loading - galact1c - 2024-11-27

First thing to note is I prefer to watch Jellyfin in Chrome/web browser, versus the standalone JMP media player. I have tried 4 web browsers and they all exhibit the below issue.
The roku client and JMP standalone still work correctly.
I updated from 10.9.8 to 10.10.2 on 11/17/24.
I am on Windows 10.
Things had been fine for the last 10 days besides the fact that some plugins stated they required a restart and weren't functioning correctly.
Another thing that may be helpful is at the time, dashboard said that client and web version were both 10.10.2, but after restarting and the issue began, JMP standalone says client is 10.10.2 and web is 10.10.3.
Tonight I decided to simply click the restart button from the dashboard page in attempt to fix the plugins.
After restarting, the site/web browser loaded the Jellyfin logo screen, but stayed on a black screen after that. 
Cleared all cache, cookies, and site settings in attempt to fix it, but it still won't load anything beyond the Jellyfin logo screen.
Followed various similar threads from here and github, namely the steps for issue #688 on github involving deleting the JMP and J M P folders from appdata which not only wasn't the solution, it also prevented JMP standalone from loading, so I've since restored the folders.
Looked through logs for errors, but not sure what to look for and logs are too long to post the entirety into paste-bin, but I've pasted the last portion and can make multiple paste-bin posts if necessary. 

LOGS: https://pastebin.com/3R7W8eWi


RE: Web Browser Client Not Loading - galact1c - 2024-11-27

Update:
I downloaded the JMP standalone app onto a secondary PC and the issue that occurs in web browser followed it.
I copied the JMP and J M P folders in Appdata from the main PC where JMP standalone is working and pasted them over the existing files on the secondary PC, which has allowed JMP standalone to work on the secondary PC, but the browser issue still exists.


RE: Web Browser Client Not Loading - TheDreadPirate - 2024-11-27

Can you share the contents of C:\ProgramData\Jellyfin\Server\config\network.xml? It looks like you have it configured to only use the local loopback interface.

Also, you should consider removing the ThemerrDB plugin as it is no longer maintained.

https://github.com/LizardByte/ThemerrDB/


RE: Web Browser Client Not Loading - galact1c - 2024-11-28

<?xml version="1.0" encoding="utf-8"?>
<NetworkConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<BaseUrl />
<EnableHttps>false</EnableHttps>
<RequireHttps>false</RequireHttps>
<InternalHttpPort>8096</InternalHttpPort>
<InternalHttpsPort>8920</InternalHttpsPort>
<PublicHttpPort>8096</PublicHttpPort>
<PublicHttpsPort>8920</PublicHttpsPort>
<AutoDiscovery>true</AutoDiscovery>
<EnableUPnP>false</EnableUPnP>
<EnableIPv4>true</EnableIPv4>
<EnableIPv6>false</EnableIPv6>
<EnableRemoteAccess>true</EnableRemoteAccess>
<LocalNetworkSubnets />
<LocalNetworkAddresses>
<string>0.0.0.0</string>
</LocalNetworkAddresses>
<KnownProxies />
<IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces>
<VirtualInterfaceNames>
<string>veth</string>
</VirtualInterfaceNames>
<EnablePublishedServerUriByRequest>false</EnablePublishedServerUriByRequest>
<PublishedServerUriBySubnet />
<RemoteIPFilter>
<string>100.64.0.0/10</string>
</RemoteIPFilter>
<IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist>
</NetworkConfiguration>

My Jellyfin\Server\config\network.xml was in a different root folder than C:\ProgramData\, if that makes a difference.


RE: Web Browser Client Not Loading - TheDreadPirate - 2024-11-28

You have a remote IP filter and you added 0.0.0.0 to the bind configuration.

Change your network.xml to the following.

Code:
<?xml version="1.0" encoding="utf-8"?>
<NetworkConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<BaseUrl />
<EnableHttps>false</EnableHttps>
<RequireHttps>false</RequireHttps>
<InternalHttpPort>8096</InternalHttpPort>
<InternalHttpsPort>8920</InternalHttpsPort>
<PublicHttpPort>8096</PublicHttpPort>
<PublicHttpsPort>8920</PublicHttpsPort>
<AutoDiscovery>true</AutoDiscovery>
<EnableUPnP>false</EnableUPnP>
<EnableIPv4>true</EnableIPv4>
<EnableIPv6>false</EnableIPv6>
<EnableRemoteAccess>true</EnableRemoteAccess>
<LocalNetworkSubnets />
<LocalNetworkAddresses />
<KnownProxies />
<IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces>
<VirtualInterfaceNames>
<string>veth</string>
</VirtualInterfaceNames>
<EnablePublishedServerUriByRequest>false</EnablePublishedServerUriByRequest>
<PublishedServerUriBySubnet />
<RemoteIPFilter />
<IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist>
</NetworkConfiguration>