Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
facetbase.nl
I ran this command:
SAN certificate for all bindings of multiple IIS sites
It produced this output:
+Response from server:
+ Code: 429
+ Content: {
“type”: “urn:acme:error:rateLimited”,
“detail”: “Error creating new cert :: too many certificates already issued for: facetbase.nl”,
“status”: 429
After some searching i found these posts Clarification of rate limiting in Documentation / Rate Limits & Hitting rate limit after renewing certs
Our problem is we have auto-renewal active, whilst also trying to get new certificates.
According to the information inside linked posts it should be possible for us to create 20 new certificates each week, if we do this before any renewalls. This interferes with automatic renewal and is a counterintuitive way of managing our certificates, since we have to make somebody available to manually execute renewalls.
This problem has been going on for some time and we’ve already filled in the rate limiting form to request a higher limit, but received no response of any kind (first time was a few months ago, second time was yesterday).
Increasing the rate limit for our domain would temporarily fix our problem, however the main problem is automatic renewals taking up spots of our new certificate requests.
