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!
I wasn’t aware of that they managed registered domains the way they do. I may need to reconcider my certificate setup currently, as I currently run a certificate per service because its more secure and looked cleaner, but if they count x.website.com certificates as website.com certificates, its entirely possible that when they switch to short lived certificate defaults I may come close to that rate limit.
If they cut the validity time for certificates, I’d expect them to also increase the rate limits by a corresponding amount. It’s not like they have anything to gain by making it so regular users can’t use the service anymore. They can’t upsell you to Lets Encrypt Premium with a higher rate limit.
Yea hopefully. I know that short lived certs is currently an additional parameter when requesting, hopefully when the default changes they will have a higher rate limit. That won’t be for quite some time though I expect.