I am trying to renew my certificate but I received a too many requests for at least two of my domain names. tail of the log file: File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/letsencrypt/client.py”, line 228, in _obtain_certificate authzr) File “/root/.local/share/letse…

There’s a rate limit of 5 certificates per domain (TLD + 1, so subdomains count too) per 7 days in place. You will have to wait a week.

Yes. You’ll get that error if you’ll just keep requesting certificates: 01:12:f9:53:70:03:61:ad:ea:26:b1:5d:95:3f:cf:f2:d8:7f on Jan 17 21:49:00 2016 GMT 01:cb:38:a7:5a:9a:6b:a1:cf:f6:ef:6a:7a:bf:b3:1e:46:8d on Jan 17 21:53:00 2016 GMT 01:d4:bf:c6:11:b4:69:57:9a:5e:6b:94:43:44:3c:19:de:39 on Jan …

That’s junk, I added new domain names, why didn’t that renew my certificate? And now I cannot renew because I added new domain names? Junk. Junk Junk Junk. Please fix.

Once a certificate has been issued, it’s issued. Period. It’s signed, it’s submitted to the Certificate Transparency logs. Done deal. If you “”“change”"" something to the certificate, you’ll get a new one. You just can’t “edit” a previously issued certificate… Which, of course, adds to the issued c…

Adding a new domain or renewing a certificate is no different from issuing a new certificate. Both will create a new certificate, which is the rate-limited operation (necessary to limit the OCSP signing load). If you regularly need certificates for new domains (i.e. a few times a week), a better op…

Except they did not, the certificate expired jan 19th. Something is wrong, and my server is now crippled by this. I understand this is beta but I am drawing your attention to this because it is a huuuuuuge issue. There must be a foolproof way to renew certificates, with zero failures, for you guys…

Yes, your original certificate expired on Jan 20 00:53:00 2016 GMT. I don’t know how you ended up with all those quadruple identical certificates, but I’m quite sure it’s not the fault of Let’s Encrypt. There’s no way the official client would have done so without user influence and/or misconfigure…

It’s hard to comment on this without knowing how you’re renewing your certificates. crt.sh clearly shows 5 domains requested for your domain in the last 7 days. Without knowing how you’re invoking the client, we can’t really help you figure this one out. Let’s Encrypt currently doesn’t automaticall…

I was using this command to renew: letsencrypt-auto certonly -v -t -c /etc/letsencrypt/domain.ini domain.ini was based on sample configs. I did add domain names recently, and I ran the command to add those domains and I assumed the new certificates would include new expirations but obviously that…

There’s nothing to “update”. That’s not how certificates work. Once issued, always issued.

Cannot renew certificate "too many requests"

Help

Topic		Replies	Views
Too many certificates already issued Server	24	78171	May 23, 2017
New rate limit question	22	8776	April 19, 2016
Error creating new cert :: too many certificates already issued for exact set of domains Help	20	20456	October 21, 2017
Public beta rate limits Issuance Tech	131	63782	December 22, 2016
Error creating new order :: too many certificates already issued for exact set of domains Help	4	4201	June 5, 2020

Cannot renew certificate "too many requests"

Related topics