# Too Many Request Error but didn't create any certs? **URL:** \ **Category:** Help\ **Created:** [April 8, 2019, 8:57pm UTC](https://community.letsencrypt.org/t/too-many-request-error-but-didnt-create-any-certs/90686 "2019-04-08T20:57:14Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Ari-K](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@Ari-K](https://community.letsencrypt.org/u/Ari-K)\ **Post date:** [April 8, 2019, 8:57pm UTC](https://community.letsencrypt.org/t/too-many-request-error-but-didnt-create-any-certs/90686/1 "2019-04-08T20:57:14Z")
Hi this is my error: Requesting new certificate order… new-order error: HTTP/1.1 100 Continue Expires: Mon, 08 Apr 2019 20:40:26 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache HTTP/1.1 429 Too Many Requests Server: nginx Content-Type: application/problem+json Content-Length: 266 Boulder-Requester: 44558126 Link: ;rel=“index” Replay-Nonce: IrCBgMqLuJc\_SJwRbbtXWfbIsiVyP\_t01fOcBT9IpCM Expires: Mon, 08 Apr 2019 20:40:26 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Mon, 08 Apr 2019 20:40:26 GMT Connection: close { “type”: “urn:ietf:params:acme:error:rateLimited”, “detail”: “Error creating new order :: too many certificates already issued for exact set of domains: [dinapolilevels.com](http://dinapolilevels.com),[www.dinapolilevels.com](http://www.dinapolilevels.com): see [https://letsencrypt.org/docs/rate-limits/](https://letsencrypt.org/docs/rate-limits/)”, “status”: 429 }. Exiting… but according to [https://crt.sh/?q=dinapolilevels.com](https://crt.sh/?q=dinapolilevels.com) I didn’t issue any today so why I can’t create a new one ? ![10](https://global.discourse-cdn.com/letsencrypt/original/3X/c/f/cf063d22bd52a372603f54f4baf2d278618d8deb.png) If there are too many existing how can I get the private key ? I would really appreciate help. Thanks Ari ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [April 8, 2019, 9:00pm UTC](https://community.letsencrypt.org/t/too-many-request-error-but-didnt-create-any-certs/90686/2 "2019-04-08T21:00:19Z")
Hi @Ari-k, welcome to the community forum 👋 > [@Ari-K](#): > > but according to [crt.sh | dinapolilevels.com](https://crt.sh/?q=dinapolilevels.com) I didn’t issue any today so why I can’t create a new one ? It's not obvious but you need to update your `crt.sh` query to use a `%.` wildcard prefix. E.g. `%.dinapolilevels.com`. Doing that will show five identical certificates issued on 2019-04-07 in the [crt.sh output](https://crt.sh/?q=%25.dinapolilevels.com). That matches the [duplicate certificate rate limit](https://letsencrypt.org/docs/rate-limits/#duplicate-certificate) and the error message you received. Do you know how those certificates were created? ---
**Author:** ![Ari-K](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@Ari-K](https://community.letsencrypt.org/u/Ari-K)\ **Post date:** [April 8, 2019, 9:05pm UTC](https://community.letsencrypt.org/t/too-many-request-error-but-didnt-create-any-certs/90686/3 "2019-04-08T21:05:46Z")
Yesterday 2019-04-07 I was canceling [Webflow.com](http://Webflow.com) hosting which was with a certificate. When I was done and moved to new hosting zenbox.pl I tried to issue the certificate through them but I was getting the same error back. I have an option to manually add SSL but I can’t access the existing certifications nor can I create a new one. I’m in a loop ☹ What can I do ? Can I prove that I own the domain and get access to those existing somehow? or revoke/ delete them and issue a new one ? ---
**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\ **Post date:** [April 8, 2019, 9:15pm UTC](https://community.letsencrypt.org/t/too-many-request-error-but-didnt-create-any-certs/90686/4 "2019-04-08T21:15:29Z")
> [@Ari-K](#): > > Can I prove that I own the domain and get access to those existing somehow? or revoke/ delete them and issue a new one ? Nope, Let's Encrypt doesn't ever possess users' private keys—they exist only on your own server. If you don't have appropriate access to the server or if the private key has been deleted, there's no way that we can get you access to the private key. Also, as our rate limits page explains, > Revoking certificates does not reset rate limits, because the resources used to issue those certificates have already been consumed. > **[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... You'll need to wait a week, or issue a certificate containing a different combination of names, or request a certificate from a different CA. ---
**Author:** ![Ari-K](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@Ari-K](https://community.letsencrypt.org/u/Ari-K)\ **Post date:** [April 8, 2019, 9:49pm UTC](https://community.letsencrypt.org/t/too-many-request-error-but-didnt-create-any-certs/90686/5 "2019-04-08T21:49:23Z")
> [@schoen](#): > > issue a certificate containing a different combination of names how can I do that? > [@schoen](#): > > request a certificate from a different CA. what other CA have a free cert I can use for a week while waiting ? ---
**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\ **Post date:** [April 8, 2019, 9:54pm UTC](https://community.letsencrypt.org/t/too-many-request-error-but-didnt-create-any-certs/90686/6 "2019-04-08T21:54:50Z")
> [@Ari-K](#): > > how can I do that? You could add an extra subdomain like `example.dinapolilevels.com`; in that case this rate limit wouldn't prevent the issuance of the certificate for all three names. > [@Ari-K](#): > > what other CA have a free cert I can use for a week while waiting ? I've never used it, but I know Buypass Go SSL is a free publicly-trusted certificate provider that's compatible with the ACME protocol that Let's Encrypt uses. ---
**Author:** ![Ari-K](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@Ari-K](https://community.letsencrypt.org/u/Ari-K)\ **Post date:** [April 8, 2019, 11:06pm UTC](https://community.letsencrypt.org/t/too-many-request-error-but-didnt-create-any-certs/90686/7 "2019-04-08T23:06:50Z")
Thank you for the idea of using another CA. In the end I used [cloudflare.com](http://cloudflare.com) and their shared SSL that comes with a free plan. Website [https://dinapolilevels.com/](https://dinapolilevels.com/) is secure again 🙂 ---
**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\ **Post date:** [April 8, 2019, 11:17pm UTC](https://community.letsencrypt.org/t/too-many-request-error-but-didnt-create-any-certs/90686/8 "2019-04-08T23:17:28Z")
You also need a valid certificate on your origin server to secure the connection between Cloudflare’s CDN servers and the origin. For that, you can use Let’s Encrypt (returning to the original problem), another CA, or Cloudflare’s Origin CA. Without a valid certificate on the origin, and the SSL setting in Cloudflare’s dashboard set to “Full (strict)”, the website isn’t fully secure. > **[Managing Cloudflare Origin CA certificates](https://support.cloudflare.com/hc/en-us/articles/115000479507-Managing-Cloudflare-Origin-CA-certificates)** > > Understand how to use a Cloudflare Origin CA certificate to encrypt traffic between Cloudflare and your origin web server. Learn how to manage Origin CA certificates via Cloudflare and receive advi... ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [May 10, 2019, 9:36am UTC](https://community.letsencrypt.org/t/too-many-request-error-but-didnt-create-any-certs/90686/10 "2019-05-10T09:36:55Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.