Comment

Comment on NGINX config for TLS passthrough with multiple services?

MigratingtoLemmy@lemmy.world ⁨1⁩ ⁨year⁩ ago

Hi OP,

I don’t know how to do TLS pass-through, but I think you could just run NAT (configure the firewall on your VPS) and body your reverse proxy at home. No need for TLS pass-through in such a case, unless you absolutely need to host the proxy on the VPS.

Cheers

source

Sort:hotnew top

nutbutter@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago
I am not sure how to do that. Can you, please, link a guide or any documentation? Does this method prevent the VPS provider from looking into the data being passed through?

source
- MigratingtoLemmy@lemmy.world ⁨1⁩ ⁨year⁩ ago
  I don’t have any guide (haven’t looked for one). The concept is simple:
  
  Configure Wireguard server on the VPS.
  
  Connect to server using your router/home firewall as a client (I believe you’ve done this already).
  
  Configure nftables or iptables to forward traffic coming from a certain IP/port through your VPN connection to your router.
  
  Since you have hosted your proxy at home, that’s where TLS termination happens, which means your traffic is encrypted in transit (NAT does not decrypt packets). So yes, you’re (in theory) safe from the VPS provider.
  
  I believe there are ways to encrypt one’s RAM on a VPS but you likely don’t need it here, and that might be beyond the scope of this discussion anyway.
  
  Cheers. I was given this idea by another person on Lemmy, I’m just pushing this wonderful idea forward.
  
  source
  - nutbutter@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago
    I have configured WireGuard server on the VPS, yes. But I am not connecting to it using my router. I am just using a wg config file on my home server to connect to it. And do I configure nftables or iptables on the VPS? Because the traffic from my home server is already set to forward to the VPS using wireguard. The proxy is set up on the VPS, not home server. I cannot change any settings on my router because I am behind CGNAT.
    
    source
    MigratingtoLemmy@lemmy.world ⁨1⁩ ⁨year⁩ ago
    Well, it doesn’t matter if you configure the wireguard client on the router or the server.
    
    Running your proxy at home instead of on the VPS makes it possible for you to terminate SSL at home, inside your LAN, which means no need for TLS pass-throughs.
    
    nftables is recommended by Debian, but I suppose either one will work just fine.
    
    I’m asking you to configure NAT on your VPS so as to forward traffic from the wider Internet, through your VPS into your wireguard tunnel. Obviously, I’m assuming you’re following security practices on the VPS so as to not compromise your home network. The configuration you have on your server is fine, since that’s meant for outbound traffic.
    
    You can absolutely run a Wireguard client on your router, regardless of whether you are behind CG-NAT or not. It’s a different story if your router doesn’t even let you run extra software on top. That’s a different conversation.
    
    Cheers.
    
    source
    -> View More Comments