Thanks for the advice, I didn’t know a reverse proxy was what I was setting up though I’ve seen that term all over. I think Caddy is likely in my future but I already have basic access to my home network through a Wireguard tunnel for now so I was hoping dnsmasq could solve for my case without getting too fancy or exposing any ports. I think I should probably try to learn about reverse proxies more generally to figure out the next steps forward.
Comment on What's up, selfhosters? - The Sunday thread
kitnaht@lemmy.world 5 weeks agoHighly suggest putting Caddy on a machine, forwarding port 443 and 80 to caddy, and then letting it do your reverse-proxy stuff. Register a domain name, give it your IP address, and then tell caddy that ‘immich.yourdomain.bleh’ goes to port 78789 and plex goes to ‘media.yourdomain.bleh’ port 89898 – Caddy handles all of the TLS stuff, handshaking, you name it - so you can have secure sites with proper certs.
Then make sure those things are isolated from your home network through vlans if your router supports it.
You can get fancier with it using a tailscale and getting some datacenter IP to forward into your network
FunkFactory@lemmy.world 5 weeks ago
sugar_in_your_tea@sh.itjust.works 5 weeks ago
I set up DNS challenge with Let’s Encrypt with Caddy, and now I don’t need to forward anything to it if I don’t want to.
azron@lemmy.ml 5 weeks ago
DNS challenge so you can get a wildcard cert? Or is it still per domain? I haven’t looked recently but it seemed difficult but I’d like to avoid transparency log installs where I can.
sugar_in_your_tea@sh.itjust.works 5 weeks ago
You can do both (not sure how wildcard works through Caddy though), I did it per domain. I prefer doing TLS trunking per device, hence to wildcard.