# Too many requests of a given type **URL:** \ **Category:** Help\ **Created:** [July 26, 2017, 11:03am UTC](https://community.letsencrypt.org/t/too-many-requests-of-a-given-type/38917 "2017-07-26T11:03:00Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![MPolymath](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mpolymath/32/15144_2.png) [@MPolymath](https://community.letsencrypt.org/u/MPolymath)\ **Post date:** [July 26, 2017, 11:03am UTC](https://community.letsencrypt.org/t/too-many-requests-of-a-given-type/38917/1 "2017-07-26T11:03:00Z")
My domain is: keepcontrol.space I ran this command: certbot-auto --apache -d staging.keepcontrol.space It produced this output: root@keepcontrol:~# certbot-auto --apache -d staging.keepcontrol.space Saving debug log to /var/log/letsencrypt/letsencrypt.log Cert is due for renewal, auto-renewing… Renewing an existing certificate Performing the following challenges: tls-sni-01 challenge for staging.keepcontrol.space Waiting for verification… Cleaning up challenges An unexpected error occurred: There were too many requests of a given type :: Error creating new cert :: too many certificates already issued for exact set of domains: staging.keepcontrol.space Please see the logfiles in /var/log/letsencrypt for more details. My web server is (include version): Apache/2.4.7 (Ubuntu) The operating system my web server runs on is (include version): Ubuntu 14.04.5 LTS My hosting provider, if applicable, is: digitalocean 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 It has been around 20 days and I still get the same error. Here are some logs that might be useful in debugging the issue: The result of sudo certbot certificate: Renewal configuration file /etc/letsencrypt/renewal/staging.keepcontrol.space.conf produced an unexpected error: expected /etc/letsencrypt/live/staging.keepcontrol.space/cert.pem to be a symlink. Skipping. Revocation status for /etc/letsencrypt/live/keepcontrol.space/cert.pem is unknown * * * Found the following certs: Certificate Name: keepcontrol.space-0001 Domains: keepcontrol.space Expiry Date: 2017-08-26 15:26:00+00:00 (VALID: 31 days) Certificate Path: /etc/letsencrypt/live/keepcontrol.space-0001/fullchain.pem Private Key Path: /etc/letsencrypt/live/keepcontrol.space-0001/privkey.pem Certificate Name: keepcontrol.space Domains: staging.keepcontrol.space Expiry Date: 2017-06-28 10:22:00+00:00 (INVALID: EXPIRED) Certificate Path: /etc/letsencrypt/live/keepcontrol.space/fullchain.pem Private Key Path: /etc/letsencrypt/live/keepcontrol.space/privkey.pem Certificate Name: [stagingkeepcontrolspace-1olbxacya.stackpathdns.com](http://stagingkeepcontrolspace-1olbxacya.stackpathdns.com) Domains: [stagingkeepcontrolspace-1olbxacya.stackpathdns.com](http://stagingkeepcontrolspace-1olbxacya.stackpathdns.com) Expiry Date: 2017-10-06 11:10:00+00:00 (VALID: 72 days) Certificate Path: /etc/letsencrypt/live/stagingkeepcontrolspace-1olbxacya.stackpathdns.com/fullchain.pem Private Key Path: /etc/letsencrypt/live/stagingkeepcontrolspace-1olbxacya.stackpathdns.com/privkey.pem ## The following renewal configuration files were invalid: /etc/letsencrypt/renewal/staging.keepcontrol.space.conf I also commented out this command in crontab today as I feared it might of been responsible: m h dom mon dow command 30 2 \* \* 1 /usr/local/sbin/certbot-auto renew \>\> /var/log/le-renew.log Has anyone encountered a similar issue ? Any help would be much appreciated. ---
**Author:** ![jared.m](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jared.m/32/17871_2.png) [@jared.m](https://community.letsencrypt.org/u/jared.m)\ **Post date:** [July 26, 2017, 11:52am UTC](https://community.letsencrypt.org/t/too-many-requests-of-a-given-type/38917/2 "2017-07-26T11:52:48Z")
Something on your machine has been issuing multiple certs for staging.keepcontrol.space every day for several days now. [https://crt.sh/?q=%keepcontrol.space](https://crt.sh/?q=%25keepcontrol.space) You should find out what’s gone rogue. Things to look for are automated tasks with either the --renew-by-default or --force-renewal options on the command line or in the ini file. This will force certbot to renew every time it runs instead of at the proper expiry period of 60 days. ---
**Author:** ![MPolymath](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mpolymath/32/15144_2.png) [@MPolymath](https://community.letsencrypt.org/u/MPolymath)\ **Post date:** [July 26, 2017, 1:34pm UTC](https://community.letsencrypt.org/t/too-many-requests-of-a-given-type/38917/3 "2017-07-26T13:34:48Z")
Thank you very much Jared.M. I will keep an eye out for further certificate demands and locate where the automation is coming from. ---
**Author:** ![MPolymath](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mpolymath/32/15144_2.png) [@MPolymath](https://community.letsencrypt.org/u/MPolymath)\ **Post date:** [July 27, 2017, 9:45am UTC](https://community.letsencrypt.org/t/too-many-requests-of-a-given-type/38917/4 "2017-07-27T09:45:39Z")
It seems like the certificates are no longer being automatically issued. I will await the 4 days missing before I can renew my certificate and give you feedback then. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [August 26, 2017, 9:45am UTC](https://community.letsencrypt.org/t/too-many-requests-of-a-given-type/38917/5 "2017-08-26T09:45:51Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.