mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: 404 on update #5688
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JasonHorkles on GitHub (May 12, 2024).
Please describe your bug
After upgrading Jellyfin, visiting the site now gives a 404 error (https://domain/web/)
I've tried in multiple browsers, flushing dns cache, and enabling developer mode in Cloudflare but it's still happening.
Also, the PC and Roku apps seem to work fine but not the Android one.
Reproduction Steps
apt update && apt full-upgrade -yJellyfin Version
10.8.13
if other:
10.9.0
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
Failed to load resource: the server responded with a status of 404 ()
Please attach any screenshots here
No response
Code of Conduct
@bioblatt commented on GitHub (May 12, 2024):
Same issue for me using Firefox or Chromium, the Jellyfin Media Player (1.9.1-1) on Linux Mint works. My Android app (2.6.1) is also unable to connect (cache deleted and reinstalled).
@gnattu commented on GitHub (May 12, 2024):
So all of you are having issue specific to the android app right?
@JasonHorkles commented on GitHub (May 12, 2024):
It happens in browsers on any device too
@gnattu commented on GitHub (May 12, 2024):
Post your nginx config please, it is more likely a configuration issue.
To rule out that, directly access jellyfin server with the 8096 port and see if that works
@JasonHorkles commented on GitHub (May 12, 2024):
I had already restored a previous backup, but I can try duplicating the server and updating it again
Also I have CloudFlare redirecting to port 476 since I already have 443 in use
@gnattu commented on GitHub (May 12, 2024):
Ahh, yeah. Please remove this block:
It won't work with 10.9 now. It is a hack we used for 10.8 and you no longer need this. We have to update our documentation for this.
@JasonHorkles commented on GitHub (May 12, 2024):
I'll give it a shot, thanks!
@JasonHorkles commented on GitHub (May 12, 2024):
That works, can't believe it was that simple lol
Thank you so much!