YurkshireLadI thought it would be easy enough to run a reverse proxy on my home server to access a local website using https. Oh boy was I wrong.
Human after all
quaff@YurkshireLad letsencrypt with dns01 challenge and a local DNS (or just using /etc/hosts on the client device). That's what ya need to get local HTTPS access 🫡
@quaff thanks. Trying to get Caddy + letsencrypt working with DNS-01 in docker.
@YurkshireLad ahhh I use nginx+docker myself. May look into Caddy at some point since it's all the rage. Sounds like it should be fairly straightforward. Looking forward to hearing how it turns out for ya!
@quaff so far not so well! Let’s encrypt is having trouble getting the certificate. I’m using the DigitalOcean module for Caddy.
@YurkshireLad I'm not sure how caddy handles it, but if there's no way to do a letsencrypt dns-01 challenge with caddy, might be easier to use certbot directly.
Steve@YurkshireLad nginx proxy manager worked well for me to do this. But I also do the same thing manually with nginx and letsencrypt on a vps too.
@heysteve maybe I’ll try Nginx manager. It’s for a local network, not a VPS. Https might be overkill for a server on my home network but I wanted to get https working.
@YurkshireLad right. I use the proxy manager on my local homelab. Makes life easier having real TLS certs.
@heysteve I got it working using nginx proxy manager within 10 minutes. Wow! Thanks for mentioning it.