Give every self-hosted service its own subdomain (reverse proxy 101)

There’s a moment in every homelab where you’re squinting at a sticky note that says :8096 is Jellyfin, :3000 is Grafana, :8123 is Home Assistant… and you realize this doesn’t scale. The fix — a reverse proxy giving each service its own subdomain — is the single biggest quality-of-life upgrade you can make. photos.yourdomain.net beats http://192.168.1.10:2342 in every way, and you get real HTTPS as a bonus. Here’s the whole mental model.

What a reverse proxy actually does

A reverse proxy is one program that listens on ports 80 and 443, looks at the hostname in each incoming request, and forwards it to the right internal service:

  • photos.yourdomain.net → the photos container on :2342
  • grafana.yourdomain.net → Grafana on :3000
  • home.yourdomain.net → Home Assistant on :8123

The browser only ever talks to the proxy, on standard ports, over HTTPS. The messy internal IPs and ports live entirely behind it. That’s the whole trick.

The three pieces you need

1. DNS that points the names somewhere. You need *.yourdomain.net (or individual records) resolving to your setup. Two common shapes:

  • Local-only: point the names at your proxy’s LAN IP using your router’s DNS or a Pi-hole. Nothing is exposed to the internet; the names only work at home.
  • Anywhere: point them at your public IP (or a Cloudflare-proxied record) and reach them from outside — or, better for privacy, keep DNS local and reach home over Tailscale. If a service really does have to be reachable from outside, there is a way to do it without opening a port.

A wildcard record (*.yourdomain.net) means you never touch DNS again — every new subdomain just works.

2. A reverse proxy. Nginx Proxy Manager, Traefik, or Caddy — each maps a hostname to an internal target and handles HTTPS. Pick by workflow; I compared them here.

3. TLS certificates, automatic. All three proxies get free Let’s Encrypt certificates for you. With a wildcard DNS record and a DNS-based challenge, you can even get one wildcard cert covering every subdomain, so a new service is instantly HTTPS with zero extra steps.

The payoff, concretely

Before: you memorize ports, type IP addresses, get browser security warnings, and can’t easily share a link. After: every service is a clean name.yourdomain.net with a padlock, new services take thirty seconds to expose, and you never think about a port number again.

A couple of gotchas

  • Don’t expose everything to the internet just because you can. Local-only DNS + Tailscale gives you subdomains and HTTPS without opening a single port — the safest default. Open ports only for the specific things that genuinely need public access.
  • Cache headers and HTTPS redirects are set at the proxy — one place to get right, and then every service inherits it.
  • Keep the proxy updated. It’s the one thing on the front line, so it’s the one thing worth patching promptly.

The short version

One reverse proxy + DNS for the names + automatic Let’s Encrypt = every service on its own tidy, HTTPS subdomain, and the end of the sticky-note-of-ports era. It’s an afternoon’s setup that pays off every single day you use your homelab afterward.