4 ms·
Get a cheap vps. Set it up as a wireguard server. Stick a barebones haproxy on it. Run it in tcp mode pointing at a wireguard client ip for the backend. Pick s
by ectospheno 4y ago
Get a cheap vps. Set it up as a wireguard server. Stick a barebones haproxy on it. Run it in tcp mode pointing at a wireguard client ip for the backend.
Pick some machine in your house. Make it a wireguard client connecting to the vps. Run whatever web server/app you want. Make sure your home router is running something like fq_codel.
Done. You don't need dynamic dns as your home client will just reconnect. Your ISP won't see any ports open because there aren't any. Your SSL certs and all data live in your house, not on the vps. There is nothing to backup at the vps except for yanking some logs.
- pflanze 4y ago> Stick a barebones haproxy on it. Run it in tcp mode pointing at a wireguard client ip for the backend. If you have just one backend server instance, you could also use a DNAT iptables rule instead, which would have the advantage of not hiding the originating IP from the backend. Or am I missing something?
- ectospheno 4y agoI'm assuming actual priority is keeping your home internet connection usable to your family. Easier to fail gracefully under configurable loads in the haproxy config. I'd rather enormous amounts of traffic never reach the house than try to handle it there.
- pflanze 4y agoThat's a good point, thanks!