Error creating new authz :: too many currently pending authorization s


I’ve noticed that certificate for our issues tracker has expired. There is a cron job that runs every day to renew certificate (in case it is about to expire). When I’ve logged onto the server there were a lot of cron jobs stuck (running some perl script).

I’ve killed them all and ran renew manually. Got “too many currently pending authorization” error. How could I fix this issue?

Thanks for your help!

Please fill out the fields below so we can help you better.

My domain is:

I ran this command (same command is ran daily - it used to work fine before):

sudo letsencrypt -n --standalone --pre-hook ‘systemctl stop apache2.service’ --post-hook ‘systemctl start apache2.service’ renew

It produced this output:

2017-05-15 19:13:50,890:WARNING:certbot.renewal:Attempting to renew cert from /etc/letsencrypt/renewal/ produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new authz :: too many currently pending authorizations. Skipping.

My operating system is (include version): Debian stable
My web server is (include version): Apache
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no


alternatively search rate limits on this forum. There are lots of articles on this topic

The “too many currently pending authorizations” error is usually the sign of a buggy client application. It refers to a situation where clients attempt to obtain certificates but don’t complete the process (perhaps because the client crashes or hangs, or delays a large amount of time before completing the request).

Are those Perl scripts perhaps also Let’s Encrypt clients or is that simply coincidental?

Do you just have the one certificate on that system?

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