# Error creating new order :: too many certificates already issued for exact set of domains **URL:** \ **Category:** Help\ **Created:** [May 4, 2020, 9:08pm UTC](https://community.letsencrypt.org/t/error-creating-new-order-too-many-certificates-already-issued-for-exact-set-of-domains/121690 "2020-05-04T21:08:49Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\ **Post date:** [May 4, 2020, 9:41pm UTC](https://community.letsencrypt.org/t/error-creating-new-order-too-many-certificates-already-issued-for-exact-set-of-domains/121690/2 "2020-05-04T21:41:23Z")
> [@letsgochamp](#): > > I can’t wait 1 week to renew it, what can I do? Rate Limit doc: [Rate Limits - Let's Encrypt](https://letsencrypt.org/docs/rate-limits/) You've hit the **Duplicate Certificate** limit, so you'll need actually to wait until that limit expires. Source: [https://check-your-website.server-daten.de/?q=peepsamurai.com](https://check-your-website.server-daten.de/?q=peepsamurai.com) [Let's Debug Toolkit](https://tools.letsdebug.net/cert-search?m=domain&q=peepsamurai.com&d=168) 11 May 2020 15:10:46 UTC is the next time you can request the **same set** of certificates. There is only one way to bypass the rate limit: > A certificate is considered a renewal (or a duplicate) of an earlier certificate if it contains the same set of hostnames, ignoring capitalization and ordering of hostnames. For instance, if you requested a certificate for the names [`www.example.com,` `example.com`], you could request four more certificates for [`www.example.com,` `example.com`] during the week. If you changed the set of hostnames by adding [`blog.example.com`], you would be able to request additional certificates. A tip: You are using Route53 as your DNS provider, and certbot-auto has integration for that (so you don't need to **manually** add records **and** issue new certificate when renew, just use the `./certbot-auto renew` if you setup correctly). See this thread for more information: [Example of using certbot-auto with Route 53 DNS?](https://community.letsencrypt.org/t/example-of-using-certbot-auto-with-route-53-dns/53021/) --- _[View the full topic](https://community.letsencrypt.org/t/error-creating-new-order-too-many-certificates-already-issued-for-exact-set-of-domains/121690)._