2024-03-10, 08:08 AM
(This post was last modified: 2024-03-10, 11:42 AM by User 7547. Edited 1 time in total.)
I recreated everything, included the IP in the configuration:
podman create --replace \
--label "io.containers.autoupdate=registry" \
--name jellyfin \
--publish 192.168.0.98:8096:8096/tcp \
--network server \
--user $(id -u server):$(id -g server) \
--group-add=$(getent group render | cut -d: -f3) \
--device /dev/dri/renderD128:/dev/dri/renderD128:rwm \
--volume jellyfin-cache:/cache:Z \
--volume jellyfin-config:/config:Z \
--mount type=bind,source=/var/my_data/home/server/jellyfin/media,destination=/media,ro=true,relabel=private \
docker.io/jellyfin/jellyfin:latest
podman create --replace \
--label "io.containers.autoupdate=registry" \
--name caddy \
--publish 192.168.0.98:80:80/tcp \
--publish 192.168.0.98:443:443/tcp \
--network server \
--user 0:0 \
--volume /var/my_data/home/server/caddy/Caddyfile:/etc/caddy/Caddyfile:Z \
--volume /var/my_data/home/server/caddy/caddy_data:/data:Z \
docker.io/serfriz/caddy-duckdns:latest
podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
cca2e1a54fe6 docker.io/jellyfin/jellyfin:latest 20 seconds ago Up 2 seconds (starting) 192.168.0.98:8096->8096/tcp jellyfin
1b0b7f7fa306 docker.io/serfriz/caddy-duckdns:latest caddy run --confi... 12 seconds ago Up 8 seconds 192.168.0.98:80->80/tcp, 192.168.0.98:443->443/tcp caddy
myhost.duckdns.org {
reverse_proxy 192.168.0.98:8096
tls {
dns duckdns MYTOKEN
}
}
Locally it is working, but when I try to reach it via https://myhost.duckdns.org/, just loading and eventually the connection time out:
I'm probably missing something with Caddy.
cat /etc/sysctl.conf
net.ipv4.ip_unprivileged_port_start=80
cat duck.log
OK
firewall-cmd --zone=public --add-port=443/tcp --permanent
firewall-cmd --zone=public --add-port=80/tcp --permanent
firewall-cmd --zone=public --add-port=8096/tcp --permanent
firewall-cmd --reload
podman create --replace \
--label "io.containers.autoupdate=registry" \
--name jellyfin \
--publish 192.168.0.98:8096:8096/tcp \
--network server \
--user $(id -u server):$(id -g server) \
--group-add=$(getent group render | cut -d: -f3) \
--device /dev/dri/renderD128:/dev/dri/renderD128:rwm \
--volume jellyfin-cache:/cache:Z \
--volume jellyfin-config:/config:Z \
--mount type=bind,source=/var/my_data/home/server/jellyfin/media,destination=/media,ro=true,relabel=private \
docker.io/jellyfin/jellyfin:latest
podman create --replace \
--label "io.containers.autoupdate=registry" \
--name caddy \
--publish 192.168.0.98:80:80/tcp \
--publish 192.168.0.98:443:443/tcp \
--network server \
--user 0:0 \
--volume /var/my_data/home/server/caddy/Caddyfile:/etc/caddy/Caddyfile:Z \
--volume /var/my_data/home/server/caddy/caddy_data:/data:Z \
docker.io/serfriz/caddy-duckdns:latest
podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
cca2e1a54fe6 docker.io/jellyfin/jellyfin:latest 20 seconds ago Up 2 seconds (starting) 192.168.0.98:8096->8096/tcp jellyfin
1b0b7f7fa306 docker.io/serfriz/caddy-duckdns:latest caddy run --confi... 12 seconds ago Up 8 seconds 192.168.0.98:80->80/tcp, 192.168.0.98:443->443/tcp caddy
myhost.duckdns.org {
reverse_proxy 192.168.0.98:8096
tls {
dns duckdns MYTOKEN
}
}
Locally it is working, but when I try to reach it via https://myhost.duckdns.org/, just loading and eventually the connection time out:
I'm probably missing something with Caddy.
cat /etc/sysctl.conf
net.ipv4.ip_unprivileged_port_start=80
cat duck.log
OK
firewall-cmd --zone=public --add-port=443/tcp --permanent
firewall-cmd --zone=public --add-port=80/tcp --permanent
firewall-cmd --zone=public --add-port=8096/tcp --permanent
firewall-cmd --reload