Here were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains

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. https://crt.sh/?q=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:

snickies.com

I ran this command:

certonly --webroot --webroot-path=/var/www/certbot --email thunpisit.am@gmail.com --agree-tos --no-eff-email --force-renewal -d snickies.com -d www.snickies.com

It produced this output:

certbot | Saving debug log to /var/log/letsencrypt/letsencrypt.log
certbot | Plugins selected: Authenticator webroot, Installer None
certbot | Renewing an existing certificate
certbot | An unexpected error occurred:
certbot | There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: snickies.com,www.snickies.com: see https://letsencrypt.org/docs/rate-limits/
certbot | Please see the logfiles in /var/log/letsencrypt for more details.
certbot | IMPORTANT NOTES:
certbot | - Your account credentials have been saved in your Certbot
certbot | configuration directory at /etc/letsencrypt. You should make a
certbot | secure backup of this folder now. This configuration directory will
certbot | also contain certificates and private keys obtained by Certbot so
certbot | making regular backups of this folder is ideal.
certbot exited with code 1

My web server is (include version): Nginx latest

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

My hosting provider, if applicable, is: AWS GovCloud

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): Using latest through docker container

I have been getting this for the past couple days and I only try to request certbot maybe 3 times a day max. I use staging before actually requesting the cert but for some reason I think you guys havn’t lift the limit on my domain yet.

Hi @thunpisit

you have created 5 identical certificates ( https://check-your-website.server-daten.de/?q=snickies.com ):

CertSpotter-Id Issuer not before not after Domain names LE-Duplicate next LE
948860127 CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US 2019-06-04 11:58:17 2019-09-02 11:58:17 snickies.com, www.snickies.com - 2 entries duplicate nr. 5 next Letsencrypt certificate: 2019-06-11 06:48:37
949900147 CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US 2019-06-04 11:56:59 2019-09-02 11:56:59 snickies.com, www.snickies.com - 2 entries duplicate nr. 4
948853696 CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US 2019-06-04 11:52:24 2019-09-02 11:52:24 snickies.com, www.snickies.com - 2 entries duplicate nr. 3
948844535 CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US 2019-06-04 11:43:50 2019-09-02 11:43:50 snickies.com, www.snickies.com - 2 entries duplicate nr. 2
948386461 CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US 2019-06-04 06:48:37 2019-09-02 06:48:37 snickies.com, www.snickies.com - 2 entries duplicate nr. 1
885395535 CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US 2019-04-29 00:06:09 2019-07-28 00:06:09 snickies.com, www.snickies.com - 2 entries

That hits the limit. Please read

Where are these? Please use one certificate 60 - 85 days, then create the next certificate.

There were in a docker container and the certs are inside the container which all of them already destroyed. It sounds llike I hit 5 / week limit so what will be the next time I am able to request the certificate?

That's the wrong design using Letsencrypt certificates.

You should save account informations and certificates outside of your container, so you can reuse the account and the certificate.

Read the shared output:

next Letsencrypt certificate: 2019-06-11 06:48:37

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