3 ms·
I use a Digital Ocean vm as a public-facing reverse proxy with a Wireguard tunnel back to my homelab, where everything is actually hosted.
by tenacious_tuna 4y ago
I use a Digital Ocean vm as a public-facing reverse proxy with a Wireguard tunnel back to my homelab, where everything is actually hosted.
- codazoda 4y agoThat’s interesting. Do use a dynamic IP at home in this case or static? If it’s dynamic, what does the update process look like? Edit: It looks like this might be automatic. This is something interesting I should look into a bit. It’s probably just extra complexity for my little server, but I’ve got some uses in mind.
- dvdkon 4y agoI do something similar, the actual server connects to the tunnel VPS, not the other way around. The server doesn't actually have a public IP address.
- tenacious_tuna 4y agolike dvdkon says, only the VPS has a static public address, and my homelab reaches out to keep the tunnel alive. Tehcnically my homelab is also on a static public IP as well--this was more an exercise in "could I do this" than "actually necessary," but it's still cool as hell and I'm very happy. About the only hangup was I had to configure Wireguard to keep the tunnel alive, otherwise sometimes the VPS would receive incoming traffic and if my lab hadn't reached out in a while (which, why would it?) the tunnel would be down, and the proxy connection would die. Thankfully that's built-in functionality.