Then why did you comment? 😂
Comment on Anyone use Caddy w Porkbun here? Looking for help after updating Caddy…
sxan@midwest.social 1 month ago
I’ve never heard of Porkbun, but it doesn’t sound like a caddy issue. Let’s Encrypt requires being able to resolve the DNS name you’re requesting a cert for, and to be able to connect to your web service and fetch a secret to prove you own the domain. If porkbun does something like punch a hole in your LAN firewall and let in http traffic, then porkbun is the problem. Not Caddy.
just_another_person@lemmy.world 1 month ago
sxan@midwest.social 1 month ago
Because they were wondering if it was a Caddy issue, and I’ll bet real money it isn’t.
Being able to exclude components from being a possible source of the issue is critical to problem solving.
sugar_in_your_tea@sh.itjust.works 1 month ago
This part isn’t true, you can use DNS challenge and they don’t need to connect to your service. I have several services on my LAN that have never been accessible from the internet that have Let’s Encrypt certs.
That sounds like the method OP is trying to use.
sxan@midwest.social 1 month ago
Hmmm. You’re right; it’s a mechanism I’ve never used because it’s more work and it is slower, and I forget about it. All you need to do is be able to prove you own the domain, and control over the DNS record is certainly viable.
Is that what Porkbun does? Because Caddy can automate the http method, but not the DNS challenge method, because both require a handshake and that’s updating the DNS record.
sugar_in_your_tea@sh.itjust.works 1 month ago
Porkbun is a domain registrar, so I’m guessing OP is using their API to edit a DNS record with the challenge so Let’s Encrypt can prove ownership of the domain. Caddy can automate that, however, you need a Caddy build with a plugin for the registrar (use xcaddy), and then supply login details in the Caddyfile.
Here’s the plugin for porkbun, and the README documents how to use it.