Hi

I started setting up a Jellyfin server for friends to allow them watch remotely after the recent changes from Plex.

The experience so far isn’t great. Jellyfin seems to have many advanced features than Plex but the essential ones do not work that well.

The library scan took 3 hours for around 6k files. Plex takes much less time than that. There are many people raising this issue for years now but it is still not fixed.

From the logs I see Jellyfin trying to extract images for chapters even though the option isn’t checked. I already found reports for such issues but they are closed without an answer.

The big problem for me is Jellyfin not starting and getting stuck (without meaningful logs) at startup each time the server is shutdown. I did the reinstall 5 times now and trying the native install now. From the debug logs it seems like Jellyfin is stuck on one sql query.

From what I have seen, many issues are getting closed because of non activity even when the issue is still there.

I know that the project is done by volunteers but I was just wondering whatever I should invest more time on trying to resolve the issues. Maybe my server specs are just not ideal for Jellyfin.

  • Underwire@lemmy.worldOPEnglish
    2·
    14 days ago

    I started with docker install, first using the LinuxSever image and then the official image.

    Now I tried the native install and will see tomorrow if it is still OK.

    I am using Ubuntu.

    • sabreW4K3@lazysoci.alEnglish
      2·
      14 days ago

      Can you post your docker-compose.yaml so I can compare it to mine please. Make sure you obfuscate your IP addresses and ports.

      • Underwire@lemmy.worldOPEnglish
        2·
        13 days ago

        It is really a standard config

        services:
  jellyfin:
    image: jellyfin/jellyfin:10.10.7
    container_name: jellyfin
    user: 30000:30002
    environment:
      - PUID=30000
      - PGID=30002
      - TZ=Etc/UTC
    volumes:
      - /media/WD/tools/Jellyfin/config:/config
      - /media:/media
    ports:
      - 8096:8096
    restart: unless-stopped
        • sabreW4K3@lazysoci.alEnglish
          1·
          13 days ago

          Where does that user: 30000:30002 come from?

          Also that PUID/PGID seems wrong for a standard config.

          Here’s mine:

          jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - /opt/jellyfin/config:/config
      - films:/data/movies
      - tv:/data/tvshows
      - jellyfinmeta:/config/metadata
    ports:
      - 8096:8096
    restart: unless-stopped

          Try dropping the user and changing your PUID and PGID back to 1000 and see how you get on.

          • Underwire@lemmy.worldOPEnglish
            2·
            13 days ago

            user and PUID, PGID do the same thing and not all images support PUID and PGID. They tell docker to run the image using the user with those id. My user has ID 30000 and group 30002. This allows me to change files on my library with this user without causing permissions issues for jellyfin.

            • sabreW4K3@lazysoci.alEnglish
              1·
              13 days ago

              I would start the investigation there.

              I’m running my Jellyfin on a Raspberry Pi, and it runs like a dream, so there’s definitely a config issue afoot.

              • Underwire@lemmy.worldOPEnglish
                1·
                13 days ago

                Investigate what? That is a standard config and didn’t change anything. Your Raspberry Pi is maybe more powerful than my server. How big is your library?