Exposing my homelab over WireGuard
Published June 24, 2026, 2:03 p.m. by wielandtech
The usual way to put a self-hosted site on the internet is to forward 80 and 443 on your home router to the cluster. I didn't want to do that. It puts my home IP in public DNS and leaves a permanent hole in the router pointing straight at my nodes.
The other easy option is a Cloudflare Zero Trust tunnel. It's free, it works, and half the homelab subreddit uses it. But I spent a whole blog post talking about not depending on the big providers, and routing every request through Cloudflare would make that post a little awkward.
So instead, every public hostname (the apex, dev, qa, and the *.review wildcards) points at a $5 DigitalOcean droplet. The droplet takes whatever comes in on 80 and 443 and pushes the raw TCP down a WireGuard tunnel to my UniFi gateway, which hands it to Traefik in the cluster. The gateway dials out to the droplet, so my router has zero inbound ports open.
# home gateway -> VPS, roughly
[Peer]
PublicKey = <droplet-public-key>
Endpoint = <droplet-ip>:51820
AllowedIPs = 10.12.12.1/32
On the droplet it's about ten lines of stream proxy: 443 goes to 10.12.12.2:443 and 80 to 10.12.12.2:80, passthrough only. TLS terminates at home, where cert-manager keeps the certs. The droplet never sees anything but ciphertext, so if someone roots it they get a pipe that goes one place. Even the Let's Encrypt HTTP-01 challenges come in through the tunnel like normal traffic, which was satisfying to watch.
Downsides, since there are some. Every public byte now takes a detour through one small VPS, which is fine for a personal site and a few dashboards but wouldn't be for video. If the droplet or tunnel goes down, nothing is reachable from outside, even though everything is still running fine on the LAN. The provider can't read my traffic, but they can still see how much of it there is and where it comes from.
And the droplet is the one piece of all this that isn't in GitOps. Every app, cert, and firewall rule in the cluster is in a repo, while the VPS proxy config lives on the VPS and in my head. Terraform and cloud-init are next on the list. They've been next on the list for a while.
Still, for one extra hop and five bucks a month my router's inbound list is empty and nobody's DNS has my home IP in it. I'll take that.
Please log in to add a comment.