mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: After Update to 10.8.11 cant login anymore #5105
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 @solisinvictum on GitHub (Sep 25, 2023).
Please describe your bug
After Updating to 10.8.11, its impossible to login anymore.
If visiting the web ui, following is shown:
All clients cant login anymore (Smartphones, FireTV Sticks, etc).
After restarting the server, only for 1-2 minutes it is possible to log in. After that time, the Wizards shows up again.
Jellyfin Version
10.8.z
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@cvium commented on GitHub (Sep 25, 2023):
Have you tried clearing the browser cache?
@solisinvictum commented on GitHub (Sep 25, 2023):
Yes. tried other browsers and OS'es too. But this seems to be a bigger problem, because like said Apps like Jellyfin for FireTV, Kodi, Smartphones etc cant log in anymore. I just rolled back a VM Image prior the update (10.8.10) because users were waiting thats works again.
@solisinvictum commented on GitHub (Sep 26, 2023):
Ok, sry. My Issue. I totaly forgot the VM is running arch not debian.
After little investigation, this seems to be the problem:
https://github.com/jellyfin/jellyfin/issues/10236
https://bugs.archlinux.org/task/79712
https://aur.archlinux.org/packages/jellyfin-server
Im unsure if i should do this: https://aur.archlinux.org/packages/jellyfin-server#comment-934026
Or wait for fixes from upstream?
@kauron commented on GitHub (Oct 2, 2023):
I'm having the same issue in ArchLinux, after updating from
jellyfin-{server,web}-bin10.8.10 (from the aur) tojellyfin-{server,web}10.8.11 from the official repositories.@solisinvictum can you remember what the action recommended by the aur comment you linked was? The package was deleted from the AUR and I can't find the comment (there's no recent archive on the wayback machine...)
@solisinvictum commented on GitHub (Oct 3, 2023):
@kauron: Yeah there was written, to move to old config locations etc to the new one. Sry, didnt reminder anymore which paths exactly.
Because this is only a small instance for me and family, i stopped after a hour working on it with trial & error, and simply removed jellyfin, purged any config, and reinstalled jellyfin complete new from repo and configured anything new.
@sevenrats commented on GitHub (Dec 12, 2023):
looks like this bug is resolved in release and has linked workarounds. anybody have a problem with me closing this issue?
@stegl commented on GitHub (Dec 16, 2023):
i have the same problem updating from jellyfin_10.8.11_windows-x64 to jellyfin_10.8.13_windows-x64
it looks like all data from older version was deleted
@jellyfin-bot commented on GitHub (Apr 15, 2024):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@jellyfin-bot commented on GitHub (May 7, 2024):
This issue was closed due to inactivity.