Just finished a fresh install of sparkbox on a ubuntu 26.04 after seeing the video. Been a smooth ride up until setting up seerr. when trying to connect i keep getting the pop up attached. Read though everything seerr/jellyfin related here and on the install guide with no luck.
34 replies
ziggity wrote:
ran it, looks to be up for 2 hours, roughly the start time from the reboot. root@dahausmedia:~sudo docker ps | grep seerrrr 2d029c14cc4d seerr/seerr:v3.2.0 "docker-entrypoint.s…" 2 hours ago Up 2 hours (healthy) 0.0.0.0:5055-5055/tcp, [::]:5055-5055/tcp sb-seerr
ziggity wrote:
looks like it gives a flat out 500 error wget: server returned error: HTTP/1.1 500 Internal Server Error
DigitalDojos wrote:
Just chiming in to say thanks as well! Same exact instance for me and workaround also got me to step 3. Thanks all!
tomspark wrote:
DigitalDojos — thanks for the confirmation. That makes 2 confirmed reports of the seerr Jellyfin pre-fill bug, plus probably a bunch of silent ones who gave up. v1.6.88 (just shipped) reverts the bad pre-fill so future installs don't need the workaround. sudo sparkbox update whenever you want to be on it — won't change anything for your existing setup since you're already past it.
tomspark wrote:
That Something went wrong while trying to sign in popup means Seerr reached Jellyfin (good — connection works) but the actual SIGN-IN failed. Almost always one of two things: 1) Jellyfin's first-run wizard isn't done yet. Open Jellyfin directly at http://YOUR-SERVER-IP:8096 — if it shows its own setup wizard (preferred display language, create admin user, add library), step through that first. Seerr can't authenticate against an account that doesn't exist yet. 2) You did set up Jellyfin, but you're using the wrong credentials. Jellyfin's admin login is a SEPARATE account from your SparkBox dashboard admin — they're not shared. Usernames are also case-sensitive. Once Jellyfin's wizard is finished and you have an admin user, come back to Seerr's sign-in step and paste that Jellyfin username + password.
ziggity wrote:
Just ran jellyfin again, opening directly takes me to home screen showing "nothing here". Checking the dashboard it shows a single user the default 'sparkbox'. Created a user and added permissions to it then attempted to sign in again, same error. Is it possible to refresh jellyfin and restart the install wizard? Upon first load i simply had a login screen to the sparkbox account with the password supplied from the docker popup.
tomspark wrote:
That sparkbox user IS the auto-created Jellyfin admin SparkBox seeds during install — that's why Jellyfin doesn't show its own first-run wizard, it's already past it. Use that one to sign into Seerr, not your own newly-created user. The password isn't the SparkBox dashboard password — Jellyfin has its own. It's stored on disk at /opt/sparkbox/state/jellyfin-admin-password.txt. Open it on the host: sudo cat /opt/sparkbox/state/jellyfin-admin-password.txt Username in Seerr's sign-in: sparkbox. Password: whatever's in that file. That should connect cleanly. (If you'd rather use your own user, you can set its password to match, but using the seeded admin is simplest.)
ziggity wrote:
Just ran the sudo line on host and got the same password i am currently inputting into seerr.
tomspark wrote:
OK so the password's right but Seerr still rejects it — that means the issue is one layer down. Two tests to pin where: 1) Sign into Jellyfin DIRECTLY at http://YOUR-SERVER-IP:8096 with username sparkbox + that same password. If Jellyfin rejects you there, the auto-seeded admin's password drifted somewhere. If Jellyfin accepts you, the issue is between Seerr and Jellyfin. 2) While Seerr is failing, grab Jellyfin's logs: sudo docker logs sb-jellyfin-media --tail 50 Paste anything that mentions Authentication / User / Login during the failed sign-in attempt. That'll tell me whether Jellyfin's auth API is even getting hit, or Seerr's request is bouncing at the network layer.
ziggity wrote:
1) Signed in to Jellyfin directly using the login info from the admin-password.txt with no issue. 2) ran the command and this is what i found. [01:19:02] [INF] [29] Jellyfin.Server.Implementations.Users.UserManager: Authentication request for sparkbox has succeeded. [01:19:02] [INF] [29] Emby.Server.Implementations.Session.SessionManager: Current/Max sessions for user sparkbox: 0/0 [01:19:02] [INF] [29] Emby.Server.Implementations.Session.SessionManager: Creating new access token for user 8dce1a4e-74d0-4416-aaba-d48e82f05c3a
tomspark wrote:
Big finding — Jellyfin's auth IS succeeding (Authentication request for sparkbox has succeeded + access token created). So the popup is lying about WHERE the failure is; Seerr is failing on a NEXT step after the auth, not at login itself. Most common cause is the auto-seeded sparkbox user has restricted permissions Seerr expects. Quick test that pins it: 1) In Jellyfin, Dashboard → Users → + Add User → create a fresh user, give it admin rights. 2) sudo docker restart sb-seerr 3) In Seerr's wizard, sign in with the NEW Jellyfin username + password instead. If that works, the sparkbox user has a permission missing and we can patch the auto-seed. If THAT fails too, it's a Seerr-side issue post-auth — paste sudo docker logs sb-seerr --tail 50 and I'll see what Seerr is choking on after the access token comes back.
ziggity wrote:
1) added new user, gave it admin rights. 2) ran restart 3) attempted log in with new user, same error. ran docker logs, here is what it gave back. root@dahausmedia:~ sudo docker logs sb-seerr --tail 50 2026-05-10T00:42:50.727Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet 2026-05-10T00:42:51.833Z [info][Server]: Server ready on port 5055 npm error path /app npm error command failed npm error signal SIGTERM npm error command sh -c NODEENV=production node dist/index.js npm error A complete log of this run can be found in: /home/node/.npm/logs/2026-05-10T004233861Z-debug-0.log seerr@3.2.0 start NODEENV=production node dist/index.js 2026-05-10T01:42:07.758Z [info]: Commit Tag: e4ee71ae459cd45b66ad59b4b90c01e102e28e49 2026-05-10T01:42:10.481Z [info]: Starting Seerr version 3.2.0 (node:18) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) 2026-05-10T01:42:14.066Z [debug][Settings Migrator]: Checking migration '0001migratehostname.js'... 2026-05-10T01:42:14.069Z [debug][Settings Migrator]: Checking migration '0002migrateapitokens.js'... 2026-05-10T01:42:14.072Z [debug][Settings Migrator]: Checking migration '0003embymediaservertype.js'... 2026-05-10T01:42:14.074Z [debug][Settings Migrator]: Checking migration '0004migrateregionsetting.js'... 2026-05-10T01:42:14.075Z [debug][Settings Migrator]: Checking migration '0005migratenetworksettings.js'... 2026-05-10T01:42:14.076Z [debug][Settings Migrator]: Checking migration '0006removelunasea.js'... 2026-05-10T01:42:14.078Z [debug][Settings Migrator]: Checking migration '0007migratearrtags.js'... 2026-05-10T01:42:14.081Z [debug][Settings Migrator]: Checking migration '0008migrateblacklisttoblocklist.js'... 2026-05-10T01:42:14.089Z [info][Notifications]: Registered notification agents 2026-05-10T01:42:14.147Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet 2026-05-10T01:42:15.162Z [info][Server]: Server ready on port 5055 npm error path /app npm error command failed npm error signal SIGTERM npm error command sh -c NODEENV=production node dist/index.js npm error A complete log of this run can be found in: /home/node/.npm/logs/2026-05-10T014159163Z-debug-0.log seerr@3.2.0 start NODEENV=production node dist/index.js 2026-05-10T01:44:44.902Z [info]: Commit Tag: e4ee71ae459cd45b66ad59b4b90c01e102e28e49 2026-05-10T01:44:47.700Z [info]: Starting Seerr version 3.2.0 (node:18) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) 2026-05-10T01:44:52.416Z [debug][Settings Migrator]: Checking migration '0001migratehostname.js'... 2026-05-10T01:44:52.464Z [debug][Settings Migrator]: Checking migration '0002migrateapitokens.js'... 2026-05-10T01:44:52.468Z [debug][Settings Migrator]: Checking migration '0003embymediaservertype.js'... 2026-05-10T01:44:52.471Z [debug][Settings Migrator]: Checking migration '0004migrateregionsetting.js'... 2026-05-10T01:44:52.474Z [debug][Settings Migrator]: Checking migration '0005migratenetworksettings.js'... 2026-05-10T01:44:52.476Z [debug][Settings Migrator]: Checking migration '0006removelunasea.js'... 2026-05-10T01:44:52.480Z [debug][Settings Migrator]: Checking migration '0007migratearrtags.js'... 2026-05-10T01:44:52.484Z [debug][Settings Migrator]: Checking migration '0008migrateblacklisttoblocklist.js'... 2026-05-10T01:44:52.492Z [info][Notifications]: Registered notification agents 2026-05-10T01:44:52.499Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet 2026-05-10T01:44:53.690Z [info][Server]: Server ready on port 5055
tomspark wrote:
Those startup logs are clean — but the line "Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet" confirms Seerr never persisted your Jellyfin connection, meaning the Sign In step is still bailing before it saves. Two things that'll narrow it down: (1) right after you click Sign In and the popup pops, run sudo docker logs sb-seerr --tail 100 and paste the new lines (not the startup ones). (2) Open F12 → Network tab in your browser, click Sign In, find the request that goes red, and paste its status code + response body. That'll tell us whether Seerr is rejecting the password, failing the Jellyfin handshake, or hitting NPM somewhere it shouldn't.
tomspark wrote:
Your latest reply came through empty (body didn't post — maybe image-only?). Can you re-paste the post-Sign-In sb-seerr log + the F12 Network response so I've got something to work from? Just want to make sure I'm answering what you actually shared.
ziggity wrote:
Automod removed my reply, trying a different method. 1) ran the command and saw no change. 2) not very familiar with this tab on browser so i did my best, attached are screenshots of the test and the errors.
ziggity wrote:
here is the sign in logs starting from commands root@dahausmedia:~ sudo docker logs sb-seerr --tail 100 npm error command failed npm error signal SIGTERM npm error command sh -c NODEENV=production node dist/index.js npm notice npm notice New major version of npm available! 10.9.4 - 11.14.1 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.14.1 npm notice To update run: npm install -g npm@11.14.1 npm notice npm error A complete log of this run can be found in: /home/node/.npm/logs/2026-05-10T002325853Z-debug-0.log seerr@3.2.0 start NODEENV=production node dist/index.js 2026-05-10T00:24:10.308Z [info]: Commit Tag: e4ee71ae459cd45b66ad59b4b90c01e102e28e49 2026-05-10T00:24:18.207Z [info]: Starting Seerr version 3.2.0 (node:18) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) 2026-05-10T00:24:24.688Z [debug][Settings Migrator]: Checking migration '0001migratehostname.js'... 2026-05-10T00:24:24.694Z [debug][Settings Migrator]: Checking migration '0002migrateapitokens.js'... 2026-05-10T00:24:24.698Z [debug][Settings Migrator]: Checking migration '0003embymediaservertype.js'... 2026-05-10T00:24:24.702Z [debug][Settings Migrator]: Checking migration '0004migrateregionsetting.js'... 2026-05-10T00:24:24.709Z [debug][Settings Migrator]: Checking migration '0005migratenetworksettings.js'... 2026-05-10T00:24:24.712Z [debug][Settings Migrator]: Checking migration '0006removelunasea.js'... 2026-05-10T00:24:24.717Z [debug][Settings Migrator]: Checking migration '0007migratearrtags.js'... 2026-05-10T00:24:24.728Z [debug][Settings Migrator]: Checking migration '0008migrateblacklisttoblocklist.js'... 2026-05-10T00:24:24.741Z [info][Notifications]: Registered notification agents 2026-05-10T00:24:24.759Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet 2026-05-10T00:24:25.851Z [info][Server]: Server ready on port 5055 npm error path /app npm error command failed npm error signal SIGTERM npm error command sh -c NODEENV=production node dist/index.js npm error A complete log of this run can be found in: /home/node/.npm/logs/2026-05-10T002351561Z-debug-0.log seerr@3.2.0 start NODEENV=production node dist/index.js 2026-05-10T00:42:42.821Z [info]: Commit Tag: e4ee71ae459cd45b66ad59b4b90c01e102e28e49 2026-05-10T00:42:45.914Z [info]: Starting Seerr version 3.2.0 (node:18) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) 2026-05-10T00:42:50.643Z [debug][Settings Migrator]: Checking migration '0001migratehostname.js'... 2026-05-10T00:42:50.647Z [debug][Settings Migrator]: Checking migration '0002migrateapitokens.js'... 2026-05-10T00:42:50.651Z [debug][Settings Migrator]: Checking migration '0003embymediaservertype.js'... 2026-05-10T00:42:50.653Z [debug][Settings Migrator]: Checking migration '0004migrateregionsetting.js'... 2026-05-10T00:42:50.655Z [debug][Settings Migrator]: Checking migration '0005migratenetworksettings.js'... 2026-05-10T00:42:50.657Z [debug][Settings Migrator]: Checking migration '0006removelunasea.js'... 2026-05-10T00:42:50.660Z [debug][Settings Migrator]: Checking migration '0007migratearrtags.js'... 2026-05-10T00:42:50.664Z [debug][Settings Migrator]: Checking migration '0008migrateblacklisttoblocklist.js'... 2026-05-10T00:42:50.720Z [info][Notifications]: Registered notification agents 2026-05-10T00:42:50.727Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet 2026-05-10T00:42:51.833Z [info][Server]: Server ready on port 5055 npm error path /app npm error command failed npm error signal SIGTERM npm error command sh -c NODEENV=production node dist/index.js npm error A complete log of this run can be found in: /home/node/.npm/logs/2026-05-10T004233861Z-debug-0.log seerr@3.2.0 start NODEENV=production node dist/index.js 2026-05-10T01:42:07.758Z [info]: Commit Tag: e4ee71ae459cd45b66ad59b4b90c01e102e28e49 2026-05-10T01:42:10.481Z [info]: Starting Seerr version 3.2.0 (node:18) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) 2026-05-10T01:42:14.066Z [debug][Settings Migrator]: Checking migration '0001migratehostname.js'... 2026-05-10T01:42:14.069Z [debug][Settings Migrator]: Checking migration '0002migrateapitokens.js'... 2026-05-10T01:42:14.072Z [debug][Settings Migrator]: Checking migration '0003embymediaservertype.js'... 2026-05-10T01:42:14.074Z [debug][Settings Migrator]: Checking migration '0004migrateregionsetting.js'... 2026-05-10T01:42:14.075Z [debug][Settings Migrator]: Checking migration '0005migratenetworksettings.js'... 2026-05-10T01:42:14.076Z [debug][Settings Migrator]: Checking migration '0006removelunasea.js'... 2026-05-10T01:42:14.078Z [debug][Settings Migrator]: Checking migration '0007migratearrtags.js'... 2026-05-10T01:42:14.081Z [debug][Settings Migrator]: Checking migration '0008migrateblacklisttoblocklist.js'... 2026-05-10T01:42:14.089Z [info][Notifications]: Registered notification agents 2026-05-10T01:42:14.147Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet 2026-05-10T01:42:15.162Z [info][Server]: Server ready on port 5055 npm error path /app npm error command failed npm error signal SIGTERM npm error command sh -c NODEENV=production node dist/index.js npm error A complete log of this run can be found in: /home/node/.npm/logs/2026-05-10T014159163Z-debug-0.log seerr@3.2.0 start NODEENV=production node dist/index.js 2026-05-10T01:44:44.902Z [info]: Commit Tag: e4ee71ae459cd45b66ad59b4b90c01e102e28e49 2026-05-10T01:44:47.700Z [info]: Starting Seerr version 3.2.0 (node:18) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) 2026-05-10T01:44:52.416Z [debug][Settings Migrator]: Checking migration '0001migratehostname.js'... 2026-05-10T01:44:52.464Z [debug][Settings Migrator]: Checking migration '0002migrateapitokens.js'... 2026-05-10T01:44:52.468Z [debug][Settings Migrator]: Checking migration '0003embymediaservertype.js'... 2026-05-10T01:44:52.471Z [debug][Settings Migrator]: Checking migration '0004migrateregionsetting.js'... 2026-05-10T01:44:52.474Z [debug][Settings Migrator]: Checking migration '0005migratenetworksettings.js'... 2026-05-10T01:44:52.476Z [debug][Settings Migrator]: Checking migration '0006removelunasea.js'... 2026-05-10T01:44:52.480Z [debug][Settings Migrator]: Checking migration '0007migratearrtags.js'... 2026-05-10T01:44:52.484Z [debug][Settings Migrator]: Checking migration '0008migrateblacklisttoblocklist.js'... 2026-05-10T01:44:52.492Z [info][Notifications]: Registered notification agents 2026-05-10T01:44:52.499Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet 2026-05-10T01:44:53.690Z [info][Server]: Server ready on port 5055
tomspark wrote:
Perfect — that's the smoking gun. POST /api/v1/auth/jellyfin returning 500 means Seerr's backend crashed trying to reach whatever hostname is in the Jellyfin field. Most common cause: people paste their LAN IP into that field, which routes through NPM and Seerr can't talk to Jellyfin that way. The fix is to use the docker service name instead, since seerr and jellyfin-media share an internal network. In Seerr's Jellyfin step, set Hostname/IP to: jellyfin-media, Port to: 8096, untick "Use SSL". Submit. v1.6.78 pre-fills this; if you installed before today's release, the field starts empty. If it still 500s, paste sudo docker logs sb-seerr --tail 50 right after the click — the stack trace will tell us what's actually choking.
ziggity wrote:
Finally back at it again, below is the seerr logs. this is off a fresh boot up from both systems, made sure all apps were up and healthly before starting. root@dahausmedia:~ sudo docker logs sb-seerr --tail 50 2026-05-10T02:34:34.310Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet 2026-05-10T02:34:35.842Z [info][Server]: Server ready on port 5055 npm error path /app npm error command failed npm error signal SIGTERM npm error command sh -c NODEENV=production node dist/index.js npm error A complete log of this run can be found in: /home/node/.npm/logs/2026-05-10T023343138Z-debug-0.log seerr@3.2.0 start NODEENV=production node dist/index.js 2026-05-10T20:54:35.427Z [info]: Commit Tag: e4ee71ae459cd45b66ad59b4b90c01e102e28e49 2026-05-10T20:54:43.517Z [info]: Starting Seerr version 3.2.0 (node:18) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) 2026-05-10T20:54:53.913Z [debug][Settings Migrator]: Checking migration '0001migratehostname.js'... 2026-05-10T20:54:53.919Z [debug][Settings Migrator]: Checking migration '0002migrateapitokens.js'... 2026-05-10T20:54:53.936Z [debug][Settings Migrator]: Checking migration '0003embymediaservertype.js'... 2026-05-10T20:54:53.948Z [debug][Settings Migrator]: Checking migration '0004migrateregionsetting.js'... 2026-05-10T20:54:53.955Z [debug][Settings Migrator]: Checking migration '0005migratenetworksettings.js'... 2026-05-10T20:54:53.969Z [debug][Settings Migrator]: Checking migration '0006removelunasea.js'... 2026-05-10T20:54:53.976Z [debug][Settings Migrator]: Checking migration '0007migratearrtags.js'... 2026-05-10T20:54:53.991Z [debug][Settings Migrator]: Checking migration '0008migrateblacklisttoblocklist.js'... 2026-05-10T20:54:54.037Z [info][Notifications]: Registered notification agents 2026-05-10T20:54:54.082Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet 2026-05-10T20:54:56.514Z [info][Server]: Server ready on port 5055 npm error path /app npm error command failed npm error signal SIGTERM npm error command sh -c NODEENV=production node dist/index.js npm error A complete log of this run can be found in: /home/node/.npm/logs/2026-05-10T205357464Z-debug-0.log seerr@3.2.0 start NODEENV=production node dist/index.js 2026-05-10T21:14:20.378Z [info]: Commit Tag: e4ee71ae459cd45b66ad59b4b90c01e102e28e49 2026-05-10T21:14:26.999Z [info]: Starting Seerr version 3.2.0 (node:18) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) 2026-05-10T21:14:35.357Z [debug][Settings Migrator]: Checking migration '0001migratehostname.js'... 2026-05-10T21:14:35.374Z [debug][Settings Migrator]: Checking migration '0002migrateapitokens.js'... 2026-05-10T21:14:35.384Z [debug][Settings Migrator]: Checking migration '0003embymediaservertype.js'... 2026-05-10T21:14:35.389Z [debug][Settings Migrator]: Checking migration '0004migrateregionsetting.js'... 2026-05-10T21:14:35.393Z [debug][Settings Migrator]: Checking migration '0005migratenetworksettings.js'... 2026-05-10T21:14:35.399Z [debug][Settings Migrator]: Checking migration '0006removelunasea.js'... 2026-05-10T21:14:35.403Z [debug][Settings Migrator]: Checking migration '0007migratearrtags.js'... 2026-05-10T21:14:35.410Z [debug][Settings Migrator]: Checking migration '0008migrateblacklisttoblocklist.js'... 2026-05-10T21:14:35.440Z [info][Notifications]: Registered notification agents 2026-05-10T21:14:35.470Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet 2026-05-10T21:14:36.701Z [info][Server]: Server ready on port 5055
tomspark wrote:
Fresh start is good. In the Seerr sign-in form, put jellyfin-media in the Hostname field and 8096 in Port (untick Use SSL). Username stays sparkbox and use the same password you read earlier. The key one is the hostname — typing your LAN IP routes through NPM and breaks it. If it still fails, run sudo docker logs sb-seerr --tail 30 within 30 seconds of clicking Sign In so we catch the actual error.
ziggity wrote:
was already using the exact login info mentioned, ran sudo once popup started to fade, roughly 8 secs after click npm error path /app npm error command failed npm error signal SIGTERM npm error command sh -c NODEENV=production node dist/index.js npm notice npm notice New major version of npm available! 10.9.4 - 11.14.1 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.14.1 npm notice To update run: npm install -g npm@11.14.1 npm notice npm error A complete log of this run can be found in: /home/node/.npm/logs/2026-05-10T213709220Z-debug-0.log seerr@3.2.0 start NODEENV=production node dist/index.js 2026-05-10T21:38:05.094Z [info]: Commit Tag: e4ee71ae459cd45b66ad59b4b90c01e102e28e49 2026-05-10T21:38:13.136Z [info]: Starting Seerr version 3.2.0 (node:18) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) 2026-05-10T21:38:30.128Z [debug][Settings Migrator]: Checking migration '0001migratehostname.js'... 2026-05-10T21:38:30.146Z [debug][Settings Migrator]: Checking migration '0002migrateapitokens.js'... 2026-05-10T21:38:30.159Z [debug][Settings Migrator]: Checking migration '0003embymediaservertype.js'... 2026-05-10T21:38:30.170Z [debug][Settings Migrator]: Checking migration '0004migrateregionsetting.js'... 2026-05-10T21:38:30.177Z [debug][Settings Migrator]: Checking migration '0005migratenetworksettings.js'... 2026-05-10T21:38:30.179Z [debug][Settings Migrator]: Checking migration '0006removelunasea.js'... 2026-05-10T21:38:30.185Z [debug][Settings Migrator]: Checking migration '0007migratearrtags.js'... 2026-05-10T21:38:30.195Z [debug][Settings Migrator]: Checking migration '0008migrateblacklisttoblocklist.js'... 2026-05-10T21:38:30.210Z [info][Notifications]: Registered notification agents 2026-05-10T21:38:30.246Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet 2026-05-10T21:38:33.429Z [info][Server]: Server ready on port 5055
tomspark wrote:
Those seerr logs show NO POST request hit seerr at all when you clicked Sign In — meaning the click went somewhere else. That's actually a useful clue. Quick check via your browser dev tools: In the Seerr tab, press F12 (or right-click anywhere → Inspect). Click the "Network" tab at the top of the dev panel. Click the 🚫 (clear/no-entry) icon to wipe the list. Now click Sign In in Seerr. A row in the list will turn red. Click that row, look at the right panel, and copy two things: the full URL at the top, and the status code. Paste those here. That'll tell me if NPM is intercepting the request or if it never made it out of the browser.
ziggity wrote:
first red row is "jellyfin" Request URL http://myserverip:5055/api/v1/auth/jellyfin Status Code 500 Internal Server Error second red row is "me" Request URL http://myserverip:5055/api/v1/auth/me Status Code 401 Unauthorized
tomspark wrote:
Got it — POST to /api/v1/auth/jellyfin returning 500 + nothing showing in seerr's log means seerr is actually crashing handling that request (process exits before it can write the error). The 401 on /me is normal, ignore that one. To catch the crash live, run: sudo docker logs -f sb-seerr The -f means follow / watch in real-time. Leave that terminal window open. Then in your browser, click Sign In in seerr again. New lines will scroll in the terminal. The moment you see an error message or stack trace, press Ctrl+C to stop, then copy those new lines (the ones that appeared AFTER you clicked) and paste here. That'll show the actual crash reason — most likely seerr can't resolve the Jellyfin hostname for some reason, but the trace will tell us exactly.
ziggity wrote:
ran the sudo, it instantly fed back the following, clicked sign in, got the error, no new lines. waited and no change or delayed info. root@dahausmedia:~ sudo docker logs -f sb-seerr seerr@3.2.0 start NODEENV=production node dist/index.js npm error path /app npm error command failed npm error signal SIGTERM npm error command sh -c NODEENV=production node dist/index.js npm notice npm notice New major version of npm available! 10.9.4 - 11.14.1 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.14.1 npm notice To update run: npm install -g npm@11.14.1 npm notice npm error A complete log of this run can be found in: /home/node/.npm/logs/2026-05-10T213709220Z-debug-0.log seerr@3.2.0 start NODEENV=production node dist/index.js 2026-05-10T21:38:05.094Z [info]: Commit Tag: e4ee71ae459cd45b66ad59b4b90c01e102e28e49 2026-05-10T21:38:13.136Z [info]: Starting Seerr version 3.2.0 (node:18) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) 2026-05-10T21:38:30.128Z [debug][Settings Migrator]: Checking migration '0001migratehostname.js'... 2026-05-10T21:38:30.146Z [debug][Settings Migrator]: Checking migration '0002migrateapitokens.js'... 2026-05-10T21:38:30.159Z [debug][Settings Migrator]: Checking migration '0003embymediaservertype.js'... 2026-05-10T21:38:30.170Z [debug][Settings Migrator]: Checking migration '0004migrateregionsetting.js'... 2026-05-10T21:38:30.177Z [debug][Settings Migrator]: Checking migration '0005migratenetworksettings.js'... 2026-05-10T21:38:30.179Z [debug][Settings Migrator]: Checking migration '0006removelunasea.js'... 2026-05-10T21:38:30.185Z [debug][Settings Migrator]: Checking migration '0007migratearrtags.js'... 2026-05-10T21:38:30.195Z [debug][Settings Migrator]: Checking migration '0008migrateblacklisttoblocklist.js'... 2026-05-10T21:38:30.210Z [info][Notifications]: Registered notification agents 2026-05-10T21:38:30.246Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet 2026-05-10T21:38:33.429Z [info][Server]: Server ready on port 5055 ^Croot@dahausmedia:~
tomspark wrote:
Hmm, no new lines after a click is weird — usually means the container isn't actually running OR is restarting too fast to log anything. Quick check: sudo docker ps | grep seerr Look at the STATUS column on the result row. Tell me what it says — could be "Up 2 minutes" (running), or "Restarting (137)" (crash loop), or you might not see sb-seerr at all (dead). That answer narrows down which path to take next.
DigitalDojos wrote:
Following along as having exact same scenario/errors occur. Attempted everything suggest so far going to comb my logs to see if aligns but so far at same step where I made a 2nd Jellyfin user to see if that worked and it was same result
tomspark wrote:
Container's healthy and listening on 5055 — so the 500 isn't a crash, it's a real error response from inside seerr. Let's bypass the browser and the docker network layer entirely and hit seerr directly: sudo docker exec sb-seerr wget -qO- --post-data='{"username":"sparkbox","password":"placeholder","hostname":"jellyfin-media","port":8096,"useSsl":false,"urlBase":""}' --header='Content-Type:application/json' http://localhost:5055/api/v1/auth/jellyfin Paste whatever it prints. Even with a wrong password, seerr should give a clean "Unauthorized" or similar — it should NOT 500. The 500 response body will tell us exactly which step inside seerr is choking (Jellyfin handshake, settings persist, etc).
tomspark wrote:
That's wget hiding the body on HTTP error responses (annoying default). Seerr itself is Node, so we can use Node to make the same request and actually capture the body: sudo docker exec sb-seerr node -e "fetch('http://localhost:5055/api/v1/auth/jellyfin',{method:'POST',headers:{'Content-Type':'application/json'},body:JSON.stringify({username:'sparkbox',password:'placeholder',hostname:'jellyfin-media',port:8096,useSsl:false,urlBase:''})}).then(async r=console.log('STATUS:',r.status,'\nBODY:',await r.text()))" It should print STATUS: 500 followed by BODY: (the real error message). That body will pinpoint which step inside seerr is choking — Jellyfin DNS, the actual auth call, settings persist, etc.
ziggity wrote:
STATUS: 500 BODY: {"error":"Jellyfin hostname already configured"}
tomspark wrote:
FOUND IT — and it's our bug. The error "Jellyfin hostname already configured" means seerr's settings already have a Jellyfin entry from our seed script (we pre-filled the hostname during install in v1.6.78 to save users from typing it). But seerr's wizard then rejects YOUR sign-in attempt because it thinks Jellyfin is already done. The pre-fill made things worse, not better. Quick reset to unstick you: sudo docker stop sb-seerr && sudo rm -f /opt/sparkbox/modules/media/config/seerr/settings.json && sudo docker start sb-seerr Wait ~30 seconds. Refresh seerr in your browser — the wizard will run from scratch with empty fields. Fill in Jellyfin yourself: hostname jellyfin-media, port 8096, untick Use SSL, then your sparkbox/password. That should sign in cleanly. Going to ship v1.6.88 to revert the broken pre-fill.
ziggity wrote:
That did it! Its been a long ride but im happy to see step 3. next ill be following along with the file manager thread. Thank you tom!
fellini wrote:
I'll follow up in here as I'm running in to what I think is the same problem. For me, it's a Windows 10 box w/ WSL Jellyfin all set up fine. Trying to get Seer going and hitting the same error. Log output looks similar to ziggity's Jellyfin's log when the attempt fails: [2026-05-10 20:48:36.228 -04:00] [INF] [48] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "172.20.4.1" closed [2026-05-10 20:48:36.637 -04:00] [INF] [51] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "172.20.4.1" request On the browser network inspection: Request URL http://localhost:5055/api/v1/auth/jellyfin Request Method POST Status Code 500 Internal Server Error Remote Address [::1]:5055 Referrer Policy strict-origin-when-cross-origin Payload {"username":"sparkbox","password":"xxobscuredjellyfinpwd","hostname":"jellyfin-media","port":8096,"useSsl":false,"urlBase":"","email":"admin@example.com","serverType":2} Response {"error":"Jellyfin hostname already configured"} I've been using localhost since the 172. IPs don't appear to work correctly for me. Hope this helps. I'm more than a little rusty with all this stuff.
tomspark wrote:
fellini — same bug as ziggity, ours not yours. v1.6.88 (just shipped) reverts the bad pre-fill so future installs don't hit it. For YOUR install, the manual reset to unblock you right now: sudo docker stop sb-seerr && sudo rm -f /opt/sparkbox/modules/media/config/seerr/settings.json && sudo docker start sb-seerr Wait ~30 seconds, refresh seerr in your browser, wizard runs from scratch with empty fields. Fill in jellyfin-media + 8096 + untick Use SSL + sparkbox/password. Should sign in cleanly this time. That makes 3 confirmed reports of this bug now (you + ziggity + DigitalDojos) — really validates the fix.
fellini wrote:
Success!! Thanks! I'll continue chiseling away at the rest.