ianonavy
@ianonavy@lemmy.world
This is a remote user, information on this page may be incomplete. View at Source ↗
- Comment on Questions about TLS Passthrough. 1 year ago:
- The certificate and private key need to be on your home server since that’s where the TLS is decrypted.
- You should be able to tunnel TLS traffic through WireGuard, so no port forwarding is needed.
- You’d probably want to move Nginx Proxy Manager to your home server as an ingress gateway (and you can keep all the config + TLS certificates). Then on your VPS, you would no longer need the complexity and something like HAProxy, vanilla Nginx, or Traefik would suffice. Seems like NPM has an open issue to add support for TLS passthrough, but in my opinion it’s simpler to just have your VPS forward all traffic to one port on your home server.
For added security, you can make sure the proxy on the VPS only routes traffic for the correct domain using SNI. That way if someone hits your IP randomly, it only goes to your home server if the correct domain name was requested as well.
What you’re doing makes sense to me. Good luck!
- Comment on Welp that answers a lot of why all .ml are down 1 year ago:
The AT protocol that Bluesky runs on is designed to address this specific limitation of ActivityPub.