Jellyfin Forum
connection failure with some repo unavailable and database issues in the logs - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: connection failure with some repo unavailable and database issues in the logs (/t-connection-failure-with-some-repo-unavailable-and-database-issues-in-the-logs)



connection failure with some repo unavailable and database issues in the logs - Unseen9715 - 2025-03-14

Hi guys,

for the last 2 days i've been trying to figure out what's wrong with my Jellyfin Docker but i'm lost, so I ask for your help.

My setup is jellyfin running in a docker container on my unraid server, everything was working fine and then all of a sudden i cannot access it anymore. I've tried restoring a backup of the appdata from when i know it worked as well as re-install the container but nothing has worked. 

after starting the container the only error I see is something in the logs point to not being able to access https://repo.codyrobibero.dev/manifest.json

the server works and is accessible up to the login screen, but then when i try to log in it throws some SQlite errors "attempt to write to readonly database" in the logs and gives "Connection Failure. We're unable to connect to the selected server right now. Please ensure it is running and try again." in the browser

Any ideas on how I can resolve this? i've attached the logs in a txt file.

cheers
Michael


RE: connection failure with some repo unavailable and database issues in the logs - TheDreadPirate - 2025-03-14

That connection error wouldn't prevent the server from starting, but the database error would. If I had to guess, Jellyfin itself is fine but the playback reporting plugin, which has its own database, is corrupt. Rename or delete the playback reporting plugin's database file.

In the directory you mounted /config, go to /config/data/ and rename or delete playback_reporting.db.

Then start the container.