20 replies
Chris wrote:
Nothing to apologise for — that's the documented step. Our install guide tells you to complete Jellyfin's first-run wizard and choose your own login, which is exactly what you did. It also explains the whole thread. SparkBox writes its candidate Jellyfin password to your box before it finishes setting that account up, and on your box that setup never completed — so the jellyfin entry you saw was a password Jellyfin had never accepted. That's our gap, not anything you got wrong. Small mercy: it also means that screenshot never exposed a working login. Getting back into a wizard-made admin isn't something SparkBox can do yet. It's sitting with Tom now, and you'll hear from me here either way.
Chris wrote:
That dialog is telling you the truth rather than hiding a fault — Jellyfin's credentials only get written after SparkBox's autoseed step runs, and autoseed waits until gluetun is healthy. Since your VPN only started working a few minutes ago, autoseed most likely never got its chance yet. Two steps. First run: sudo sparkbox passwords — if a jellyfin entry appears, that's your username and password. If it doesn't, run sudo sparkbox media-autoseed (safe to re-run), then sudo sparkbox media-finish, and refresh the dashboard. If anything errors, paste the message here and I'll pick it up — no passwords in the post, please.
DravenB wrote:
tried signing into seerr like it said but i wont let me
Chris wrote:
Thanks for the screenshot — that output is better news than it looks. Everything ran; Seerr just needs one sign-in before it can finish. The catch is that the account isn't one you invent — SparkBox creates it for you. The username is sparkbox, and the password is saved on your box. Run sudo sparkbox passwords and look for the jellyfin entry, then use that pair at http://<your-box:5055. If there's no jellyfin line in that output, tell me and paste what sudo sparkbox media-autoseed prints — it masks the password, so it's safe to share, and it'll show me which step didn't land.
DravenB wrote:
it still wont let me sign in
Chris wrote:
Before anything else — please edit that last comment and remove the screenshot. It shows your real Jellyfin password in plain text, and this thread is public, so please treat that password as compromised. My earlier reply is what sent you down that path, and I'm sorry for that. I'm flagging two things to Tom right now: the safe way to rotate that credential, and why the Seerr sign-in still isn't going through. He handles these personally, and I'd rather get you verified steps than have you try a guess on a live box. I'll follow up here as soon as I have them.
DravenB wrote:
ok thanks i greatly appreciate it
Chris wrote:
Following up like I said I would. On changing that Jellyfin password: there is no safe self-serve way to do it right now without knocking Seerr out of sync, so rather than hand you a guess I have put it in front of Tom — he handles these personally and will come back on it. For the sign-in itself, one command worth running: sudo sparkbox up That kicks off a built-in repair that re-points Seerr at Jellyfin. A wrong stored address is the usual reason a correct password still bounces you. Watch the lines near the end that start with [seerr-heal] and paste those here — they do not contain passwords. One more thing: that screenshot is still visible on your earlier comment. If editing it is not working on your end, just say so and Tom can take it down for you.
Chris wrote:
Good news, and sooner than I expected — Tom shipped that reset today in v1.6.435, and your report is what it was built from. Run sudo sparkbox update, then: sudo sparkbox reset-password jellyfin It changes the password inside Jellyfin and the copy saved on your box together, which is exactly the drift that was blocking you, and it re-checks the Seerr sign-in for you at the end. So this should cover both the exposed password and the login that would not go through. One thing: it prints the new password on screen, so please do not screenshot or paste that output here. And the old screenshot higher up is still visible — say the word if editing it is not working for you.
DravenB wrote:
"The saved password no longer works in Jellyfin (it was probably changed inside Jellyfin's own settings) — falling back to the admin API key. [jf-password] ERROR: Saved password is rejected by Jellyfin and there is no apikey to fall back on. Change the password inside Jellyfin (Dashboard - Users), then run this again with --stdin and type that same password so SparkBox can re-sync." I updated sparkbox but im getting this error above when running the command and i cant sign in the jellyfin at all because i didnt save my previous password, im also having a similar issue with portainer where i cant sign in as well
Chris wrote:
Portainer first, since that one has a real fix: sudo sparkbox repair-portainer. It rebuilds Portainer's login from scratch and writes you a fresh admin password. The only thing you lose is settings made inside Portainer itself, which for most people is nothing. Jellyfin is the harder half. That error means Jellyfin is holding a password SparkBox never saw, so there is nothing left on the box to authenticate with. One question decides the fix: when you first opened Jellyfin, did you go through its own setup screen and choose your own username and password? I am not going to guess at a recovery on a live box, so I am flagging this to Tom with the exact error.
DravenB wrote:
yes I did make my own setup when opening Jellyfin for the first time sorry about that
DravenB wrote:
Ok just keep me up to date if you can
Chris wrote:
Here is a real update, and a better one than last time. Going back over your box: the sparkbox account I pointed you at was never actually created on yours. You made your own Jellyfin login in the first-run wizard instead, so that name was never going to be accepted. Sorry for sending you round that loop. Worth trying now: open Seerr at http://your-box-ip:5055 and on its sign-in screen use the Jellyfin username and password you chose yourself. Seerr just checks them against Jellyfin, so your own login should go through. And ignore what that last command printed about running it again with --stdin. Tom has it now; as written it cannot help.
DravenB wrote:
Ok seerr now works thank you but I have one more question you see I have a 28 tb hdd drive I got to store my media is there a way to mount it in Tom spark box?
Chris wrote:
Great to hear Seerr let you in. Yes, this is supported — but one thing to know first: SparkBox doesn't mount drives itself. It reads a path your Ubuntu box has already mounted, and the setting that points it there is Media Root, in Settings. Change that one value and movies, TV, music and downloads all follow it. Keep the whole media root on the drive, not just the library. Downloads and library have to share one filesystem, or every import copies the file instead of hardlinking and costs you double the space. Before I hand you any steps: is the drive already showing up on the box, and does it have anything on it yet? — Chris
DravenB wrote:
the drive is already mounted and showing
Chris wrote:
Perfect — that's the hard part done. In the dashboard open Settings and find the Media Root field. Set it to the drive's mount path (the same path df -h shows for that drive), then on the box run: sudo sparkbox up That rebuilds the media apps against the drive and pre-creates the downloads and library folders. If the drive already holds library folders under different capitalisation, SparkBox links to them rather than moving anything. Two things that catch people: the path can't contain a space — SparkBox stops and prints the fix if it does — and make sure the mount is permanent in /etc/fstab. If it isn't mounted at boot, downloads quietly land on your system disk instead. — Chris
DravenB wrote:
Ok seems to have worked because so far I’m not getting any errors but thanks for all the help
Chris wrote:
Glad it's holding — and there's a proper ending to this one. Tom shipped v1.6.465 today and your report is one of the reports that closed it. The root cause was ours, not anything you did: when you completed Jellyfin's own setup screen yourself, the box kept a password Jellyfin had never accepted and showed it to you as your real login. That is what sent you round in circles for days. The seeding step now adopts the account you created instead. sudo sparkbox upgrade And if Settings - Service Passwords still lists a Jellyfin password that doesn't work, this saves the one you actually use: echo 'yourJellyfinPassword' | sudo sparkbox reset-password jellyfin --resync --user 'YourName' Thanks for sticking with it. -- Chris