cross-posted from: https://discuss.online/post/41958206
Open to suggestions for managing Caddy for domains from Porkbun.
- Porkbun itself is using Cloudflare.
- Their Caddy module is confusing to setup due to API changes and older documentation.
- I’d like to use a declarative json configuration, but first I just need Porkbun to play nice enough to work when adding subdomains via wildcard.
The Goal
Setup legit Let’s Encrypt as wildcard locally to test services at
*example.domain.com, then put them into production on mainsite wildcard*.domain.comon VPS or similar.Seeking Advice
Can anyone advise on setup recommendations. I’m currently using Nginx, which I had no difficulty setting up with ACME challenge. Perhaps I’m approaching Caddy in the wrong way. Thanks for any ideas!
my homelab is using this setup, I configured porkbun API, compiled caddy with the DNS challenge plugin and configured it.
- https://codeberg.org/Disco-Robot/homelab
- https://codeberg.org/Disco-Robot/homelab/src/branch/master/ansible/coreTasks/caddy.yaml
- https://codeberg.org/Disco-Robot/homelab/src/branch/master/configs/caddyfile.j2
I am using ansible with jinja templates there, if you are not familiar with it or have any doubt feel free to ask.
Thanks, I’ll look it over
I have Porkbun domains and am getting ready to try setting up Caddy so randomly stumbling onto this thread is serendipitous.
How did it go?
Porkbun is a registrar that also has DNS hosting, and ACME DNS challenges just need DNS hosting. I also use Porkbun and I am happy with them as a registrar, but their DNS service wasn’t working out for me and I host my DNS records on Desec. It’s working well for me after I increased some timeouts in my ACME client configuration but I can’t recommend it if you’re having problems with Porkbun because the Desec rate limits are strict and their TTLs are high and if you don’t already know what you’re doing you’re likely to spend a lot of time waiting for propagation or rate limits.
I’ve been considering desec. Porkbun uses cloudflare for dns.