I've been rate limited but only 10 certificates were issued

During my early implementations of a deployer script I stupidly didn't use the staging parameter, I got hit by the ratelimit and afterwards I started using the staging parameter. But now that my coding is finished and I want to deploy the certificate for real I'm still being hit by the rate limit. But it's supposed to be 50 a week, but only 10 have been issued according to crt.sh

How can I get my certificate issued?

My domain is:

I ran this command:
./acme.sh --force --issue --dns dns_nsupdate -d "*.7rhost[dot]com" --reloadcmd "python3 /opt/ssldeployer/main.py"

It produced this output:
Create new order error. Le_OrderFinalize not found. {
"type": "urn:ietf:params:acme:error:rateLimited",
"detail": "Error creating new order :: too many certificates already issued for exact set of domains: *.7rhost[dot]com: see Rate Limits - Let's Encrypt - Free SSL/TLS Certificates",
"status": 429

The operating system my web server runs on is (include version):
CentOS 6

I can login to a root shell on my machine (yes or no, or I don't know):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
acme.sh v2.8.9

Best Regards.


No, it isn't. Read the rate limit page again, and note the specific error you received--the limit you hit is five identical certs/week.


Just to clarify, you have not issued 10 certificates, you have issued 5 certificates but by default, crt.sh shows the pre-certificates (these pre-certificates are used to get the SCTs Signed Certificate Timestamps that will be used in the final certs but don't count at all for the rate limits) and the final (leaf) certificates. You can use the deduplicate option in crt.sh (advanced section) and crt.sh will show you only the leaf certificates.



Ok I understand now, I missread the ratelimits article. Thank you.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.