Certificate Request KO | too many currently pending authorizations

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: remplacer-parebrise.fr

I ran this command: Request new SSL certificate

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many currently pending authorizations: see Rate Limits - Let's Encrypt
Please see the logfiles in /var/log/letsencrypt for more details.

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Obtaining a new certificate
An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many currently pending authorizations: see Rate Limits - Let's Encrypt
Please see the logfiles in /var/log/letsencrypt for more details.

My web server is (include version): Apache 2.4.38

The operating system my web server runs on is (include version): Debian Linux 10

My hosting provider, if applicable, is: Bare Metal (OVH)

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):

Webmin version 1.973
Usermin version 1.823
Virtualmin version 6.16 Pro

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

certbot --version
certbot 0.31.0

1 Like

Hi @koushal01 and welcome to the LE community forum :slight_smile:

I see that a certificate has been issued for that name today:
crt.sh | remplacer-parebrise.fr
And I do hope that your problem has been solved; if so, please reply with information (for other readers).

I do find this... interesting; and may be part of the problem:

I find this, as always, an all too easy place for mistakes to... happen:

And this seems... very interesting too:

1 Like

Welcome to the Let's Encrypt Community :slightly_smiling_face:

This type of error is typically encountered when an ACME client repeatedly fails/crashes in the middle of execution before sending requests to the Let's Encrypt server to verify challenges for activated authorizations for domain names. It is a very unusual error to encounter and suggests a seriously misbehaving piece of software. You might want to check with the developer of your ACME client (though I'm not sure which one given the list you've provided).

1 Like

Hello Everyone,
Thank you very much for your feedback.
Our service provider resolved this issue using script in below link:

  • List item

https://tools.letsdebug.net/clear-authz

2 Likes

I'm very glad you found the script to clear the pending authorizations! :smiley:

Two questions still haunt me though:

  • Why did this happen in the first place?
  • Will this continue happening?
2 Likes

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