Comment on Issues with https certs locally
moonshine69@lemmy.nz 5 days ago
Not one correct answer here that i see…oof.
If you are doing a dns challenge then You need to give caddy access to your domain to perform the dns challenge. Depending on domain provider that is easy or hard. It will briefly change some records that tells let’s encrypt you own the domain and then issue the cert
Or you can do http challenge, this requires you to manually configure your domain to point to a publicly accessible caddy endpoint which is probably not what you want, ok if you do it briefly but not recommended unless you know what you’re doing
Who is your domain provider?
Spiffyman@slrpnk.net 3 days ago
I use porkbun and I do the DNS challenge. I know it succeeds because proxmox gets https perfectly fine. But none of my lxc containers get https after doing DNS challenges for them. Not sure what I am doing wrong since I clearly did it right at least once :/
moonshine69@lemmy.nz 3 days ago
Nice, ok hmm… sounds like you are using the router for internal DNS, did you set all the services to point at caddy?
Eg you could try a quick hack in hosts (assuming the caddy ip is 192.168.10.10)
And then navigate to one of the services over https
Main thing is all your internal DNS records need to point at caddy, and then it forwards to the real container IP
Not strictly required but could be worthwhile to get a dedicated internal dns server up… I use technitium, or there’s pi hole or a few other options …
Spiffyman@slrpnk.net 2 days ago
moonshine69@lemmy.nz 2 days ago
Nice :)