• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Problem with upgrade and configuration

     
    • 0 Vote(s) - 0 Average

    Problem with upgrade and configuration

    v0rt
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Aug
    Reputation: 0
    Country:France
    #1
    2025-08-19, 06:43 PM
    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.
    bitmap
    Offline

    Community Moderator

    Posts: 1,062
    Threads: 9
    Joined: 2023 Jul
    Reputation: 30
    #2
    2025-08-20, 12:26 AM
    Can you post your compose file?
    Jellyfin 10.10.7 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage

    [Image: AIL4fc84QG6uSnTDEZiCCtosg7uAA8x9j1myFaFs...qL0Q=w2400]
    v0rt
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Aug
    Reputation: 0
    Country:France
    #3
    2025-08-20, 08:07 AM (This post was last modified: 2025-08-20, 08:08 AM by v0rt.)
    Code:
    version: "3.7"

    services:
      jellyfin:
        container_name: jellyfin
        image: jellyfin/jellyfin:latest

        restart: unless-stopped
        privileged: true
        ports:
          - "8096:8096"
          - "8920:8920" 
        volumes:
          - /data/media/movies:/media/Movies
          - /data/media/series:/media/Series
          - /data/media/music:/media/Music
          - /data/anime:/media/Anime
          - /mnt:/media/Transcode
          - data:/config
          - data:/cache



        environment:
          - TZ="Europe/Paris"
          - NVIDIA_VISIBLE_DEVICES=all
        runtime: nvidia
        deploy:
          resources:
            reservations:
              devices:
                - capabilities: [gpu]
       

    volumes:
      data:
    visualblind
    Offline

    Junior Member

    Posts: 24
    Threads: 4
    Joined: 2023 Sep
    Reputation: 0
    Country:United States
    #4
    2025-08-20, 08:19 AM (This post was last modified: 2025-08-20, 08:34 AM by visualblind. Edited 3 times in total.)
    (2025-08-20, 08:07 AM)v0rt Wrote:
    Code:
    version: "3.7"
        volumes:
          - data:/config
          - data:/cache
    volumes:
      data:

    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:
          - config:/config
          - cache:/cache
    volumes:
      config:
      cache:


    My recommendation is to read the docs completely, then start over from scratch.
    v0rt
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Aug
    Reputation: 0
    Country:France
    #5
    2025-08-20, 08:37 AM
    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.
    v0rt
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Aug
    Reputation: 0
    Country:France
    #6
    2025-09-01, 02:40 PM
    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
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode