#Seerr 5 minute sync 404's but full library sync succeeds

75 messages · Page 1 of 1 (latest)

rotund musk
#

Hey all,

Using the same settings I had before the last update or two, it looked like Seerr was not syncing the download status of my videos correctly. After observation, it appeared as though it was updating over night, but not minute to minute like before.

Dove into the logs, and it looks like the recent activity job that fires every 5 minutes is getting a 404. My overnight job and manually firing a full sync both seem to succeed.

Seerr is running through docker with jellyfin in the same docker bridge.

Configuration attached. Just using the container name to reach out to the Jellyfin container directly. Same setup correctly reaches Sonarr/Radarr by container name over the bridge.

Errors every 5 minutes:
2026-04-10T21:20:00.019Z [error][Jellyfin API]: Something went wrong while getting library content from the Jellyfin server: Request failed with status code 404{"error":404}

2026-04-10T21:20:00.019Z [error][Jellyfin Sync]: Sync interrupted{"errorMessage":""}

Let me know if you need additional information, and I'll be happy to provide! Sorry if I missed a resolved issue, I tried searching here and GitHub, but I did not see this one.

summer gull
#

Thats just a changed jellyfinUserId on your owner account

#

Follow this

rotund musk
#

Sounds good! I'll try it in just a moment and ping back if I resolve or still have issues.

summer gull
#

It should resolve it. The recently added job uses your owner accounts jellyfinUserId which if has changed for whatever reason will throw a 404 😉

rotund musk
#

Couple of issues trying to set back up. When I put in my credentials, I get this error, but it proceeds anyways after a moment.
No logs apparent in the docker container, those stopped on april 2nd apparently?

Ok, weird, but try to continue on Stage 3, Configure Media Server.

Pressing "Sync Libraries" fails after a while. When I try to put in the API key and External URL, the "Save Changes" button grays out once I click into the API key section.

I tried this about 3 times in Firefox. Switched over to Brave just in case.

Same behavior

summer gull
#

From network logs

rotund musk
#

In jellyfin, it looks like this

jellyfin | [17:04:03] [WRN] [16] Jellyfin.Networking.Manager.NetworkManager: IPv6 is disabled in Jellyfin, but enabled in the OS. This may affect how the interface is selected.
jellyfin | [17:05:29] [INF] [43] Jellyfin.Server.Implementations.Users.UserManager: Authentication request for user has succeeded.
jellyfin | [17:05:29] [INF] [43] Emby.Server.Implementations.Session.SessionManager: Current/Max sessions for user: 2/0
jellyfin | [17:05:29] [INF] [43] Emby.Server.Implementations.Session.SessionManager: Logging out access token
jellyfin | [17:05:29] [INF] [43] Emby.Server.Implementations.Session.SessionManager: Creating new access token for user
jellyfin | [17:09:57] [INF] [46] Jellyfin.Server.Implementations.Users.UserManager: Authentication request for user has succeeded.
jellyfin | [17:09:57] [INF] [46] Emby.Server.Implementations.Session.SessionManager: Current/Max sessions for user: 2/0
jellyfin | [17:09:57] [INF] [46] Emby.Server.Implementations.Session.SessionManager: Logging out access token
jellyfin | [17:09:57] [INF] [46] Emby.Server.Implementations.Session.SessionManager: Creating new access token for user
jellyfin | [17:10:12] [INF] [16] Jellyfin.Server.Implementations.Users.UserManager: Authentication request for user has succeeded.
jellyfin | [17:10:12] [INF] [16] Emby.Server.Implementations.Session.SessionManager: Current/Max sessions for user user: 2/0
jellyfin | [17:10:12] [INF] [16] Emby.Server.Implementations.Session.SessionManager: Logging out access token
jellyfin | [17:10:12] [INF] [16] Emby.Server.Implementations.Session.SessionManager: Creating new access token for user

#

ok let me see if I can find. It wasn't under docker compose logs jellyseerr, but i'll look in the folder

summer gull
#

Stop seerr

#

And delete settings.json and delete everything inside logs folder

#

And restart

#

And have browser inspect open

#

With network tab

#

And then proceed and send the response

rotund musk
#

got it

#

Sorry I'm trying to figure out what to send because my credentials are also in this POST.

I submitted the Sign In page. It posted with all of the settings

Response was:

500

{"message":"Something went wrong."}
#

I tried to click library sync after the 500 post

summer gull
#

And libray?sync

rotund musk
summer gull
#

Also server logs

summer gull
rotund musk
#

OH one second

summer gull
rotund musk
#

Ok I found the issues in the logs once we reset the log files. It looks like it was pulling the email from my jellyfin lldap which was mismatched with what I entered. Continuing with the original reset instructions

#

resolved

#

Thank you for being patient and helping me figure out wtf I was doing

summer gull
#

What was the steps you took (so if anyone else has similar issue w the ldap)

#

Why was it failing with ldap

rotund musk
#

It wasn't LLDAP specifically. I'll be clear of what exactly my couple of issues were and share the logs.

First issue, my account was not being seen as admin correctly. I tried to follow the instructions listed here: https://docs.seerr.dev/troubleshooting#solution-reset-admin-access to resolve the issue. After backing up my settings file, and restarting Jellyseerr. I was getting an error proceeding from Stage 2 "Sign In".

Second issue, although my credentials were correct, the email associated with LLDAP did not match what I put under the "Sign In" page. Since I use the Jellyfin LDAP plugin with my LLDAP container, it was verifying this email along with the username and password. This through a "Something went wrong" error, but was ambigouus about the issue, but ultimately, it still let me proceed from Stage 2 to Stage 3. Once on Stage 3, the page would not behave correctly. The settings at the bottom of the page could be entered, but the "Save Changes" button would gray out. When I tried to Sync the Libraries before the full scan, it would just time out.

I previously ran Jellyseerr before the change to Seerr. I tried running docker compose logs jellyseerr , but it looks like my logs no longer show correctly. In the container under my bind mount jellyseerr config/logs/seerr.log (symlink), I was able to tail those to see what was happening during my setup instead. Those logs were mixed with my Jellyseerr logs which were never cleared. So once we got to the step where you asked me to clear them, I was able to follow what was happening an diagnose the issue.

[TMDB] failed to retrieve/fetch XXX

#

In the logs I saw the following:

head -50 seerr.log
2026-04-10T22:14:54.954Z [info]: Commit Tag: 94a70bb5fc9a4486857071a6fc048c8081fa7ca9
2026-04-10T22:14:55.343Z [info]: Starting Seerr version 3.1.0
2026-04-10T22:14:55.773Z [debug][Settings Migrator]: Checking migration '0001_migrate_hostname.js'...
2026-04-10T22:14:55.774Z [debug][Settings Migrator]: Checking migration '0002_migrate_apitokens.js'...
2026-04-10T22:14:55.775Z [debug][Settings Migrator]: Checking migration '0003_emby_media_server_type.js'...
2026-04-10T22:14:55.776Z [debug][Settings Migrator]: Checking migration '0004_migrate_region_setting.js'...
2026-04-10T22:14:55.776Z [debug][Settings Migrator]: Checking migration '0005_migrate_network_settings.js'...
2026-04-10T22:14:55.777Z [debug][Settings Migrator]: Checking migration '0006_remove_lunasea.js'...
2026-04-10T22:14:55.777Z [debug][Settings Migrator]: Checking migration '0007_migrate_arr_tags.js'...
2026-04-10T22:14:55.786Z [debug][Settings Migrator]: Migration '0007_migrate_arr_tags.js' has been applied.
2026-04-10T22:14:55.787Z [debug][Settings Migrator]: Checking migration '0008_migrate_blacklist_to_blocklist.js'...
2026-04-10T22:14:55.787Z [debug][Settings Migrator]: Migration '0008_migrate_blacklist_to_blocklist.js' has been applied.
2026-04-10T22:14:55.789Z [info][Notifications]: Registered notification agents
2026-04-10T22:14:55.811Z [info][Jobs]: Scheduled jobs loaded
2026-04-10T22:14:55.889Z [info][Server]: Server ready on port 5055
2026-04-10T22:15:00.004Z [debug][Jobs]: Starting scheduled job: Download Sync
2026-04-10T22:15:42.120Z [info][API]: Sign-in attempt from Jellyfin user with access to the media server; editing admin user for Seerr {"ip":"::ffff:172.18.0.21","jellyfinUsername":"myusername"}
2026-04-10T22:15:42.129Z [error][Auth]: SQLITE_CONSTRAINT: UNIQUE constraint failed: user.email```
#

Please let me know if this is an adequate summary or if you need to me to post any additional information to make this useful

summer gull
rotund musk
#

Yup, that's why I just immediately solved it once I was able to see

summer gull
#

We only allow unique emails bc email is used for authentication on local login

rotund musk
#

Not sure why docker compose logs jellyseerr doesn't show anymore, but at least I know where to look for future issues now. Again thank you for your time and your work on Seerr :)

summer gull
#

As in if you changed to seerr

#

When you migrated

rotund musk
#

ohhh

#

should i rename the container in these two spots?

summer gull
#

Oh wait ita named jellyseerr 🤔

rotund musk
#

yeah I just changed the image

summer gull
#

Oh also you dont need that "user: 1000:1000" btw

rotund musk
#

it stopped on april 2nd, which i think i was migrated over by then

summer gull
#

Our image runs as 1000:1000

rotund musk
#

ah nice

summer gull
#

But no harm in keeping it

summer gull
#

I wanna see what files it created

#

Also check if settings > logs load

#

That uses a file called .machine-logs in your logs folder

#

And not seerr.log

rotund musk
#

ignore the fact i mispelled jellyseer

#

just a bind mount typo :(

summer gull
#

Hmm it seems to be creating the proper .machine logs too

#

docker compose logs can you do that

#

Instead of specifying the container name

#

Or

#

docker ps and grab the container id

rotund musk
#

i can do it by container id

summer gull
#

And then use the id

rotund musk
#

yeah

#
2026-04-02T03:45:00.008Z [error][Jellyfin API]: Something went wrong while getting library content from the Jellyfin server: Request failed with status code 404 {"error":404}
2026-04-02T03:45:00.008Z [error][Jellyfin Sync]: Sync interrupted {"errorMessage":""}
2026-04-02T03:46:00.028Z [debug][Jobs]: Starting scheduled job: Download Sync
2026-04-02T03:47:00.027Z [debug][Jobs]: Starting scheduled job: Download Sync
2026-04-02T03:48:00.025Z [debug][Jobs]: Starting scheduled job: Download Sync
2026-04-02T03:49:00.025Z [debug][Jobs]: Starting scheduled job: Download Sync
2026-04-02T03:50:00.027Z [debug][Jobs]: Starting scheduled job: Download Sync
2026-04-02T03:50:00.029Z [info][Jobs]: Starting scheduled job: Jellyfin Recently Added Scan
2026-04-02T03:50:00.029Z [info][Jellyfin Sync]: Scan starting {"sessionId":"8eafe1f9-d501-47d9-9e81-beb5419e6b1e"}
2026-04-02T03:50:00.031Z [info][Jellyfin Sync]: Beginning to process recently added for library: Movies
2026-04-02T03:50:00.034Z [error][Jellyfin API]: Something went wrong while getting library content from the Jellyfin server: Request failed with status code 404 {"error":404}
2026-04-02T03:50:00.034Z [error][Jellyfin Sync]: Sync interrupted {"errorMessage":""}
2026-04-02T03:51:00.026Z [debug][Jobs]: Starting scheduled job: Download Sync

docker logs <container-id> shows the same thing as docker compose logs jellyseerr

They just stop on april 2nd

#

however under settings > logs like you were asking before.

Everything is just bebopping along

summer gull
#

Hmm not sure then. Could be a docker issue. Could try changing the service and container name so docker will consider it as a completely new container and might restart logs if you want docker logs that is

rotund musk
#

i renamed the container in both places highlighted before and docker is showing the logs now

rotund musk
#

for those who follow, don't forget to change your proxy-conf if you do lol

summer gull
#

Glad you got everything working!

rotund musk
#

Much appreciated. I hope you have a lovely day