# Here were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains **URL:** \ **Category:** Help\ **Created:** [June 8, 2019, 11:11am UTC](https://community.letsencrypt.org/t/here-were-too-many-requests-of-a-given-type-error-creating-new-order-too-many-certificates-already-issued-for-exact-set-of-domains/95401 "2019-06-08T11:11:25Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![thunpisit](https://avatars.discourse-cdn.com/v4/letter/t/d26b3c/32.png) [@thunpisit](https://community.letsencrypt.org/u/thunpisit)\ **Post date:** [June 8, 2019, 11:11am UTC](https://community.letsencrypt.org/t/here-were-too-many-requests-of-a-given-type-error-creating-new-order-too-many-certificates-already-issued-for-exact-set-of-domains/95401/1 "2019-06-08T11:11:25Z")
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](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](http://snickies.com) I ran this command: certonly --webroot --webroot-path=/var/www/certbot --email [thunpisit.am@gmail.com](mailto:thunpisit.am@gmail.com) --agree-tos --no-eff-email --force-renewal -d [snickies.com](http://snickies.com) -d [www.snickies.com](http://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](http://snickies.com),[www.snickies.com](http://www.snickies.com): see [https://letsencrypt.org/docs/rate-limits/](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. ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [June 8, 2019, 11:33am UTC](https://community.letsencrypt.org/t/here-were-too-many-requests-of-a-given-type-error-creating-new-order-too-many-certificates-already-issued-for-exact-set-of-domains/95401/2 "2019-06-08T11:33:21Z")
Hi @thunpisit > [@thunpisit](#): > > My domain is: > > [snickies.com](http://snickies.com) you have created 5 identical certificates ( [https://check-your-website.server-daten.de/?q=snickies.com](https://check-your-website.server-daten.de/?q=snickies.com) ): | CertSpotter-Id | Issuer | not before | not after | Domain names | LE-Duplicate | next LE | | --- | --- | --- | --- | --- | --- | --- | | [948860127](https://check-your-website.server-daten.de/queries/q_get_certificatefile/certfile-certspotter-948860127.pem?certspotter_id=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](http://snickies.com), [www.snickies.com](http://www.snickies.com) - 2 entries | duplicate nr. 5 | next Letsencrypt certificate: 2019-06-11 06:48:37 | | [949900147](https://check-your-website.server-daten.de/queries/q_get_certificatefile/certfile-certspotter-949900147.pem?certspotter_id=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](http://snickies.com), [www.snickies.com](http://www.snickies.com) - 2 entries | duplicate nr. 4 | | | [948853696](https://check-your-website.server-daten.de/queries/q_get_certificatefile/certfile-certspotter-948853696.pem?certspotter_id=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](http://snickies.com), [www.snickies.com](http://www.snickies.com) - 2 entries | duplicate nr. 3 | | | [948844535](https://check-your-website.server-daten.de/queries/q_get_certificatefile/certfile-certspotter-948844535.pem?certspotter_id=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](http://snickies.com), [www.snickies.com](http://www.snickies.com) - 2 entries | duplicate nr. 2 | | | [948386461](https://check-your-website.server-daten.de/queries/q_get_certificatefile/certfile-certspotter-948386461.pem?certspotter_id=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](http://snickies.com), [www.snickies.com](http://www.snickies.com) - 2 entries | duplicate nr. 1 | | | [885395535](https://check-your-website.server-daten.de/queries/q_get_certificatefile/certfile-certspotter-885395535.pem?certspotter_id=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](http://snickies.com), [www.snickies.com](http://www.snickies.com) - 2 entries | | | That hits the limit. Please read > **[Rate Limits - Let's Encrypt](https://letsencrypt.org/docs/rate-limits/)** > > Let’s Encrypt provides rate limits to ensure fair usage by as many people as possible. We believe these rate limits are high enough to work for most people by default. We’ve also designed them so renewing a certificate almost never hits a... Where are these? Please use one certificate 60 - 85 days, then create the next certificate. ---
**Author:** ![thunpisit](https://avatars.discourse-cdn.com/v4/letter/t/d26b3c/32.png) [@thunpisit](https://community.letsencrypt.org/u/thunpisit)\ **Post date:** [June 8, 2019, 11:52am UTC](https://community.letsencrypt.org/t/here-were-too-many-requests-of-a-given-type-error-creating-new-order-too-many-certificates-already-issued-for-exact-set-of-domains/95401/3 "2019-06-08T11:52:20Z")
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? ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [June 8, 2019, 12:09pm UTC](https://community.letsencrypt.org/t/here-were-too-many-requests-of-a-given-type-error-creating-new-order-too-many-certificates-already-issued-for-exact-set-of-domains/95401/4 "2019-06-08T12:09:23Z")
> [@thunpisit](#): > > There were in a docker container and the certs are inside the container which all of them already destroyed. 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. > [@thunpisit](#): > > so what will be the next time I am able to request the certificate? Read the shared output: > next Letsencrypt certificate: 2019-06-11 06:48:37 ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [July 8, 2019, 12:09pm UTC](https://community.letsencrypt.org/t/here-were-too-many-requests-of-a-given-type-error-creating-new-order-too-many-certificates-already-issued-for-exact-set-of-domains/95401/5 "2019-07-08T12:09:24Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.