# Cert failed to renew and now has hit Rate Limit

**URL:** <https://community.letsencrypt.org/t/cert-failed-to-renew-and-now-has-hit-rate-limit/75479>\
**Category:** Help\
**Created:** [October 22, 2018, 5:08pm UTC](https://community.letsencrypt.org/t/cert-failed-to-renew-and-now-has-hit-rate-limit/75479 "2018-10-22T17:08:22Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![joeker](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@joeker](https://community.letsencrypt.org/u/joeker)\
**Post date:** [October 22, 2018, 5:08pm UTC](https://community.letsencrypt.org/t/cert-failed-to-renew-and-now-has-hit-rate-limit/75479/1 "2018-10-22T17:08:22Z")

</div>

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: [countrystoveandfireplace.com](http://countrystoveandfireplace.com)

I ran this command: certbot-auto renew

It produced this output:  
Saving debug log to /var/log/letsencrypt/letsencrypt.log

* * *

Processing /etc/letsencrypt/renewal/countrystoveandfireplace.com.conf

* * *

Cert is due for renewal, auto-renewing…  
Plugins selected: Authenticator apache, Installer apache  
Renewing an existing certificate  
Performing the following challenges:  
tls-sni-01 challenge for [countrystoveandfireplace.com](http://countrystoveandfireplace.com)  
tls-sni-01 challenge for [www.countrystoveandfireplace.com](http://www.countrystoveandfireplace.com)  
Waiting for verification…  
Cleaning up challenges  
Attempting to renew cert ([countrystoveandfireplace.com](http://countrystoveandfireplace.com)) from /etc/letsencrypt/renewal/countrystoveandfireplace.com.conf produced an unexpected error: Failed authorization procedure. [countrystoveandfireplace.com](http://countrystoveandfireplace.com) (tls-sni-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Incorrect validation certificate for tls-sni-01 challenge. Requested 556ba35db7385a34b1c2d4265dbda5b9.5053a2ca23bce428a950bb41f85f101e.acme.invalid from 45.63.66.230:443. Received 2 certificate(s), first certificate had names “[countrystoveandfireplace.com](http://countrystoveandfireplace.com), [www.countrystoveandfireplace.com](http://www.countrystoveandfireplace.com)”, [www.countrystoveandfireplace.com](http://www.countrystoveandfireplace.com) (tls-sni-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Incorrect validation certificate for tls-sni-01 challenge. Requested b7fba6db7717599b5cc3ee48b731472e.885cdfd6eada7a0b42ca81a6487f3e6f.acme.invalid from 45.63.66.230:443. Received 2 certificate(s), first certificate had names “[countrystoveandfireplace.com](http://countrystoveandfireplace.com), [www.countrystoveandfireplace.com](http://www.countrystoveandfireplace.com)”. Skipping.  
All renewal attempts failed. The following certs could not be renewed:  
/etc/letsencrypt/live/countrystoveandfireplace.com/fullchain.pem (failure)

* * *

All renewal attempts failed. The following certs could not be renewed:  
/etc/letsencrypt/live/countrystoveandfireplace.com/fullchain.pem (failure)

* * *

1 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

- The following errors were reported by the server:

My web server is (include version): Apache 2.2.15

The operating system my web server runs on is (include version): CentOS Linux 6.10

My hosting provider, if applicable, is: vultr

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

So the first problem is failed renewal, and while trying to troubleshoot this, I’ve know run into the Rate Limit. I’ve had to disable SSL on the site.

Please advise

---

<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:** [October 22, 2018, 5:13pm UTC](https://community.letsencrypt.org/t/cert-failed-to-renew-and-now-has-hit-rate-limit/75479/2 "2018-10-22T17:13:09Z")

</div>

Hi @joeker

> [@joeker](#):
>
> tls-sni-01 challenge for [countrystoveandfireplace.com](http://countrystoveandfireplace.com)  
> tls-sni-01 challenge for [www.countrystoveandfireplace.com](http://www.countrystoveandfireplace.com)

the tls-sni-01 challenge is deprecated. So please try

```nohighlight
certbot-auto renew --preferred-challenges http

```

to use the http-01 - validation.

If that doesn't work, share the content of

```nohighlight
/var/log/letsencrypt/letsencrypt.log

```

---

<div class="post-metadata">

**Author:** ![joeker](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@joeker](https://community.letsencrypt.org/u/joeker)\
**Post date:** [October 22, 2018, 5:14pm UTC](https://community.letsencrypt.org/t/cert-failed-to-renew-and-now-has-hit-rate-limit/75479/3 "2018-10-22T17:14:29Z")

</div>

Hi JuergenAuer,

I did try that but have hit the Rate Limit:

[root@countrystoveandfireplace letsencrypt]# /root/certbot-auto renew --preferred-challenges http  
Saving debug log to /var/log/letsencrypt/letsencrypt.log

* * *

Processing /etc/letsencrypt/renewal/countrystoveandfireplace.com.conf

* * *

Cert is due for renewal, auto-renewing…  
Plugins selected: Authenticator apache, Installer apache  
Renewing an existing certificate  
Attempting to renew cert ([countrystoveandfireplace.com](http://countrystoveandfireplace.com)) from /etc/letsencrypt/renewal/countrystoveandfireplace.com.conf produced an unexpected error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see [https://letsencrypt.org/docs/rate-limits/](https://letsencrypt.org/docs/rate-limits/). Skipping.  
All renewal attempts failed. The following certs could not be renewed:  
/etc/letsencrypt/live/countrystoveandfireplace.com/fullchain.pem (failure)

* * *

All renewal attempts failed. The following certs could not be renewed:  
/etc/letsencrypt/live/countrystoveandfireplace.com/fullchain.pem (failure)

* * *

1 renew failure(s), 0 parse failure(s)

---

<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:** [October 22, 2018, 5:17pm UTC](https://community.letsencrypt.org/t/cert-failed-to-renew-and-now-has-hit-rate-limit/75479/4 "2018-10-22T17:17:12Z")

</div>

> [@joeker](#):
>
> There were too many requests of a given type :: Error creating new order :: too many failed authorizations

This is only a one-hour - limit, so it's not really a problem.

You can add `certonly --test-cert` to your command. So you get a test certificate, the testsystem has it's own limits. But don't install it - it's not valide -\> certonly.

---

<div class="post-metadata">

**Author:** ![joeker](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@joeker](https://community.letsencrypt.org/u/joeker)\
**Post date:** [October 22, 2018, 5:20pm UTC](https://community.letsencrypt.org/t/cert-failed-to-renew-and-now-has-hit-rate-limit/75479/5 "2018-10-22T17:20:30Z")

</div>

Ok I will try in an hour, thank you

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [October 22, 2018, 6:02pm UTC](https://community.letsencrypt.org/t/cert-failed-to-renew-and-now-has-hit-rate-limit/75479/6 "2018-10-22T18:02:02Z")

</div>

> [@joeker](#):
>
> So the first problem is failed renewal, and while trying to troubleshoot this, I’ve know run into the Rate Limit. I’ve had to disable SSL on the site.

Agreed, the first problem is that the cert expired 5 days ago.  
Did you receive any email notification that it was expiring? (if not, you should sign up for that)

---

<div class="post-metadata">

**Author:** ![joeker](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@joeker](https://community.letsencrypt.org/u/joeker)\
**Post date:** [October 22, 2018, 6:08pm UTC](https://community.letsencrypt.org/t/cert-failed-to-renew-and-now-has-hit-rate-limit/75479/7 "2018-10-22T18:08:34Z")

</div>

No I didn’t, that’s correct, I usually do for other domains

---

<div class="post-metadata">

**Author:** ![joeker](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@joeker](https://community.letsencrypt.org/u/joeker)\
**Post date:** [October 22, 2018, 6:21pm UTC](https://community.letsencrypt.org/t/cert-failed-to-renew-and-now-has-hit-rate-limit/75479/8 "2018-10-22T18:21:30Z")

</div>

UPDATE: the /root/certbot-auto renew --preferred-challenges http command worked. I’ve update the cron job accordingly.

Thank you for your assistance.

---

<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:** [November 21, 2018, 6:21pm UTC](https://community.letsencrypt.org/t/cert-failed-to-renew-and-now-has-hit-rate-limit/75479/9 "2018-11-21T18:21:31Z")

</div>

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