pyrosis , 2 months ago

I use using docker networks but that’s me. They are created for every service and it’s easy to target the gateway. Just make sure DNS is correct for your hostnames.

Lately I’ve been optimizing remote services for reverse proxy passthru. Did you know that it can break streams momentarily and make your proxy work a little harder if your host names don’t match outside and in?

So in other words if you want full passthru of a tcp or udp stream to your server without the proxy breaking it then opening a new stream you would have to make sure the internal network and external network are using the same fqdn for the service you are targeting.

It actually can break passthru via sni if they don’t use the same hostname and cause a slight delay. Kinda matters for things like streaming videos. Especially if you are using a reverse proxy and the service supports quic or http2.

So a reverse proxy entry that simply passes without breaking the stream and resending it might ook like…

Obviously you would need to get the http port working on jellyfin and have ipv6 working with internal DNS in this example.

<span style="color:#323232;">server {
</span><span style="color:#323232;">    listen 443 ssl;
</span><span style="color:#323232;">    listen [::]:443 ssl;  # Listen on IPv6 address
</span><span style="color:#323232;">
</span><span style="color:#323232;">    server_name jellyfin.example.net;
</span><span style="color:#323232;">
</span><span style="color:#323232;">    ssl_certificate /path/to/ssl_certificate.crt;
</span><span style="color:#323232;">    ssl_certificate_key /path/to/ssl_certificate.key;
</span><span style="color:#323232;">
</span><span style="color:#323232;">    location / {
</span><span style="color:#323232;">        proxy_pass https://jellyfin.example.net:8920;  # Use FQDN
</span><span style="color:#323232;">        ...
</span><span style="color:#323232;">    }
</span><span style="color:#323232;">}
</span>