Retry limit exceeded

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:

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:
digital ocean
I can login to a root shell on my machine (yes or no, or I don't know):
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):

Looking at the log of my Traefik container I have the return that I broke the rule of misuse of the certificates api.
I would like to create an account for each site of mine so this doesn't happen again. How is this possible?

2022-02-03T07:14:47.950479596Z {"level":"error","msg":"Unable to obtain ACME certificate for domains "" detected thanks to rule "" : unable to generate a certificate for the domains []: acme: error: 429 :: POST :: :: urn:ietf:params:acme:error:rateLimited :: Error creating new order :: too many failed authorizations recently: see Rate Limits - Let's Encrypt, url: ","time":"2022-02-03T07:14:47Z"}

This resets in one hour. And it's not linked to an acme account, just 5 per hostname per hour.

It has an underlying cause. I would look for it. What else do your logs say about failed validations?

This is something that your acme client documentation shall tell you. (But it would not solve this problem)

1 Like

Your ACME client is failing in getting a certificate and is making too many attempts without succeeding. It's probably failing until you've fixed why it's failing.

Please use the staging environment to fix your ACME client for that hostname and only after that works, try the production environment again.


Could you guide me to use the test environment? I use kuberntes and traefik as proxy

Read here:

1 Like

The documentation for the staging environment from Let's Encrypts point of view can be found here:

How that's set up in traefic/kubernetes: I don't know and actually I don't wanna know :stuck_out_tongue:


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