Error logging into Jellyfin for the first time
Posted by Wolf21
My question: Provide an error summary for demox SparkBox AI replied: Demox error summary System - SparkBox modules enabled: core, dashboard, media - Jellyfin container: sb-jellyfin-media - Image: jellyfin/jellyfin:10.11.11 - Container state: running and healthy - Restart policy: always - Host port: 8096 - Media mount: /home/joel/shares/arr-media:/data - Jellyfin config mount: /opt/sparkbox/modules/media/config/jellyfin:/config User scenario - First Jellyfin setup. - No real media has been added or configured yet. - The issue occurs before media-library configuration. - Port 8096 responds, but the Jellyfin web UI returns a connection error / cannot complete the setup or login request. Relevant log errors text SQLite Error 1: 'no such column: p.PermissionPermissionsGuid' Affected requests include: text GET /users/public POST /Users/authenticatebyname Additional log entries: text Failed executing DbCommand An exception occurred while iterating over the results of a query context type 'Jellyfin.Database.Implementations.JellyfinDbContext' Migration-related entries: text Jellyfin version: 10.11.11 There are 0 migrations for stage PreInitialisation. There are 0 migrations for stage CoreInitialisation. There are 0 migrations for stage AppInitialisation. Current assessment - Jellyfin’s HTTP endpoint is reachable. - The failure occurs while querying the SQLite database, not because the media folder …(reply truncated — full chat sent to Tom)
2 replies
Wolf21 wrote:
Fixed it on my own... (Sparkbox AI was going to have me start editing all kinds of things that my gut told me it wasn't correct) The Fix: 1) edited .env to add "JELLYFINVERSION=12.0" at the bottom. Saved and exited file 2) in a terminal, ran: sparkbox up media and waited until everything settled down and appeared all green in the dashboard. 3) connected to http://192.168.170.20:8096 using the credentials from sparkbox. Log in was successfull (never did run through the initial startup, but I'm in.
Chris wrote:
I'm sorry the earlier AI response treated an unverified SQLite message as your diagnosis and was about to send you toward database edits. The true issue was the Jellyfin data and image not agreeing; access returning after the compatible image was used is consistent with that, and you should not edit or delete the database. One check: please refresh Jellyfin and confirm that the login still opens normally without making any more database or compose-file changes. I've corrected what SparkBox support knows about this path so unsupported database-editing advice is not repeated to the next person.