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.
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:
VPS
I can login to a root shell on my machine (yes or no, or I don't know):
sure
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):
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.
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.
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.
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?
