+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: Connection to Jellyfin in Podman container (/t-connection-to-jellyfin-in-podman-container)
Connection to Jellyfin in Podman container - danseaman6 - 2024-05-17
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-jellyfinPort 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 rulesHowever, 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?
RE: Connection to Jellyfin in Podman container - TheDreadPirate - 2024-05-17
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.
RE: Connection to Jellyfin in Podman container - fito - 2024-05-17
you have opened the wrong port, you need to open port 8096, not 8069
RE: Connection to Jellyfin in Podman container - TheDreadPirate - 2024-05-18
Good catch.