My question: both boxes same problem SparkBox AI replied: If both boxes show the same error, this isn’t a browser or password issue. Both Jellyfin databases are failing the same /Users/Public query: text SQLite Error 1: no such column: p.PermissionPermissionsGuid The container reports healthy, but Jellyfin’s user database schema is incompatible with the running 10.11.11 image. That’s why the login page spins and SparkBox can’t resync the password. Don’t delete or manually edit either Jellyfin database. That risks losing users, libraries, and watch history. For each box, run: bash sudo docker inspect -f '{{range .Mounts}}{{println .Source "-" .Destination}}{{end}}' sb-jellyfin-media sudo docker image inspect jellyfin/jellyfin:10.11.11 --format '{{.Id}}' Then make a backup before changing anything: bash sudo sparkbox backup Because the same schema failure exists on both boxes, it needs the supported SparkBox/Jellyfin migration or image fix, not another password reset. Click Share to demox with the two error logs and the mount output. Tom needs to check why both databases are being opened by 10.11.11 without the expected permission column. The useful diagnosis is now clear: Docker is healthy, network access reaches Jellyfin, but Jellyfin’s SQLite user query fails internally. What I still need help with: (describe what didn't work or what's still broken)
9 replies
Seez wrote:
I’m facing the same issue! No idea how to fix it, but hoping Tom or someone will have a fix ASAP! 😲
Chris wrote:
I’m sorry, but the quoted AI reply treated an unverified SQLite error as if it were your confirmed error and sent you toward database inspection. Please do not delete or edit either Jellyfin database. For the one next check, on one affected box run sudo docker inspect sb-jellyfin-media --format '{{.Config.Image}} {{.State.Status}} {{if .State.Health}}{{.State.Health.Status}}{{end}}' and paste only that output, with no logs or credentials. The current SparkBox media pin is Jellyfin 10.11.11; the published rollback leaves a box already running 12.1 in place rather than silently downgrading it. I’ve corrected this diagnosis so an unsupported schema explanation is not repeated to the next person.
franciscus wrote:
jellyfin/jellyfin:10.11.11 running healthy
Chris wrote:
Thanks — a healthy jellyfin/jellyfin:10.11.11 container rules out the quoted AI reply’s unverified database-schema diagnosis. The published rollback also leaves a box already running 12.1 in place, so this is not a version mismatch on the box you checked. Please describe the exact visible problem on one box: does Jellyfin show a login page, spin indefinitely, or display an error? Paste only that message, without logs or credentials. I’ve corrected the diagnosis so an unsupported schema explanation is not repeated to the next person.
franciscus wrote:
Jellyfin shows the loginpage! image Sending a screenshot, the little blue part is a piece of the loop where it stalls. Tried other browser, no adblocks working.
Chris wrote:
Thanks — the screenshot shows Jellyfin reaching its login page and then stalling on the loading loop; it does not show the SQLite error quoted earlier. Because your container is healthy and running the tested 10.11.11 image, that database-schema diagnosis is not supported. Please do one check from the same home network: open Jellyfin directly using your SparkBox box's LAN IP followed by port 8096, rather than the dashboard/domain link. Tell me whether the direct page still stalls or reaches the normal login. I’ve corrected the earlier diagnosis so an unsupported database explanation is not repeated to the next person.
franciscus wrote:
Same error here, I have a domain connected(cloudflare) to the sparkbox, gives the same error
franciscus wrote:
Working again after update.
Chris wrote:
I'm glad the update restored Jellyfin on both boxes. That confirms the database-editing diagnosis quoted earlier was not the right path; please leave the Jellyfin databases unchanged. One check: after a normal page refresh, confirm that the login and the first screen still open normally. I've corrected what SparkBox support knows about this failure so the unsupported schema explanation is not repeated to the next person.