+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions)
+--- Thread: Unable to create/edit Library properly. (/t-unable-to-create-edit-library-properly)
Unable to create/edit Library properly. - DejaVu - 2025-10-26
- Fresh install of JellyFin 10.11.0
- Linux Docker using Docker Compose
I've got a few Libraries populated and working fine since my decision not to upgrade my JellyFin, but to install from fresh direct to 10.11.0. The update simply took too long.
The Libraries I originally created during setup are all working fine.
However, fast forward a few days and trying to create a new Library on the same setup, I get an annoying spinning circle on any type of Library creation. The original Libraries I can manipulate still.
I refresh the Admin backend only to be presented with the new Library having been created.
Checking said Library, the language and region I selected are not set. Clicking "Edit Images" = Spinning Circles.
Then, when playing around even more, trying to reconfigure the created Library, I get the attached - at which point, the only solution is to "Remove".
Which it does, leading back to square one (no new Library).
RE: Unable to create/edit Library properly. - HokieRulz - 2025-11-10
I'm having the exact same issue.
I did find that after I create a new library, if I then restart the LXC (I'm running on Proxmox - perhaps just restarting the Jellyfin service would be sufficient?),then manually initiate a library scan, and then the library shows up with content populated. In "Manage Library" it will finally show language and region correctly.
RE: Unable to create/edit Library properly. - CyberZeus - 2025-11-11
I encounter the exact same issue with Jellyfin 10.11.2 with a VM on Ubuntu Server 24.04.3 LTS x86_64.
I can't add new libraries.
Please see attached image (Test Library is the affected library, unable to scan or edit)
Thanks
Edit: restarting Jellyfin container after adding a new library solves the problem, but this is not the expected behavior...