SOLVED: Accessing Jellyfin in Docker Compose using Native Caddy and DuckDNS. Can't open ports

[jellykrabbypatty]

Have you run a port checker, that port 443 is open and forwarded to the device running Caddy? It has to be open for Caddy to work.

Portchecker.co says 443 and 80 are closed for external public IP address linked to duckdns. I have 443, 80, and 8096 configured to run through Linux UFW and have tested that works because 8096 was closed and none of my Jellyfin stuff was working. Now it is open and it is back to working locally. 

In Netgear router settings, I go to Advanced, Advanced Setup, Port Forwarding/PortTriggering, and have two services. 

One for HTTP with external start point 80, external end point 80, internal start port 80, and internal end port 80. I have that set for internal ip address which is my 192.168.xx.xx computer IP address (not the public facing one).

The other for HTTPS with external start point 443, external end point 443, internal start port 443 and internal end port 443. I have that set for internal ip address which is my 192.168.xx.xx computer IP address (not the public facing one).

In the Jellyfin GUI, I have "allow remote connections" checked in Networking, and everything else is left to default.  

EDIT: My Caddyfile is    

subdomain.duckdns.org {  
reverse_proxy localhost:8096
} 

EDIT EDIT: My router has a setting called VLAN / Bridge Settings, and a checkbox that says "Enable VLAN / Bridge Setup". Does that put it in bridge mode?