Waiting for solver before continuing: Cant create a wildcard certificate

[Whitestrake (Matthew Fay)]

@Louen

First Created this token with Zone.DNS.Edit

Does it have Zone.Zone:Read as well? (See: GitHub - caddy-dns/cloudflare: Caddy module: dns.providers.cloudflare)

@Louen

I’m worried because I’ve been re-issuing too much the single certificate for example.com many times, so probably it wont have many opportunities left

I would recommend manually swapping to the LetsEncrypt staging endpoint while you’re testing this deployment.

How to use Let's Encrypt staging endpoint with Caddy

If you’re setting up your server for the first time or testing a new network or domain configuration and you are using Let’s Encrypt (one of Caddy’s default certificate authorities), you should use their staging environment to avoid being rate limited. This is very easy to do in Caddy. At the top of your Caddyfile, specify the acme_ca global option: { acme_ca https://acme-staging-v02.api.letsencrypt.org/directory } If you already have a global options block, just add that line to it; don’…

You won’t get trusted certificates from the staging endpoint, but the rate limits are greatly relaxed there and you can test away until you get a good result before swapping back to the production endpoint for real certs.

I believe Caddy can do this automatically if it detects a certain amount of failures but it’s best to be nice to the ACME server here and avoid the risk of a rate limit for yourself in the process.