• 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 SOLVED: Docker Container - Playback failed due to a fatal playback error

     
    • 0 Vote(s) - 0 Average

    SOLVED: Docker Container - Playback failed due to a fatal playback error

    pennywise134
    Offline

    Junior Member

    Posts: 14
    Threads: 4
    Joined: 2024 Nov
    Reputation: 0
    Country:Canada
    #1
    2025-02-21, 02:47 AM (This post was last modified: 2025-02-21, 03:11 AM by pennywise134. Edited 1 time in total.)
    I installed Jellyfin in a Docker container on my Beelink mini PC running Ubuntu. The installation itself appears to have been successful, I can configure and populate my libraries—but whenever I try to play a video file, I get the error:

    "Playback failed due to a fatal playback error."

    I previously had Jellyfin running successfully as a bare-metal install on the same machine, but I’m running into this issue with the Docker container.

    Has anyone encountered this before? What troubleshooting steps should I take? I've attached a log file for review.

    Thanks in advance for any help!

    CPU: i3 1220p
    RAM: 24GB DDR5
    OS: Ubuntu 24.04.2 LTS


    Attached Files
    .txt   log.txt (Size: 57.12 KB / Downloads: 32)
    Go to solution
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2025-02-21, 01:54 PM (This post was last modified: 2025-02-21, 01:55 PM by TheDreadPirate. Edited 1 time in total.)
    You checked "Allow encoding in AV1 format", which the i3-1220P does not support. It only support DEcoding AV1.

    This table on wiki will help you check the correct boxes. Use the Alderlake column.

    https://en.wikipedia.org/wiki/Intel_Quic...d_encoding
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    pennywise134
    Offline

    Junior Member

    Posts: 14
    Threads: 4
    Joined: 2024 Nov
    Reputation: 0
    Country:Canada
    #3
    2025-02-21, 03:22 PM (This post was last modified: 2025-02-21, 03:24 PM by pennywise134. Edited 1 time in total.)
    (2025-02-21, 01:54 PM)TheDreadPirate Wrote: You checked "Allow encoding in AV1 format", which the i3-1220P does not support.  It only support DEcoding AV1.

    This table on wiki will help you check the correct boxes.  Use the Alderlake column.

    https://en.wikipedia.org/wiki/Intel_Quic...d_encoding

    Would that cause a fatal playback error even if the files that are failing to play aren't in AV1 format? The files I'm trying to play are all HEVC.
    gnattu
    Offline

    Team Member

    Posts: 336
    Threads: 0
    Joined: 2024 Feb
    Reputation: 17
    #4
    2025-02-21, 03:41 PM
    > Would that cause a fatal playback error even if the files that are failing to play aren't in AV1 format? The files I'm trying to play are all HEVC.

    Yes. You are using a browser that reports av1 support but not hevc support (likely firefox) which caused server to transcode to av1 and that is the problem because your hardware does not have av1 hardware encoder. With that disabled the server will transcode to h264 instead.
    1
    pennywise134
    Offline

    Junior Member

    Posts: 14
    Threads: 4
    Joined: 2024 Nov
    Reputation: 0
    Country:Canada
    #5
    2025-02-21, 05:32 PM
    Yes. You are using a browser that reports av1 support but not hevc support (likely firefox) which caused server to transcode to av1 and that is the problem because your hardware does not have av1 hardware encoder. With that disabled the server will transcode to h264 instead.
    [/quote]

    I unchecked the "Allow encoding in AV1 format" box, and I'm still getting the fatal error. Any thoughts?

    I attached the ffmpeg log, let me know if there are any other log files I should gather.

    Also, here are the contents of my docker-compose.yml file:

    version: '3.8'
    services:
      jellyfin:
        image: jellyfin/jellyfin
        container_name: jellyfin
        restart: unless-stopped
        network_mode: "host"
        volumes:
          - ./configConfused-faceconfig
          - ./cacheConfused-facecache
          - /media/lucas/GOLDConfused-facemedia
        environment:
          - PUID=1000
          - PGID=1000
          - TZ=America/Toronto


    Attached Files
    .txt   FFmpeg.transcode.02.21.2025.txt (Size: 46.11 KB / Downloads: 54)
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #6
    2025-02-21, 06:22 PM
    Oh. You didn't pass the GPU into the container.

    https://jellyfin.org/docs/general/admini...ial-docker

    Both the device and the render group need to be passed into the container.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    pennywise134
    Offline

    Junior Member

    Posts: 14
    Threads: 4
    Joined: 2024 Nov
    Reputation: 0
    Country:Canada
    #7
    2025-02-21, 08:03 PM (This post was last modified: 2025-02-21, 08:03 PM by pennywise134.)
    (2025-02-21, 06:22 PM)TheDreadPirate Wrote: Oh.  You didn't pass the GPU into the container.

    https://jellyfin.org/docs/general/admini...ial-docker

    Both the device and the render group need to be passed into the container.


    Ahhh, yes my bad I missed that step. Thank you! I confirmed transcoding is working after adding the below to the yml file. Itseems to be working without passing the render group...is that step necessary?

    devices:
          - /dev/dri : /dev/dri
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #8
    2025-02-21, 08:26 PM
    Since you are running the container as root, no. If you wished to run the container as an unprivileged user, you would.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    pennywise134
    Offline

    Junior Member

    Posts: 14
    Threads: 4
    Joined: 2024 Nov
    Reputation: 0
    Country:Canada
    #9
    2025-02-21, 08:51 PM
    (2025-02-21, 08:26 PM)TheDreadPirate Wrote: Since you are running the container as root, no.  If you wished to run the container as an unprivileged user, you would.

    great, thank you very much for your help. I'm glad this is finally working!
    « 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