Unexpected registration rate limiting error

Help
41

I was testing. I had little time (including time to think ahead :slight_smile: ) so it is completely my fault. Also when deleting a certificate for one domain I had to do full reinstall as the webroot plugin was giving errors… Anyway I hoped there is other way then to wait till next week.

42

The existing certs should still exist in the LE directory ( unless you deleted that without keeping a backup ) when you reinstalled.

For testing, you should use the staging server.

The quickest route - if you haven’t got the old certs still - is probably waiting a week. There is a way to ask for an exception to the rates on a specific domain being developed, whoever I don’t suspect that will be ready within the week.

43

Thank you, Serverco. I will wait.

I’ve been waiting for a year so I’m hot. Great tool.

44

I’m experiencing the same problem on our staging environment.

We ran the buik of our requests (100+) on the stage server (might have run a few again prov during manual executions when I forgot to put the --test-cert flag).

Waited the weekend to get unblocked… how long does it usually take? Running on a tight deadline here…

1 Like
45

The great one, i installed in 5/6 domains in a week and now Im facing the following issue :

Certificate signature failed. If you supplied your own CSR make sure the domains on it match what you put on SSLForFree. If there is a rate limiting error at the end of this paragraph certificates per Domain is currently 5 per 7 days. Try asking Lets Encrypt to increase the limit or wait 7 days. Rate limits should increase in the near future. { “type”: “urn:ietf:params:acme:error:rateLimited”, “detail”: “Error finalizing order :: too many certificates already issued for exact set of domains: domainname.com: see https://letsencrypt.org/docs/rate-limits/”, “status”: 429 }

What’s the process for "asking Lets Encrypt to increase the limit " ??

Thanks

46

Your error is not related to the one in this thread.

In fact, you have issued duplicate certificates for the exact same domain 5 times in a week: you can search for your domain on http://crt.sh/ to see all of the duplicates.

There shouldn't really be any need for you to issue duplicate certificates so rapidly - you should be able to re-use a previously issued certificate (since they're all the same).

There isn't one, in your case, because you do not have a valid reason to ask for an exception. You will need to wait out the 7 days, or issue a certificate with a different set of domains to avoid the rate limit. If you believe you have a valid reason, then you can search on Rate Limits - Let's Encrypt for the information about applying for rate limit exceptions.

47

Hi,

Thank you for your reply.