Rate Limit Too Many Issued

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. crt.sh | 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: rhecllc.com

I ran this command:

It produced this output: Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours

We tried too many times while you were having an outage, however, from what we see, the certificate never generated, it always failed, so how is this too many certificates issued? Is there a way to get around this without waiting a week?

1 Like

There are a lot of certificates issued recently and submitted to the Certificate Logs: crt.sh | rhecllc.com

So apparently your outage was not affecting the actual issuance.

3 Likes

As a temporary solution (if you lost your private key generated during the failed attempts), you can change a set of domain names in the certificate and issue a new one. For example, add the third alias: rhecllc.com, www.rhecllc.com and www1.rhecllc.com and make sure you add it in all three places: certificate, DNS A record and nginx virtual host. Then you will be able to issue the certificate because it contains a different set of domain names.

4 Likes

Welcome to the Let's Encrypt Community, Adrian :slightly_smiling_face:

With what software or process did you acquire your certificates? Are you unable to install one of the certificates you've acquired?

3 Likes

Do you still have any of those certs?
If running certbot, show:
certbot certificates
If running acme.sh, show:
acme.sh --list
If anything else, show whatever makes it printout the list of managed certs.

2 Likes