2025-02-27, 01:43 PM
If you're going directly to port 8096, it would bypass Nginx.
Let's try this. Remove port publishing in Jellyfin. Reconfigure Nginx to proxy Jellyfin's bridge IP (172.16.0.6). Have ALL clients go to the domain address.
To improve the experience for local clients, you should enable NAT loopback if your router supports that. If not, most routers should allow you to add custom DNS entries. You would add a DNS entry to resolve your domain name to your host's LAN IP. I prefer just doing custom DNS entries, in general, so that my domain name still works for LAN clients if the Internet were to go out.
What we're trying to do is reduce the number of context changes that is going on for network traffic. Going from host network to bridge network to host network to bridge network, and then again in reverse.
Let's try this. Remove port publishing in Jellyfin. Reconfigure Nginx to proxy Jellyfin's bridge IP (172.16.0.6). Have ALL clients go to the domain address.
To improve the experience for local clients, you should enable NAT loopback if your router supports that. If not, most routers should allow you to add custom DNS entries. You would add a DNS entry to resolve your domain name to your host's LAN IP. I prefer just doing custom DNS entries, in general, so that my domain name still works for LAN clients if the Internet were to go out.
What we're trying to do is reduce the number of context changes that is going on for network traffic. Going from host network to bridge network to host network to bridge network, and then again in reverse.