It’s been more than a week since I successfully issued a certificate for my domain and I still get the error :
An unexpected error occurred:
There were too many requests of a given type :: Error finalizing order :: too many certificates already issued for: centiva-test.ca: see https://letsencrypt.org/docs/rate-limits/
I’m trying to generate a wildcard certificate for *.dev04.centiva-test.ca
Edit for future readers: The renewal rate limiting situation has improved since this post was written. You should ignore the quote below and follow the links for more up-to-date information.
There have been 52 certificates issued in the last week:
To make sure you can always renew your certificates when you need to, we have a Renewal Exemption to the Certificates per Registered Domain limit. Even if you’ve hit the limit for the week, you can still issue new certificates that count as renewals. An issuance request counts as a renewal if it contains the exact same set of hostnames as a previously issued certificate. This is the same definition used for the Duplicate Certificate limit described above. Renewals are still subject to the Duplicate Certificate limit. Also note: the order of renewals and new issuances matters. To get the maximum possible number of certificates, you must perform all new issuances before renewals during a given time window.
Your domain is in an awkward situation. You have to juggle the scheduling carefully, or use fewer certificates, or ask Let's Encrypt for a rate limit adjustment.
Oh thank you very much! I forgot about the automatic SSL system we have and didnt see the generated certificate using crt.sh and haven’t heard about the letsdebug tool before but will surely use it in the future.
We will review our issuance workflow and consider asking letsencrypt for a rate limit adjustment.