My domain is:
I ran this command:
certbot certonly --debug --webroot -w /var/www/redirect/public_html -d local.intranet.1stdibs.com
It produced this output:
Error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new cert :: too many certificates already issued for: 1stdibs.com
My web server is (include version):
The operating system my web server runs on is (include version):
CentOS Linux release 7.3.1611 (Core)
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):
We’re using certbot/letsencrypt for around 200 internal-use-only subdomains; I naturally ran into the 20/week limit, as they are all under intranet.1stdibs.com, but since completing that initial task, I have had no issues with renewals or extra subdomains/other domains.
On 2017-09-08, I started receiving the “too many certificates” error, so I tried adding this subdomain to a working cert renewal, and later, attempted to use the python script linked here to clean out pending authorizations; I still receive the “too many certificates” error.
Any idea what is happening here? crt.sh suggests that we aren’t generating a ridiculous number of certificates (we are using certbot, so I assume it is playing nice). I’m not sure if that pending-authorization-clearing script actually works as advertised, or if that is even really my problem. Really been enjoying using LE for our internal certs and hoping we aren’t hitting some fixed system limit!