1. Reverse‑proxy wars
The discussion is dominated by the choice of reverse‑proxy software.
- Caddy is praised for its “simple and straightforward” configuration, but some users complain about its plugin model and distributed‑config pain:
“Caddy is increasingly popular… I use both and cannot decide which I prefer.” – verdverm
“The pain I've had with it is distributed configuration… I use the JSON API rather than their DSL.” – verdverm
- Traefik is lauded for its “plug‑and‑forget” nature, especially in Kubernetes:
“Traefik is so easy to plug in and forget about.” – windexh8er
- Nginx remains a staple for its mature ecosystem, though its “if” directive can be troublesome:
“I use nginx for homelab things because my use‑cases are simple, but I've run into issues at work with nginx in the past because of the above.” – philsnow
2. DNS & subdomain plumbing
Getting local services reachable via friendly names is a recurring theme.
- Tailscale’s built‑in DNS and “tailscale serve” are highlighted as a quick solution:
“You can use tailscale services to do this now.” – domh
- Custom DNS (Pi‑Hole, AdGuard, bind9) is recommended to keep traffic internal and avoid ISP loopback problems:
“Also recommending using a DNS server that points*.yourdomainto your reverse proxy’s IP.” – c‑hendricks
- Cloudflare tunnels are mentioned as an alternative, though bandwidth limits are a concern:
“Tunnels go through Cloudflare infrastructure so are subject to bandwidth limits.” – QGQBGdeZREunxLe
3. Hardware, power, and cost
Participants weigh the trade‑offs between performance, energy use, and budget.
- Old gaming PCs or laptops are often repurposed for homelabs:
“I’ve been thinking of tearing down my old gaming desktop … and using a 2014 Macbook Pro instead.” – hparadiz
- Power consumption is a real cost driver:
“My server is costing me about $100/month in electricity costs.” – leptons
“The setup mentioned in the article has an avg 600 kWh/year … HP EliteDesk uses 100