jellyfin / jellyfin-web

Web Client for Jellyfin
https://jellyfin.org
GNU General Public License v2.0
2.4k stars 1.28k forks source link

Loading Webpage "hangs" until reload with CTRL + SHIFT + R (without cache) #5494

Closed DaRealHansForSure closed 1 month ago

DaRealHansForSure commented 6 months ago

Describe The Bug Every now and then, when you call up the Web UI, it gets stuck at the Jellyfin logo.

In the Network tab you can see that it is no longer loaded as the main chunk. However, if you call up the page again with CTRL + SHIFT + R, everything loads normally.

This happens from time to time. Disable Cache in the Network Developer does not help either.

Version 10.8.z rlease of jellyfin-web works as expected.

Steps To Reproduce

  1. Start instance with web 10.9.1
  2. Finish the first setup
  3. Login
  4. Wait some time, and call the jellyfin web page again

Expected Behavior Loading fully Web UI

Logs No Errorlogs appears in Browser.

Screenshots bla bla2

System (please complete the following information):

DaRealHansForSure commented 6 months ago

I have just made some additional observations.

When this error occurs, I see activity on the “” element in the DOM in the Dev Tools, but nothing is effectively changed visually (too fast)

ItzzCode commented 6 months ago

Also experiencing this issue on Firefox 125.0.3 for Linux Mint, using the same version. It only began occurring when I upgraded.

hjpaul7 commented 6 months ago

+1 also seeing this

dmitrylyzo commented 6 months ago

bla

That's the old logo. Do you use a reverse proxy (you on Windows, but still)? Some proxies can cache a lot.

ItzzCode commented 6 months ago

Not the OP, but it occured to me even though I connected directly to the Jellyfin Server without a reverse proxy (inadvisable I know, but eh).

DaRealHansForSure commented 6 months ago

Sometimes it runs behind a reverse Proxy, but Caching is disabled, and also after a fresh reload it don't work.

Same occours sometimes lokal without Proxy

cthulhuz commented 6 months ago

I have experienced the same issue. Had to downgrade to 10.8 due to it.

DaRealHansForSure commented 6 months ago

I experienced this bug already in a early state of 10.9 Web as Information

buzzkillingtonne commented 6 months ago

I've also been experiencing this issue.

Server running on Debian 12, accessing from Firefox and Chrome on both Windows and EndeavourOS. When it happens again I'll need to test accessing it without the NGINX reverse proxy, however restarting the service on the server seems to fix the issue temporarily.

ramonskie commented 6 months ago

also experiencing this issue since 10.9.1 browser: brave, firefox

jellyfin is hosted on docker within a synology nas behind the synology.me proxy

solution was for me to force renew cache CTRL + SHIFT + R

Ryah commented 6 months ago

Also experiencing this

Hosted on Docker. Hangs on everything I try it on. Edge, Chrome, Floorp, and Android.

Can only access it with Jellyfin-vue frontend or Jellyfin Media Player.

Found no solution so far. Even clearing cache and cookies didn't help.

Nevermind, this was due to some jellyfin modifications I did to main.*.bundle.js and completely forgot about. Deleting those mounts and repulling the docker image fixed it for me without clearing any data.

thornbill commented 6 months ago

Please check the browser console for errors

jellyfin-bot commented 2 months ago

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.