Replies: 2 comments 4 replies
-
It does use the same user ehen updating token but im not sure why yours did that. Could be a little db issue. You could try one of two things. Restore from a backup (assuming you restored) or edit sqlite and change your new user to owner and remove old owner |
Beta Was this translation helpful? Give feedback.
3 replies
-
Just wanted to share that I've run into the same issue. Seems that with the last update (from 1.2 to 1.4) it created another user with the same sync issues shared by @MrMarble. As I wasn't bothered about my request history too much I did a quick re-install. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have both jellyfin and jellyseerr running on docker, somehow (maybe during an update of jellyfin) the tokens for the users changed and when trying to log in jellyseerr with my admin account (which is my only account, synced with jellyfin), it creates a new user account, keeping me out of the "owner" one.
I can see some sync errors stating an auth error when trying to sync with jellyfin:
peeking through the
db.sqlite3
file, I can see that a new user is created with the same name:Output (pretty printed for easy of reading):
I think jellyseerr should use the same user updating the token instead of creating a new one.
Beta Was this translation helpful? Give feedback.
All reactions