My question: After troubleshooting with Tom AI, I provided the last few lines from /opt/sparkbox/state/media-autoseed.log; log contents as follows: [autoseed] Waiting for Seerr to be reachable... [autoseed] Signing Seerr into Jellyfin... [autoseed] FAIL: Seerr Jellyfin sign-in failed: HTTP 500 — {"error":"Jellyfin hostname already configured"} [media-autoseed] ERROR: media-autoseed.js exited non-zero. See /opt/sparkbox/state/media-autoseed.log. [media-autoseed] Fallback: complete Jellyfin + Seerr wizards manually, then run 'sudo sparkbox media-finish'. SparkBox AI replied: The autoseed failed because Seerr already has a Jellyfin server saved from an earlier attempt. The autoseed tried to add it again, and Seerr refused with "Jellyfin hostname already configured." That's why setup never finished and the admin link never got set. Also, I told you to look in /app. That was wrong. Your install is at /opt/sparkbox, so the log is /opt/sparkbox/state/media-autoseed.log. The output you pasted matches. On the admin flag: Seerr gives admin to whichever account first signed in through Jellyfin during its setup. My best guess is Seerr was set up before the sparkbox admin account was in place, so the link came up as a regular user. I can't confirm that from here. What I won't do: - Re-run the wizard or reset Seerr. There's no supported way from here, and deleting its config could break the Jellyfin and Sonarr links. - Edit the saved Jellyfin entry in Seerr. That's the va …(cut here — the full chat went to Tom) What I still need help with: Tom AI analysis above is correct; there was a strange hiccup with the initial Jellyfin / Seerr sign-in sequence. I don't remember the exact details, but I believe the Seerr account is not properly synced with the Jellyfin account
5 replies
Chris wrote:
Thanks for posting the log, it narrows this down. Seerr refused SparkBox's sign-in with 'Jellyfin hostname already configured'. That means Seerr already had a Jellyfin connection saved and will not accept a second one. Because that sign-in never completed, the SparkBox account never signed in to Seerr at that step. That may also be why requests are waiting in Pending, but I have not confirmed that yet. I can't confirm the explanation about admin rights from the earlier chat, so please don't act on it or on the Seerr steps it suggested. Please don't run repair-seerr or redo Seerr's setup yet. That command wipes Seerr's own settings folder, including its request history. One check for now. Run this and reply with the line it prints (no passwords): sudo sparkbox version If it isn't 1.7.8, send me the number and I'll give you the next step. The update comes before any Seerr changes.
moonjellyfish8416 wrote:
SparkBox v1.7.6
Chris wrote:
Thanks, 1.7.6 is the version we needed. The current SparkBox release is 1.7.8, so your box is two releases behind. Let's update before we look at Seerr again, so we are working from the same code. Run this on the box. Use upgrade, not update: update only refreshes app images, while upgrade installs a new SparkBox release. sudo sparkbox upgrade When it finishes, run: sudo sparkbox version It should print 1.7.8. If the upgrade stops with an error, reply with the last few lines it printed, with any passwords removed. We have not confirmed that 1.7.8 changes the Seerr sign-in, so we will check Seerr after the upgrade rather than assume it fixes it. Please still don't run repair-seerr or redo Seerr's setup.
moonjellyfish8416 wrote:
Here is the message I receive when running "sudo sparkbox upgrade": [INFO] This box is in the group still on v1.7.6 while v1.7.8 rolls out gradually — upgrading to v1.7.6. [OK] SparkBox is already on the latest release (v1.7.6). [INFO] To just refresh your apps' images, use: sudo sparkbox update
Chris wrote:
I'm sorry. I told you the upgrade would bring your box to 1.7.8, and I had no basis for saying that. 1.7.8 is the current release, but when your box asked which version to move to, the answer was 1.7.6, so the upgrade stopped there. The line "already on the latest release (v1.7.6)" compares your box with that 1.7.6 target, not with 1.7.8. I can't see from here why your box was given that target, so I have logged it with the team as an open issue, with the output you pasted. Please leave the box as it is for now. Don't run repair-seerr or redo Seerr's setup, and there's no need to run the upgrade again, since it will give the same answer. The Seerr question is still open, and I won't guess at it again until the box is on 1.7.8. We have learned from this. We are changing how we word upgrade answers, so we don't promise a version before we can see it.