Installed file browser, Can't find the login details. Can you help. Excellent software by the way, many thanks for this.
19 replies
tomspark wrote:
Found it — port mismatch. Your URL has :8089 but you put 8080 in the Port field. Sonarr ignores the URL's port; only the dedicated Port field matters. Fix: Host: 192.168.3.67 Port: 8089 URL Base: (leave blank) Use SSL: off Username: admin Password: (from /opt/sparkbox/state/qbittorrent-admin-password.txt) Category: sonarr The "Category" field is what I meant by label — when Sonarr hands a torrent to qBit, it tags it with this name so qBit picks the right save-path mapping. SparkBox's arr-bootstrap auto-creates sonarr and radarr categories, just type sonarr in lowercase. Hit Test. If it still fails, paste the exact error message.
tomspark wrote:
Sweet. Worth noting for anyone landing here later: the filebrowser DB-reset step in this thread is unrelated to the Sonarr→qBit port issue you hit — those were two separate problems that happened to surface in the same install. Holler back here if anything else trips you up.
tomspark wrote:
Easy fix — your FileBrowser password is in a file on the server. Run this: sudo cat /opt/sparkbox/state/filebrowser-admin-password.txt That prints your username + password. Username is admin, password is a random one we generated at install. Use those to log in at FileBrowser's web page.
Crom wrote:
I tried that on my system. I was having a similar issue. But when I used the credentials from the file on the server it said "Wrong credentials" Any suggestions? Thanks!
tomspark wrote:
Crom — quick check: try logging in with admin / admin (the default credentials). If THAT works, our password-rotation script never ran on your install. Force it now with: sudo rm -f /opt/sparkbox/state/filebrowser-initted && sudo /opt/sparkbox/scripts/filebrowser-init.sh Wait ~15 seconds and try the password from the file again. If admin/admin doesn't work either, paste the output of: sudo cat /opt/sparkbox/state/filebrowser-init.log and I'll dig in further from there.
Crom wrote:
Unfortunately, looks like neither option worked. - "Crom — quick check: try logging in with admin / admin (the default credentials). If THAT works, our password-rotation script never ran on your install." Same error message when attempting default credentials. - "Force it now with: sudo rm -f /opt/sparkbox/state/filebrowser-initted && sudo /opt/sparkbox/scripts/filebrowser-init.sh" Same error. Related the second solution: When running the script above is it supposed to change the previously generated password or is it keeping the randomly generated password and just updating the reference to it? If it was supposed to change it did not. Log output: sudo cat /opt/sparkbox/state/filebrowser-init.log [filebrowser-init] stopping sb-filebrowser briefly to release BoltDB lock... [filebrowser-init] running filebrowser users update admin --password ... [filebrowser-init] restarting sb-filebrowser... [filebrowser-init] WARN: users update returned exit 1: Unable to find image 'filebrowser/filebrowser:v2.31.2-s6' locally v2.31.2-s6: Pulling from filebrowser/filebrowser 0e623de493ae: Pulling fs layer 19f39f464468: Pulling fs layer 68c4ea3779b6: Pulling f [filebrowser-init] stopping sb-filebrowser briefly to release BoltDB lock... [filebrowser-init] running filebrowser users update admin --password ... [filebrowser-init] restarting sb-filebrowser... [filebrowser-init] WARN: users update returned exit 1: Unable to find image 'filebrowser/filebrowser:v2.31.2-s6' locally v2.31.2-s6: Pulling from filebrowser/filebrowser 19f39f464468: Pulling fs layer cc01b3dc062a: Pulling fs layer df25a931801a: Pulling f [filebrowser-init] stopping sb-filebrowser briefly to release BoltDB lock... [filebrowser-init] running filebrowser users update admin --password ... [filebrowser-init] restarting sb-filebrowser... [filebrowser-init] WARN: users update returned exit 1: I should also note, I tried the "clean slate" option for File Browser and the same situation
tomspark wrote:
Ah, the image pull is failing mid-password-update — that's the real issue. The script tries to run filebrowser users update inside a container but Docker can't pull the image. Try this instead: docker exec sb-filebrowser filebrowser users update admin --password newpassword123 Then log in with admin / newpassword123. If that works, we know the container's fine and it's just the init script's Docker-pull logic that's borked on your setup.
Crom wrote:
New error! ~$ docker exec sb-filebrowser filebrowser users update admin --password newpassword123 permission denied while trying to connect to the docker API at unix:///var/run/docker.sock I did do the setup as the root user as the instructions said. But if needed happy enough to uninstall and try again
tomspark wrote:
The permission denied while trying to connect to the docker API is because docker needs sudo. But before going down that path — let's confirm what's actually wrong with my earlier one-liner test first: In your browser, open FileBrowser's web page and try to log in with username admin and password admin (literally the word "admin" for both). That's the factory default. If admin/admin works → our password-rotation script didn't run on your install and we'll force it. If admin/admin DOESN'T work either → there's something else going on and I'll dig into the install log. Tell me which one you got.
Crom wrote:
Wrong credentials when trying the admin/admin combo! Let me know what else your need!
tomspark wrote:
OK so FileBrowser's DB has a third password we don't have access to. Let's force a clean re-rotation: sudo rm -f /opt/sparkbox/state/filebrowser-initted && sudo /opt/sparkbox/scripts/filebrowser-init.sh Wait about 30 seconds for it to finish, then try logging into FileBrowser's web page again with the password from /opt/sparkbox/state/filebrowser-admin-password.txt. If it still doesn't work after that, paste the last 20 lines of: sudo cat /opt/sparkbox/state/filebrowser-init.log That log will show whether the rotation actually succeeded this time or what step is failing.
Crom wrote:
[filebrowser-init] restarting sb-filebrowser... [filebrowser-init] WARN: users update returned exit 1: Unable to find image 'filebrowser/filebrowser:v2.31.2-s6' locally v2.31.2-s6: Pulling from filebrowser/filebrowser 19f39f464468: Pulling fs layer cc01b3dc062a: Pulling fs layer df25a931801a: Pulling f [filebrowser-init] stopping sb-filebrowser briefly to release BoltDB lock... [filebrowser-init] running filebrowser users update admin --password ... [filebrowser-init] restarting sb-filebrowser... [filebrowser-init] WARN: users update returned exit 1: ╔═════════════════════════════════════════════════════════════════�� [filebrowser-init] stopping sb-filebrowser briefly to release BoltDB lock... [filebrowser-init] running filebrowser users update admin --password ... [filebrowser-init] restarting sb-filebrowser... [filebrowser-init] WARN: users update returned exit 1: ╔═════════════════════════════════════════════════════════════════�� [filebrowser-init] stopping sb-filebrowser briefly to release BoltDB lock... [filebrowser-init] running filebrowser users update admin --password ... [filebrowser-init] restarting sb-filebrowser... [filebrowser-init] WARN: users update returned exit 1: ╔═════════════════════════════════════════════════════════════════�� [filebrowser-init] stopping sb-filebrowser briefly to release BoltDB lock... [filebrowser-init] running filebrowser users update admin --password ... [filebrowser-init] restarting sb-filebrowser... [filebrowser-init] WARN: users update returned exit 1: ╔═════════════════════════════════════════════════════════════════�� [filebrowser-init] stopping sb-filebrowser briefly to release BoltDB lock... [filebrowser-init] running filebrowser users update admin --password ... [filebrowser-init] restarting sb-filebrowser... [filebrowser-init] WARN: users update returned exit 1:
tomspark wrote:
Found it — and it's our bug. The s6 variant of FileBrowser's docker image is swallowing our users update command (the help banner you're seeing is the giveaway). Going to ship a fix in v1.6.87 in a few minutes. For right now — easiest reset since you can't log in anyway, so nothing to lose: sudo docker stop sb-filebrowser && sudo rm -f /opt/sparkbox/modules/files/config/filebrowser/database/filebrowser.db && sudo docker start sb-filebrowser Wait ~30 seconds. FileBrowser will create a fresh database with default credentials admin / admin. Log in with those, then immediately go to Settings → Users → admin → change password to something you'll remember. Done.
tomspark wrote:
Heads up — just shipped v1.6.87 with the proper fix for what Crom hit. The init script was using the s6-overlay variant of FileBrowser's image, which was swallowing our users update command (that ╔════ banner). v1.6.87 switches the one-shot CLI to the non-s6 variant so the args reach the binary. After sudo sparkbox update, future installs won't hit this. For Crom specifically, the manual reset I posted upthread (stop sb-filebrowser → rm filebrowser.db → start) gets you in immediately with admin/admin defaults if you haven't done it yet.
noliver2761 wrote:
I also encountered this problem and followed toms fix and it worked! However, not sure if related to this login credential bug but sonarr is giving me an authentication error? Sonarr is saying my login for qbittorrent is incorrect (i confirmed i was using the correct login) any ideas? I tried admin + admin and that didnt work either.
tomspark wrote:
That's a different bug — qBit's password isn't admin/admin in SparkBox, it's auto-generated at install. SSH in and grab it: sudo cat /opt/sparkbox/state/qbittorrent-admin-password.txt Then in Sonarr → Settings → Download Clients → qBittorrent: username admin, password that value. Hit Test, then Save. If Test still fails, paste the connection settings (URL, port, label — NOT the password) and we'll check the host/port side.
noliver2761 wrote:
yeah the pw i put in was correct :( also it worked perfectly fine when i first did it, just noticed radarr is having the same error! the only settings change i did between it working and not working was the fix you listed for the bug on this page sudo docker stop sb-filebrowser && sudo rm -f /opt/sparkbox/modules/files/config/filebrowser/database/filebrowser.db && sudo docker start sb-filebrowser but that shouldnt be related i think... i also was able to succssfully download an movie on radarr before this... here are the values! url sonarr http://192.168.3.67:8989 qbittorrent http://192.168.3.67:8089/ port 8080 label not sure what you mean by this
noliver2761 wrote:
It works! Thank you!
Crom wrote:
Just realized I never followed up on this. Thank you for your help!