# Unable to renew cert (too many certificates already issued for exact set of domains)

**URL:** <https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630>\
**Category:** Help\
**Created:** [August 6, 2017, 7:52pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630 "2017-08-06T19:52:08Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![baptiste](https://avatars.discourse-cdn.com/v4/letter/b/cab0a1/32.png) [@baptiste](https://community.letsencrypt.org/u/baptiste)\
**Post date:** [August 6, 2017, 7:52pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/1 "2017-08-06T19:52:08Z")

</div>

Hello,  
Since few weeks, i can’t renew few of my certs who have the same domain.  
I have this message: “There were too many requests of a given type :: Error creating new cert :: too many certificates already issued for exact set of domains”.  
And when i check one of this, i see a lot of certs:

 ![Capture](https://sea3.discourse-cdn.com/letsencrypt/uploads/default/original/2X/a/abd0e4e2f4571e0629edddf28dc49147c487e9ec.PNG)  
How can i fix this ?  
Thanks

---

<div class="post-metadata">

**Author:** ![sahsanu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sahsanu/32/89984_2.png) [@sahsanu](https://community.letsencrypt.org/u/sahsanu)\
**Post date:** [August 6, 2017, 8:21pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/2 "2017-08-06T20:21:37Z")

</div>

Hi @baptiste,

You didn’t give too much info but seems the renews follow a pattern (once on Tuesday, twice on Wednesday, twice on Thursday and once on Saturday) and so on… you shoud check if you have a task, cronjob, etc. in your server and review what the automated command does because it is not checking whether the certs need to be renewed, it is renewing them always.

Good luck,  
sahsanu

---

<div class="post-metadata">

**Author:** ![baptiste](https://avatars.discourse-cdn.com/v4/letter/b/cab0a1/32.png) [@baptiste](https://community.letsencrypt.org/u/baptiste)\
**Post date:** [August 6, 2017, 8:29pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/3 "2017-08-06T20:29:19Z")

</div>

Hi @sahsanu,  
Thanks for your reply. Indeed, I have a crontab every monday who try to renew all certs who gonna expires.  
I just came to disable this cron. When i will be able to renew my certs ?  
Wich info do you need ?  
Have a nice day.

---

<div class="post-metadata">

**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:** [August 6, 2017, 8:34pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/4 "2017-08-06T20:34:09Z")

</div>

> [@baptiste](#):
>
> Thanks for your reply. Indeed, I have a crontab every monday who try to renew all certs who gonna expires.
> 
> I just came to disable this cron.

You're demonstrably creating certificates twice a day, though, not just on Mondays.

It's actually recommended to check twice a day, not once a week, but only to _check_ twice a day, not to create unnecessary certificates.

Please fill in the rest of the help information.

* * *

Please fill out the fields below so we can help you better.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

---

<div class="post-metadata">

**Author:** ![sahsanu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sahsanu/32/89984_2.png) [@sahsanu](https://community.letsencrypt.org/u/sahsanu)\
**Post date:** [August 6, 2017, 8:38pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/5 "2017-08-06T20:38:11Z")

</div>

> [@baptiste](#):
>
> Indeed, I have a crontab every monday who try to renew all certs who gonna expires.

None of the certs you are showing in the screenshot have been renewed on Monday so, are you sure this is the only cron job running in your server? If it is, are you sure it is running only every Monday?.

> [@baptiste](#):
>
> When i will be able to renew my certs ?

You should already have your certs renewed. I don't know if the certificates showed in the screenshot are for the same subset of domains but next Tuesday seems a good date to be able to renew them.

Cheers,  
sahsanu

---

<div class="post-metadata">

**Author:** ![baptiste](https://avatars.discourse-cdn.com/v4/letter/b/cab0a1/32.png) [@baptiste](https://community.letsencrypt.org/u/baptiste)\
**Post date:** [August 7, 2017, 4:17pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/6 "2017-08-07T16:17:56Z")

</div>

In my crontab i have:  
0 0 \* \* 1 /scripts/renewCerts.sh \>/dev/null 2\> /var/log/cron.error.log  
My script renew and send an email with the output of the script.  
I use certbot, it’s can be him who try to renew ?  
Thanks

---

<div class="post-metadata">

**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:** [August 7, 2017, 4:32pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/7 "2017-08-07T16:32:05Z")

</div>

What does `/scripts/renewCerts.sh` do

Edit:

Have you ensured that no other cron jobs or systemd timers exist?

And the other information requested?

---

<div class="post-metadata">

**Author:** ![baptiste](https://avatars.discourse-cdn.com/v4/letter/b/cab0a1/32.png) [@baptiste](https://community.letsencrypt.org/u/baptiste)\
**Post date:** [August 9, 2017, 6:55pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/8 "2017-08-09T18:55:43Z")

</div>

Hello,  
renewCerts.sh doing this:  
#!/bin/bash  
tmpFile=/tmp/renewCert.tmp  
if [-f $tmpFile]; then  
rm $tmpFile  
fi  
certbot renew --post-hook “/usr/sbin/service nginx reload” \> tmpFile 2\>&1 sed -i 's//  
/’ tmpFile tmpContent=(cat tmpFile) renewed=(cat tmpFile | sed '1,/:/d' | sed ' d’ | sed ‘s/^[\t]_//;s/[\t]_$//’)  
/usr/sbin/sendmail -F “letsencrypt@$HOSTNAME” -f “LetsEncrypt” -t “who@host.ext” \<\< EOM  
Subject: [LETSENCRYPT] Renouvellement des certificats  
Content-type: text/html; charset=utf-8

```
<h1>Résumé :</h1>
<p>$renewed</p>
<br>
<h1>Détails :</h1>
<p>$tmpContent</p>
EOM

if [-f $tmpFile]; then
        rm $tmpFile
fi

```

I dont know wich jobs or systemd can try to renew.

Two days ago, i have disable renewCerts.sh in my crontab, but…  
 ![image](https://global.discourse-cdn.com/letsencrypt/original/2X/6/680e19e4d6cc7ece5ba655b1211abfcc6a5ed4a9.png)  
Have a nice day

---

<div class="post-metadata">

**Author:** ![baptiste](https://avatars.discourse-cdn.com/v4/letter/b/cab0a1/32.png) [@baptiste](https://community.letsencrypt.org/u/baptiste)\
**Post date:** [August 9, 2017, 6:56pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/9 "2017-08-09T18:56:18Z")

</div>

More information about one of this ID:

 ![image](https://sea3.discourse-cdn.com/letsencrypt/uploads/default/original/2X/a/af03fa56b3d53c5f3968da2de9bc6f1f8e64a4b1.png)

---

<div class="post-metadata">

**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:** [August 9, 2017, 10:09pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/10 "2017-08-09T22:09:16Z")

</div>

So you definitely must have something else trying to get these certificates. It’s interesting to see that the issuance events happen at about two different times of day, around 23:00 or 10:00 UTC. (The certificate `notBefore` date will be set to one hour prior to the true issuance time to reduce problems for clients that have their time set incorrectly.)

What kind of software runs on this machine? Are you using any sort software like Caddy or cPanel that might include its own certifical-renewal code?

---

<div class="post-metadata">

**Author:** ![baptiste](https://avatars.discourse-cdn.com/v4/letter/b/cab0a1/32.png) [@baptiste](https://community.letsencrypt.org/u/baptiste)\
**Post date:** [August 10, 2017, 5:49pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/11 "2017-08-10T17:49:55Z")

</div>

I haven’t any pannel, i use certbot standalone, nginx and crontab for automatization.  
Can i see who try to renew ? By IP or by any other information ?  
Thanks

---

<div class="post-metadata">

**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:** [August 10, 2017, 6:23pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/12 "2017-08-10T18:23:28Z")

</div>

@cpu, do you think we can give out any more information about that?

---

<div class="post-metadata">

**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:** [August 10, 2017, 6:24pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/13 "2017-08-10T18:24:01Z")

</div>

> [@baptiste](#):
>
> Can i see who try to renew ? By IP or by any other information ?

By the way, they actually _succeed_ when they try, so they must have a considerable level of control over your domain name. 🙂

---

<div class="post-metadata">

**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:** [August 11, 2017, 4:33pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/14 "2017-08-11T16:33:49Z")

</div>

> [@schoen](#):
>
> @cpu, do you think we can give out any more information about that?

I'm hesitant to give out specifics like IP addresses or email addresses. I can say the following:

1. it seems to always be the same UA, Certbot 0.10.2, requesting a new-cert for the `www.web01.pixelads.fr` domain (and other `pixellads.fr` domains)
2. it's always the same ACME account, even for the requests hitting the rate limit (I assume some of those must be the OP). The account email is something at the base domain being requested.
3. the requests all come from the same IPv6 address

I'm not sure how to suggest @baptiste finds this certbot installation. It certainly seems like there is one that is going off-the-rails.

---

<div class="post-metadata">

**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:** [August 11, 2017, 4:47pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/15 "2017-08-11T16:47:05Z")

</div>

Thanks, that seems like useful information.

---

<div class="post-metadata">

**Author:** ![baptiste](https://avatars.discourse-cdn.com/v4/letter/b/cab0a1/32.png) [@baptiste](https://community.letsencrypt.org/u/baptiste)\
**Post date:** [August 14, 2017, 6:03pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/16 "2017-08-14T18:03:14Z")

</div>

How many time i must wait to can renew my certs ?  
If i remove certbot from my server during one week, i gonna haven’t any renew ? Can i keep my certs ?  
This solution is the last one 🙂  
Thanks for all

---

<div class="post-metadata">

**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:** [August 14, 2017, 6:46pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/17 "2017-08-14T18:46:00Z")

</div>

Maybe you can look in `/var/log/letsencrypt` to see if you have evidence that Certbot is somehow still being run on this system? Every time it runs, it should create a new log file there.

---

<div class="post-metadata">

**Author:** ![baptiste](https://avatars.discourse-cdn.com/v4/letter/b/cab0a1/32.png) [@baptiste](https://community.letsencrypt.org/u/baptiste)\
**Post date:** [August 20, 2017, 8:14am UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/18 "2017-08-20T08:14:39Z")

</div>

After verification, since i have remove certbot from my server, i haven’t any renew.  
How many time i must wait before i can renew ?  
Thanks

---

<div class="post-metadata">

**Author:** ![silverfix](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/silverfix/32/15707_2.png) [@silverfix](https://community.letsencrypt.org/u/silverfix)\
**Post date:** [August 20, 2017, 4:49pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/19 "2017-08-20T16:49:01Z")

</div>

up, exactly same issue here ☹

---

<div class="post-metadata">

**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:** [August 20, 2017, 6:33pm UTC](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630/20 "2017-08-20T18:33:33Z")

</div>

@baptiste, according to my calculations, you should be able to renew already. Of course, it would be great to understand why the previous unintended renewals were happening and where those certificates were going.

[Next page](https://community.letsencrypt.org/t/unable-to-renew-cert-too-many-certificates-already-issued-for-exact-set-of-domains/39630.md?page=2)
