Not sure what kind of rate limit was exceed

[avhacker]

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

My domain is: smartnetwork.tw

I ran this command: I use both dehydrated and SSLforfree to generate and update my SSL.

It produced this output:
{
“type”: “urn:acme:error:rateLimited”,
“detail”: “Error creating new cert :: too many certificates already issued for: smartnetwork.tw”,
“status”: 429
}

My web server is (include version):
nginx-1.10.2-5.el6

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

My hosting provider, if applicable, is:

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.

I tried to create a new SSL certificate today and got this error. Last week, I updated about 19 certificates. All of the certificates are for internal usage only. I’m not sure when limitation I hit but the update process is just to loop over all my certificate directories and acquire an update one by one. Does this count to 20 certificates per domain per week? Could you temporary increase my quota? I’ll adjust the update process not to update certificates so frequently. Thanks.

[schoen]

Hi @avhacker,

The rate limits are documented at

https://letsencrypt.org/docs/rate-limits/

There is no way to override them temporarily.

One thing that some people have found confusing about the rate limits is that the order in which you perform operations matters: renewals (getting new certificates with identical domain coverage to previously-issued certificates) are not restricted by the certificates per registered domain limit, but do count against it. Therefore, you can get more certificates in total by issuing all new certificates prior to performing any renewals. (This order-dependence is going to be removed in the future.)