A strange issue after re-deploying a fresh Jellyfin

[jeypawlik]

I was having some weird Jellyfin issues that resulted in me needing to completely delete and reinstall Jellyfin on my NAS. However, I hadn't thought about how that would affect Seerr.

I've logged in to my Seerr with the same Jellyfin login I had previously and linked up my Seerr once again, under the assumption that I lost all my requests. Ah well!

However I noticed that when I went to re-request a show it's already labelled "requested" but doesn't show up in my Requests list. I can't seem to un-request it at all to re-add it to my list. I'm just wondering if I might be missing something and unsure if this counted as a bug or not so I thought I'd add it here!

My Seerr and Jellyfin are both up to date. I didn't see anyone else have this problem, it seems like a weird one!

[jeypawlik]

oops my bad, I found I just had to delete the settings.json

[fallenbagel]

Yup. That updates the userid (what I talked about in the other comment) as mentioned in the docs. But keep in mind it will only update the owner account. Not your users. Your users will be treated as new accounts c:

[fallenbagel]

This is not a bug.

What you're trying to do is an unsupported setup. You can't use the same Seerr instance across different Jellyfin servers and expect everything to behave identically, because there are server-specific differences.

The main issue here is user IDs. Your account on the second Jellyfin server will have a different user ID, so Seerr will treat it as a different user. As a result, request status and permissions will not match what you expect.

Additionally, if enable scan in arr is enabled and the media already is monitored in Sonarr/Radarr, Seerr will mark it as requested or available. That's expected behavior, since one of Seerr's primary purposes is to track media already managed by the *arr applications.

If you're moving to a new Jellyfin server, the cleanest solution is usually to start with a fresh Seerr database. Otherwise, you'll need to manually modify the database and map the user IDs accordingly.

Also, support requests should be posted in the appropriate support channels (Discord), not in GitHub.