Setting up local Caddy with Porkbun
(wiki.livingcartoon.org)
from kiol@discuss.online to selfhosted@lemmy.world on 30 Jun 16:44
https://discuss.online/post/41958260
from kiol@discuss.online to selfhosted@lemmy.world on 30 Jun 16:44
https://discuss.online/post/41958260
cross-posted from: 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!
#selfhosted
threaded - newest
Just to be clear, why wouldn’t simply provisioning a certificate for each subdomain under the wildcard work?
Like, if you have a test site test.example.domain.com, you could have nginx (using acme) create a certificate for that. And then when you move to test.domain.com, nginx would do the same thing.
Now, technically letsencrypt does have a rate limit, but it’s a fairly generous rate limit:
I would do my testing this way, and I didn’t hit any limits, although I was careful to keep certificates and reuse them, and to not spam.
If you need more domains with SSL than that rate limit would provide, then it would make sense to investigate Caddy with porkbun, since DNS-01 challenges are the only way to get wildcard certificates, which apply to a whole wildcard.
Thanks for the thoughts. I’ll reference this as I continue working on this.
Second comment, but if you need/want Caddy we can help that too. It looks like the documentation link in the github page you linked is dead, and the correct one is: caddyserver.com/docs/json/apps/tls/…/acme/
I found that from this page: caddy.community/t/…/8148
Thanks again. Will reference this as well, and provide update with what happens.