Error 429 Rate limit

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., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: i got a error due to a broken vm, this is a new vm and cant get the ssl to work

It produced this output:
An error occurred creating certificates with Let's Encrypt:

acme: error: 429 :: POST ::
:: urn:ietf:params:acme:error:rateLimited :: Error creating new order :: too
many certificates already issued for exact set of domains:,

My web server is (include version):

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

My hosting provider, if applicable, is:

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

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

When can i get a ssl again for this domain?

also, is there a thing we can do in the meantime to have an ssl?

Hi @00FF00Parsley

please read your complete error message.

Then the link shared there.

PS: Use your backup of that VM, there is a valid certificate.

Hi Juegen,

Thank you for helping me out.

So if i can find the old certificate on the vm what broke down, i can restore it?
What files do i need from that vm? i can search for it maybe.
is it ?

Please: I have no idea

  • if you have a backup
  • if you have one, how that backup is organized

I have a the vm live now, and can ssh into it. ill search for it.
the certificate is in .crt extension?

No idea, as you haven't said which client you're using. If you're using certbot, you'd be looking for cert.pem and privkey.pem, and they'd be somewhere in /etc/letsencrypt/.

1 Like

Okay thank you, ill look into that.

Thanks for helping me out, i have succesfully retrieved the .crt and .key from the old vm.

I did this trough SSH and sftp.

Thank you! ssl is working fine for now!

1 Like

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