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.
We run an SSL Certificate pipeline on behalf of around 60,000 customers. We have had a few requests for a new certificate fail recently on the first try stating that we’ve hit our rate limit for that particular domain. What’s causing this and is there anything we can do to mitigate it?
My domain is: liorablum.com
I ran this command: n/a. We use acmephp to programatically request certificates
It produced this output:
Truncated from our error logs:
“message”:“Client error: POST https://acme-v01.api.letsencrypt.org/acme/new-cert
resulted in a 429 Too Many Requests
response:\n{\n \“type\”: \“urn:acme:error:rateLimited\”,\n \“detail\”: \“Error creating new cert :: too many certificates already issued f (truncated…)\n”,“code”:429,“file”:”/app/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113",“trace”:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know):no
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):