# Time to rate limits

**URL:** <https://community.letsencrypt.org/t/time-to-rate-limits/148548>\
**Category:** Help\
**Created:** [March 29, 2021, 4:04pm UTC](https://community.letsencrypt.org/t/time-to-rate-limits/148548 "2021-03-29T16:04:35Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tommy-Traviline](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tommy-traviline/32/48487_2.png) [@Tommy-Traviline](https://community.letsencrypt.org/u/Tommy-Traviline)\
**Post date:** [March 29, 2021, 4:04pm UTC](https://community.letsencrypt.org/t/time-to-rate-limits/148548/1 "2021-03-29T16:04:35Z")

</div>

There were too many requests of a given type :: Error creating new order :: yo many certificates alreday issued for exact set of domains: www.traviline.nat.cu:

I have that error since Friday morning

My question is this:

When can I request a certificate again?

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [March 29, 2021, 4:19pm UTC](https://community.letsencrypt.org/t/time-to-rate-limits/148548/2 "2021-03-29T16:19:30Z")

</div>

Welcome to the Let's Encrypt Community, Tommy 🙂

You are allowed 5 duplicate certificates per any rolling 7-day period where certificates are considered duplicates of each other if they cover the exact same domain names in any order.

You can find the complete history of the certificates you have been issued on [crt.sh](https://crt.sh/?Identity=www.traviline.nat.cu&deduplicate=Y).

> **[Rate Limits - Let's Encrypt - Free SSL/TLS Certificates](https://letsencrypt.org/docs/rate-limits/)**
>
> Last updated: Mar 5, 2020 | See all Documentation 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...

---

<div class="post-metadata">

**Author:** ![Tommy-Traviline](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tommy-traviline/32/48487_2.png) [@Tommy-Traviline](https://community.letsencrypt.org/u/Tommy-Traviline)\
**Post date:** [March 29, 2021, 4:22pm UTC](https://community.letsencrypt.org/t/time-to-rate-limits/148548/3 "2021-03-29T16:22:22Z")

</div>

So if I reach the limit on Friday, should I wait until Friday of the other week?

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [March 29, 2021, 4:26pm UTC](https://community.letsencrypt.org/t/time-to-rate-limits/148548/4 "2021-03-29T16:26:33Z")

</div>

Yes. The exact time is indicated by the Timestamps of the certificates as seen on crt.sh. As long as you still have the private key for at least one of the certificates, you should be alright. You might consider creating a certificate covering **both** `traviline.nat.cu` **and** `www.traviline.nat.cu` (which you can do right now).

---

<div class="post-metadata">

**Author:** ![Tommy-Traviline](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tommy-traviline/32/48487_2.png) [@Tommy-Traviline](https://community.letsencrypt.org/u/Tommy-Traviline)\
**Post date:** [March 29, 2021, 4:38pm UTC](https://community.letsencrypt.org/t/time-to-rate-limits/148548/5 "2021-03-29T16:38:15Z")

</div>

thanks, excellent help

---

<div class="post-metadata">

**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:** [March 29, 2021, 5:25pm UTC](https://community.letsencrypt.org/t/time-to-rate-limits/148548/6 "2021-03-29T17:25:35Z")

</div>

Hi @Tommy-Traviline

> [@Tommy-Traviline](#):
>
> When can I request a certificate again?

why are you doing that? That's a waste of resources.

Create **one** certificate, use it 60 - 85 days, then create the next.

It's not the idea using Letsencrypt to create 5 certificates per week with the same set of domain names.

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [March 29, 2021, 8:09pm UTC](https://community.letsencrypt.org/t/time-to-rate-limits/148548/7 "2021-03-29T20:09:41Z")

</div>

I agree with @JuergenAuer

@Tommy-Traviline Please use the [staging environment](https://letsencrypt.org/docs/staging-environment/) for testing and please store your production certificates and private keys on persistent storage, so they don't get deleted all the time.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [April 28, 2021, 8:10pm UTC](https://community.letsencrypt.org/t/time-to-rate-limits/148548/8 "2021-04-28T20:10:36Z")

</div>

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