mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
User logins are being corrupted intermittently #7867
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 @admitguy on GitHub (Dec 4, 2025).
Description of the bug
On version 10.11.3 and 10.11.4, I’ve noticed multiple users on my server being unable to logon with their credentials intermittently. This happens across all connected apps as well (e.g. jellyseerr). I was baffled for a while, and determined if I log in as an admin and update any setting on the user (library access, permissions, etc.) the issue resolves itself. I have also verified it’s not a password issue, because I have been able to regain access for an account without modifying the password at all. The bigger issue is i’ve been locked out of my admin account twice and was almost unable to recover.
I’m running Jellyfin via docker container and restarting the container didn’t help at all.
Reproduction steps
What is the current bug behavior?
Unable to login with correct credentials
What is the expected correct behavior?
Login works.
Jellyfin Server version
10.11.3
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.11.4
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@Raul824 commented on GitHub (Dec 9, 2025):
Would like to add more details and logs to this same error, I have been observing.
I think some cleanup task is corrupting the user instead of cleaning up the old sessions its corrupting the user.
Below are the sequence of events.
Below are the logs when tried step 2 and 3.
@hal-shin commented on GitHub (Feb 3, 2026):
I also get this issue, it's happened thrice so far. Debugging with AI, I've narrowed it down to bad database state. Running the following fixes the problem for me:
For whatever reason, it appears that the write-ahead logs and the shared memory file seems to get corrupted.
@theguymadmax commented on GitHub (Feb 3, 2026):
We are aware of the but problem, but haven't tracked down the cause. This closed thread https://github.com/jellyfin/jellyfin/issues/14367 also had some discussion. Restarting Jellyfin usually solves the issue.