Cert generation rateLimit

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: silinajewellery.ma

I ran this command: from directadmin, generate new certificate

It produced this output: acme: error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rateLimited :: Error creating new order :: too many new orders recently: see Rate Limits - Let's Encrypt, url:
Certificate generation failed.

My web server is (include version): Litespeed

The operating system my web server runs on is (include version): Centos 7

My hosting provider, if applicable, is: Me

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

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

1 Like

Welcome to the Let's Encrypt Community :slightly_smiling_face:

That rate limit usually occurs when:

  • an ACME client trying to acquire a certificate repeatedly fails/quits in the middle of the process before actually acquiring the certificate.
  • an ACME client (most often of a hosting provider) attempts to acquire many different certificates for different domain names in a short time

The first condition is often ameliorated when subsequent attempts succeed in authenticating domain names on the order resulting in the need to authenticate fewer domain names with each attempt until eventually all domain names for the certificate have been authenticated.

For users of the ACME v2 API you can create a maximum of 300 New Orders per account per 3 hours. A new order is created each time you request a certificate from the Boulder CA, meaning that one new order is produced in each certificate request. Exceeding the New Orders limit is reported with the error message too many new orders recently.


To investigate this further, you could look at the DirectAdmin logs, or, if you're not the system administrator, ask the hosting provider to look at the DirectAdmin logs. As @griffin says, it seems possible that the software is crashing right in the middle of the issuance process for some reason.


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