2024-05-09, 10:31 AM
Hello all,
I'm using Jellyfin in Docker on a Synology NAS 920+.
I have a reverse proxy setup using Synology's reverse proxy service. My question is why I can still access Jellyfin through the HTTP port.
Let's use the default ports for simplicity. I have port forwarding setup for 8920 to 8920. Then I have a reverse proxy setup pointing HTTPS 8920 to HTTP 8096. This way I don't have to mess with SSL certs in Jellyfin itself, it just uses my SSL cert I have assigned to my domain.
My question is, why can I still access Jellyfin through MyNas.com:8096 even though port forwarding isn't set up for this port?
I'm using Jellyfin in Docker on a Synology NAS 920+.
I have a reverse proxy setup using Synology's reverse proxy service. My question is why I can still access Jellyfin through the HTTP port.
Let's use the default ports for simplicity. I have port forwarding setup for 8920 to 8920. Then I have a reverse proxy setup pointing HTTPS 8920 to HTTP 8096. This way I don't have to mess with SSL certs in Jellyfin itself, it just uses my SSL cert I have assigned to my domain.
My question is, why can I still access Jellyfin through MyNas.com:8096 even though port forwarding isn't set up for this port?