Reverse Proxy HTTPS - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions) +--- Thread: Reverse Proxy HTTPS (/t-reverse-proxy-https) |
Reverse Proxy HTTPS - keduncan3 - 2024-05-09 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? RE: Reverse Proxy HTTPS - TheDreadPirate - 2024-05-09 Are you able to access port 8096 remotely? Or on the same LAN? If this is all on the same LAN, port forwarding does not apply and having a reverse proxy will not block port 8096 from being directly accessed on LAN. |