# Hit the Rate Limit **URL:** \ **Category:** Server\ **Created:** [January 15, 2018, 10:59am UTC](https://community.letsencrypt.org/t/hit-the-rate-limit/50491 "2018-01-15T10:59:45Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![koluke](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/koluke/32/1329_2.png) [@koluke](https://community.letsencrypt.org/u/koluke)\ **Post date:** [January 15, 2018, 11:13am UTC](https://community.letsencrypt.org/t/hit-the-rate-limit/50491/2 "2018-01-15T11:13:34Z")
That error means somebody (either on that server or on another server on your domains) got a duplicate certificate containing the same set of domains successfully. If you had run into the TLS-SNI issue, you would’ve received an error similar to the one described in [Solution: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA](https://community.letsencrypt.org/t/solution-client-with-the-currently-selected-authenticator-does-not-support-any-combination-of-challenges-that-will-satisfy-the-ca/49983)). Based on that, it looks like your cert renewed properly? If not, there’s no way to reset the rate limits manually, so you’ll have to wait for the rate limits to expire as described in [https://letsencrypt.org/docs/rate-limits/](https://letsencrypt.org/docs/rate-limits/)). If you post your domain here, we can look up your domain and see which certs have been issued (Let’s Encrypt logs this info by default, so hiding your domain here doesn’t do much). If you’re hesitant, you can check yourself at [https://crt.sh](https://crt.sh) to see how many certificates have been issued for your domain. --- _[View the full topic](https://community.letsencrypt.org/t/hit-the-rate-limit/50491)._