![]() |
Problem with upgrade and configuration - 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: Problem with upgrade and configuration (/t-problem-with-upgrade-and-configuration) |
Problem with upgrade and configuration - v0rt - 2025-08-19 Hi, Version: Actualy 10.10.7 Installation: Docker and Portainer for deploy on Ubuntu 25.04 Description: I'm having some issues with my Jellyfin instance that I can't seem to resolve. When the Docker image is updated (sometimes): - I lose the media libraries, but the files are still accessible from the interface; the update, however, when there's new media, no longer works. - I lose the extensions, extension repositories, and configuration. - Sometimes, after the update, it tells me that the server doesn't exist, and I have to reconnect. I've already done multiple reinstallations from scratch, but I find it's starting to get overwhelming and quite annoying. I've tried the recommended mount points, I've tried hard-setting more points, I've tried numerous solutions, and I can't seem to resolve this issue. Do you have any leads? Thank you in advance for your help. RE: Problem with upgrade and configuration - bitmap - 2025-08-20 Can you post your compose file? RE: Problem with upgrade and configuration - v0rt - 2025-08-20 Code: version: "3.7" RE: Problem with upgrade and configuration - visualblind - 2025-08-20 (2025-08-20, 08:07 AM)v0rt Wrote: For one thing you are never suppose to use the same volume for both the /config and /cache internal directories. I believe the official recommendation is to use bind mounts for the config/cache directories. The way you're doing it now is letting Docker obfuscate that away and it sounds like there's a problem regarding the containers ability to properly read the config files (most likely since you're using a single volume for both /config and /cache) since you stated your instance looses that information upon upgrading. If you are hell-bent on using docker volumes instead of bind mounts, then use a different volume for each path: Code: volumes: My recommendation is to read the docs completely, then start over from scratch. RE: Problem with upgrade and configuration - v0rt - 2025-08-20 Okay, I can try that and see if it works better. All my containers work in bulk, only the Jellyfin one is giving me problems. I'll try the recommended method, even though I think I've already tried it. I'll give it a try and let you know. RE: Problem with upgrade and configuration - v0rt - 2025-09-01 Hi! It took me a while to re-configure, but I feel like it's working much better! I already feel smoother when browsing, reading, and everything else, and my plugins are finally working properly, and the media library isn't getting deleted. So, for me, everything's fine ! Thanks |