Limit not reached, but have a error

Limit not reached, but I recieved message:

An unexpected error occurred: There were too many requests of a given type :: Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours.

My domain is:

I ran this command:

certbot --nginx -d

It produced this output:

An unexpected error occurred: There were too many requests of a given type :: Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours.

My web server is (include version):

Nginx 1.18.0

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

Debian 11

My hosting provider, if applicable, is:


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

SSH only

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

certbot 1.12.0

What part of the error message isn't clear? It says you've created five identical certificates within the past week (168 hours). Use one of them.

In other words, contrary to the title of this topic, you have reached (one of) the limit(s).


it was NOT renewals ( Rate Limits - Let's Encrypt )

Use one of them.

Can't. After server problems (damned nginx forgot how to use server_name directive) server was fully reinstalled.

Yep, five duplicate certificates in 12 minutes.

Are you sure that's the only command you ran? What about the commands starting around 26 Feb 2022 04:26:50 UTC (05:26 CET, 07:26 MSK)


Didn't say it was, and it doesn't matter. The rate limits provide that you can't issue more than five identical certificates in a week, as you're abusing the service.

Then you'll need to wait for a week after the first of those five was issued. Edit: and in the future, use the staging environment for testing; that's what it's there for.


No, there were problems with the server yesterday. More than 24 hours have passed since then.

There is a Failed Validation limit of 5 failures per account, per hostname, per hour.

where is a "week" ?

Thou shall sort out your server issue using the staging environment, and then wait for the rate limit to forget about you.


In a completely different rate limit:


It was not testing. Before this situation, I never had same issue. None of the more than 20 servers in a few years.

It WAS NOT renewals.

Staging env for production server? Really O.o

But it was still duplicate certificates.

I'd ask what it was, then, to have you issuing five identical certificates in twelve minutes, but ultimately it doesn't matter. That's abuse of the service. Wait a week, or use a different CA.


It either was forced renewals or you repeatedly issued the same certificate by resetting the machine (or erasing the certificate).

Of course you cannot use that if users are supposed to be visiting.

You can also read the rate limits page very carefully and it will suggest to you how to work around this specific limit. Telling you here defeats the side effect of carefully reading that page.


Yesterday I was getting a strange error message. I have not preserved the exact text, I reproduce it from memory:

We can't complete the certificate registration because the "server_name" parameter is missing in your configs.

Although it was, of course, present for both the default host and the desired host.

Are you sure that's the error?

Maybe it was talking about installation instead of registration, and you issued more certificates because certbot asked and regardless of it warning you you told it to issue more certificates?

Come on, you could've installed your certificate manually, or come here to ask before hitting that rate limit.


Yes, I'm sure it's a error.

When executing the "certbot -d ... --nginx" command, I received a list of questions, entered the correct information, the certbot went to the nginx configuration and crashed with the above error.

This happened at the stage of changing the nginx configuration files (creating 80->443 redirects).

At this moment, for some reason, the certbot could not find the directive "server_name" in the nginx configs and crashed with a fatal error, littering the stack trace in the logs.

Yes, I am absolutely sure that it was a mistake.

In this case, the certificate files were probably created - but how would I know about this, getting a fatal error?

168 hours is one week.


Can't find substring "168" at this page: Rate Limits - Let's Encrypt

Show the output of:
certbot certificates


Can you fine "week" there?