• 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 Networking & Access Connection to Jellyfin in Podman container

     
    • 0 Vote(s) - 0 Average

    Connection to Jellyfin in Podman container

    No access to web console, all logs and indicators look good.
    danseaman6
    Offline

    Junior Member

    Posts: 4
    Threads: 3
    Joined: 2023 Sep
    Reputation: 0
    Country:United States
    #1
    2024-05-17, 09:28 PM
    Using the Jellyfin documentation basically to the letter, I have a jellyfin podman container up and running. I can confirm it's running with podman ps and via the cockpit console on Fedora Server:

    Code:
    CONTAINER ID  IMAGE                              COMMAND    CREATED        STATUS                  PORTS                  NAMES
    172e8910e6b8  docker.io/jellyfin/jellyfin:latest              47 minutes ago  Up 47 minutes (healthy)  0.0.0.0:8096->8096/tcp  systemd-jellyfin

    Port 8096 is mapped. I can confirm this again with firewall-cmd:

    Code:
    >> sudo firewall-cmd --list-all
    FedoraServer (default, active)
      target: default
      ingress-priority: 0
      egress-priority: 0
      icmp-block-inversion: no
      interfaces: enp2s0
      sources:
      services: cockpit dhcpv6-client ssh
      ports: 8069/tcp
      protocols:
      forward: yes
      masquerade: no
      forward-ports:
      source-ports:
      icmp-blocks:
      rich rules

    However, I can't access the web console at http://192.168.x.x:8096 - it simply times out. Nothing in the container logs indicate anything wrong, likewise for the networking logs on the server machine itself. Any advice?
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2024-05-17, 09:31 PM (This post was last modified: 2024-05-17, 09:32 PM by TheDreadPirate.)
    You are probably using bridge networking, which means the container has its own IP. Use that instead.

    Or you could switch to host networking, then using the 192.168.X.X:8096 host address and port will work.
    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]
    fito
    Offline

    Junior Member

    Posts: 1
    Threads: 0
    Joined: 2024 May
    Reputation: 0
    Country:Guatemala
    #3
    2024-05-17, 10:36 PM
    you have opened the wrong port, you need to open port 8096, not 8069
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2024-05-18, 12:38 AM
    Good catch.
    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]
    « 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