mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: API syncing errors after copying config from one server to another #5946
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 @tamuseanmiller on GitHub (Jun 6, 2024).
Please describe your bug
Recently switched from using Jellyfin in a docker container in a VM in Proxmox to using Jellyfin in docker in a privileged LXC in Proxmox. All I did was copy the config and compose file over and started it up. Everything seemed to work until I tried connecting it to other apps. The apps never seem to error they just don't pull data from the API. For example, Symfonium can't sync the music library at all from Jellyfin although it could play pre-existing music that was there but couldn't sync music. After removing it, it can't sync the new stuff. Same thing with Jellyseerr, it has all of the old stuff but anything new doesn't sync and update.
I should note that everything else works fine, playback is great, login works, transcoding is fine, even playing content through another media player is fine as long as that content was pre-existing and didn't need a sync. Any new content can't be played from third party sources.
Reproduction Steps
Not sure if this is truly reproducible as I haven't tried but all I did was copy the config files over from the VM to a priviledged LXC and start the new container. Most parts of the API seem to work fine, just the syncing mechanism.
Jellyfin Version
10.9.0
if other:
10.9.4
Environment
Jellyfin logs
Jellyfin Logs:
FFmpeg logs
FFmpeg Logs:
Please attach any browser or client logs here
N/A
Please attach any screenshots here
N/A
Code of Conduct
@jellyfin-bot commented on GitHub (Jun 6, 2024):
Hi, it seems like your issue report has the following item(s) that need to be addressed:
This is an automated message, currently under testing. Please file an issue here if you encounter any problems.
@tamuseanmiller commented on GitHub (Jun 7, 2024):
Fixed this by deleting the library database and letting it repopulate. Not an ideal fix though.