2023-10-03, 07:48 PM
The functionality you want, not having to change URLs to get local access, is incompatible with using cloudflared tunnels.
If you DID NOT have cloudflared, many routers support a capability called "NAT Hairpin" or "NAT Loopback". If an outgoing requests resolves to your WAN IP, your router will keep the traffic local instead of going out to the web and then come back.
Because your public facing access is through the cloudflared tunnel, with your domain pointing to cloudflare, any requests to that domain HAVE to go out to cloudflare before coming back.
It sounds like you are already not using https. Even with cloudflared, your access to your jellyfin is only secure between your home and cloudflare. After it leaves cloudflare it is unencrypted.
To get the functionality you want, you will need to stop using cloudflared.
1) First determine if your router supports NAT hairpin/loopback. Without it, this isn't possible anyway.
2) Get a cert, setup https in nginx.
3) Turn off cloudflared and point your domain to your router's WAN IP.
If you DID NOT have cloudflared, many routers support a capability called "NAT Hairpin" or "NAT Loopback". If an outgoing requests resolves to your WAN IP, your router will keep the traffic local instead of going out to the web and then come back.
Because your public facing access is through the cloudflared tunnel, with your domain pointing to cloudflare, any requests to that domain HAVE to go out to cloudflare before coming back.
It sounds like you are already not using https. Even with cloudflared, your access to your jellyfin is only secure between your home and cloudflare. After it leaves cloudflare it is unencrypted.
To get the functionality you want, you will need to stop using cloudflared.
1) First determine if your router supports NAT hairpin/loopback. Without it, this isn't possible anyway.
2) Get a cert, setup https in nginx.
3) Turn off cloudflared and point your domain to your router's WAN IP.