mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Macos - having same Jellyfin.Server.Migrations.JellyfinMigrationService issue as Linux users #7477
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PacoH on GitHub (Oct 21, 2025).
Description of the bug
I installed
jellyfin_10.11.0-amd64becausejellyfin_10.10.7-amd64, which had been working perfectly until I tried to scan all libraries yesterday, and newly added folders were not showing up in Jellycon on Kodi.I ran the new version and launched the Dashboard and when I again tried to scan all libraries, the app hung up at around 68% and I had no choice but to force quit the server.
When I again restarted the server and launched the Dashboard, I got
localhost refused to connect.ERR_CONNECTION_REFUSEDI tried to run version
10.10.7but now got the same error.I tried many 'fixes' for this error involving various caches, specifying the Port Forwarding TCP address, and many more, but nothing worked.
I looked at the log and found many entries for
Jellyfin.Server.Migrations.JellyfinMigrationServicethat indicated problems:Jellyfin.Server.Migrations.JellyfinMigrationService: Failed to apply migrations System.InvalidOperationException: Sequence contains no elementsSo apparently the new version managed to corrupt the database.
How can I recover from this without losing everything I have added over years?
Reproduction steps
Run Jellyfin app.
LaunchWhat is the current bug behavior?
localhost refused to connect.ERR_CONNECTION_REFUSEDWhat is the expected correct behavior?
Dashboard should open in browser.
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
There is no dashboard.
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@gnattu commented on GitHub (Oct 21, 2025):
I'm sorry but what you did probably already killed the db and if you did not do a backup, you have to remove all jellyfin data and start fresh
@theguymadmax commented on GitHub (Oct 21, 2025):
You can try this fist and see if you have any luck. In you Jellyfin data folder there should be folder call SQLiteBackups with (date)__jellyfin.db file. Rename it to jellyfin.db and replace the on in the data folder. Also in the data folder there will be a backup of the library.db called library.db.old. Also copy that and reaname to library.db to replace the one in the main folder. Then in your config folder find the migrations.xml.backup and copy and reaname to migrations.xml. to replace the one in the current config folder.
Then retry starting 10.10.7, no guarantee it's going to work, but you can give it a try. depending on how far along you were in the migration process it might work.
Key lesson, always have a backup.
@rama31244 commented on GitHub (Oct 22, 2025):
I'm having the same error, how do i restore from a backup?
@PacoH commented on GitHub (Oct 22, 2025):
Oh, don't worry, I looked for any db backups. There weren't any. Jellyfin is supposed to automatically backup data, isn't it? Also, why wouldn't a new version automatically backup the db before potentially trouncing it? A simple precaution that would prevent such a disaster.
I backed up and deleted
~/.local/sharejellyfinand~/.config/jellyfinand started the app and added just two current folders.After a lot of hassles with the primitive Kodi Jellycon "addon," I finally was able to see and play videos from the two libraries. It is now taking forever to finish re-adding the huge libraries but at least it is working.
@PacoH commented on GitHub (Oct 22, 2025):
Heh, if you're lucky enough to have a backup (I wasn't that lucky), it is straightforward:
Backup and Restore | Jellyfin
@JPVenson commented on GitHub (Oct 22, 2025):
Read this please: https://notes.jellyfin.org/ey1aBTshRZGM46PzkNaF0w?view#
@Koumbaya commented on GitHub (Oct 22, 2025):
I'm not sure if I should create another issue, but I'm having the same symptoms, however I had 10.11.0 running for like 12h without any problems (successful scan of the library etc) before that sudden migration issue, I'm not sure what caused that (or even the restart)
edit: okay, super weird but: deleted /config, restored the backup, put 10.10.7 on the docker-compose -> started fine. Then stopped docker, put 10.11.0 (to re-do the migration I guess) -> booted instantly to a fixed (AFAICS) 10.11.0. welp.