Hey Everyone, I'm seeming to have a database write permission error for some reason. Sparkbox Doctor reports no errors, I "clean slate" and removed the app then reinstalled. Restarted the container, rebuilt etc and it still seems to have an issue. I will say it was working fine about a day or so ago and now it's not. I don't think i've changed anything to make this happen but who knows at this point. Any help is appreciated! |\2026-06-03T23:08:24.334919740Z 2026/06/03 23:08:24 Using config file: /config/settings.json \2026-06-03T23:08:24.335029446Z 2026/06/03 23:08:24 Using database: /database/filebrowser.db W2026-06-03T23:08:24.335050303Z Error: open /database/filebrowser.db: permission denied \2026-06-03T23:09:25.035398335Z 2026/06/03 23:09:25 Using config file: /config/settings.json \2026-06-03T23:09:25.035574323Z 2026/06/03 23:09:25 Using database: /database/filebrowser.db W2026-06-03T23:09:25.035639918Z Error: open /database/filebrowser.db: permission denied \2026-06-03T23:10:25.746461047Z 2026/06/03 23:10:25 Using config file: /config/settings.json \2026-06-03T23:10:25.746558029Z 2026/06/03 23:10:25 Using database: /database/filebrowser.db W2026-06-03T23:10:25.746716397Z Error: open /database/filebrowser.db: permission denied
4 replies
tomspark wrote:
That error means File Browser can't write its database file — the folder it lives in ended up owned by the wrong user (your "clean slate" reinstall most likely recreated it as root). Quick fix — hand the folder back to the right owner and restart: sudo chown -R 1000:1000 /opt/sparkbox/modules/files/config/filebrowser sudo sparkbox restart files (If your SparkBox lives somewhere other than /opt/sparkbox, swap that path accordingly.) That should stop the crash loop and let File Browser open its database again. If it comes BACK after an app update, tell me — that would tie it to the update/rollback issue you flagged on your other thread, and I'd want to chase them together.
Big_Totoro wrote:
Hey Tom, "If it comes BACK after an app update, tell me — that would tie it to the update/rollback issue you flagged on your other thread, and I'd want to chase them together." It did come back and I still am having the issue with all the apps showing they need an update, but then rolling back. Thanks!
tomspark wrote:
Thanks for the update — that's a useful clue. File Browser breaking again right when your apps were stuck in that 'update, then roll back' loop tells me the two are linked: the rolled-back update is most likely leaving that folder owned by the wrong user again. Two things would help me chase it. First, run the update from SSH instead of the dashboard button — sudo sparkbox update — it heals more than the in-app button does. Second, right after it rolls back, copy the last 30 or so lines it printed and paste them here. That shows me exactly what's failing the update so I can stop the loop at the source.
Big_Totoro wrote:
Hey Tom, "run the update from SSH instead of the dashboard button" this fixed it for me. From now on I'm going to update/upgrade from the console.