This is the solution I went with. Had to tinker a bit with the KeepAlive settings, but otherwise smooth sailing now! Thanks!
Comment on Spectrum Community WiFi
SomethingBurger@jlai.lu 1 year ago
Use Wireguard or whatever to create a VPN between your home and your VPS, put a reverse proxy to route all incoming requests to your home server, and point your domain to the VPS.
tgrowl@lemmy.world 11 months ago
Oisteink@feddit.nl 1 year ago
You can use a reverse proxy for TCP and HTTP(s), and do port forwarding for other services.
OpenVPN can be bridged as well so all devices attached to your ap/router can be on the same broadcast. I’d rate this as fairly advanced but it’s possible. See here for details
tgrowl@lemmy.world 11 months ago
So I think I’m running into this problem a bit now. The reverse proxy and everything TCP and HTTPS works. The mail server I’m still trying to figure out. I’m using Wireguard to tunnel, do you know how to “bridge” that up to the VPS so that ports I need open to listen for incoming SMTP are also being listened on on the VPS?
Oisteink@feddit.nl 11 months ago
WireGuard don’t do bridge. But smtp is tcp on port 25 and can go though proxy.
Note: you’ll need a ptr record for your VPS IP, not all providers allow this. You’ll also need to make sure your vps provider don’t block port 25. (like digital ocean)
What’s your current setup? VPS with reverse proxy and WireGuard to your home server/network?
I tend to use haproxy and would just add a tcp frontend on port 25 and have the backend point to my home-server WireGuard IP and the port I run my smtp server. Or the local ip - if your lan subnet is in the allow section of what config on the VPs side