Too many certificates already issued - rate limit?


@bmw @jsha @kelunik


Rate limit on registrations per IP is now 10 per 3 hours up from 10 per day.
Rate limit on certificates per Name is now 10 per 59 days up from 6 per 59 days.

is that per Name as in common name of SSL certificate or per top level domain + subdomains ? As I ran into this at and I don’t have 10 ssl certificates for the common name i tried but do have a total of 10 ssl certificates if you include all top level and subdomains


2015-11-15      2016-02-13
2015-11-15      2016-02-13
2015-11-15      2016-02-13
2015-11-15      2016-02-13
2015-11-15      2016-02-13
2015-11-15      2016-02-13
2015-11-04      2016-02-02
2015-10-31      2016-01-29
2015-10-27      2016-01-25
2015-10-27      2016-01-25

I see I have 6x issued SSL certificates so hit the old rate limit ?

RateLimited for a specific domain
Failures registering new subdomain certs in public beta

Ah looks like i found my problem the auto renewal cronjob I set was running more frequently than every 2 months so ran into the 10 registrations per IP per 3hr limit :sweat_smile:

guess need to wait another day for rate limit to reset :slight_smile:


It’s per top level domain (aka “registered domain”) based on the Public Suffix List. It looks like you have 10 certificates under, so you have hit the limit. Hopefully you can continue testing against staging!


cheers @jsha… my cronjob mistakenly tried auto renewal every 1 min hehe… was giving LE servers a work out :innocent:

all fixed up now so auto renew is every 2 months :smiley:

But looks like i’ve have to continue tests on staging instead :frowning:


Hi, with 90 days lifetime this limits the certificates to 15 certs per “domain”.

  • domain.tld
  • www.domain.tld
  • imap.domain.tld
  • pop3.domain.tld
  • smtp.domain.tld
  • svn.domain.tld
  • community.domain.tld
  • chat.domain.tld
    Are already 8 Domains that mean more than 1/2 of the possible.
    While other firms that make money with their are excluded from the limit
  • blogspot.
    And for example is limited to 15 country postfixes ?


“During this beta test we have very tight rate-limiting in place. We plan to loosen these limits as the beta proceeds.”

The rate limit would be reduced in production. I imagine to levels where it could be used for any amount of certificates per domain.


yeah rate limit is only for beta stages


You can always combine them into a single certificate.


We will always have some rate limits in place to help mitigate excessive use, but they will probably become somewhat more relaxed over time.


cheers @jsha

you’ll need to formally document those rate limits on the documentation and/or web site too :slight_smile:


kelunik, I don’t think you are correct. One certificate per domain, with no wildcards or virtual or parked domains. Can someone else confirm that I am correct?


You can issue certificates for multiple domains, see, the certificate is valid for and using the Subject Alternative Name field. I implemented the protocol in PHP, I should know how issuance works. :wink:


Sorry, when I visit, my browser cannot find a valid certificate. Can someone else please resolve this question?

I’m pretty sure that LE automatic support is not intended to support virtual domains, even for www.


Fixed, didn’t have as server_name so it used the default one ( and served the wrong certificate. As the main domain is not actively in use, I didn’t ever try www., thanks.


I verify the fix, and see the alternate name in the certificate. It is unfortunate that so many webmasters are obtaining separate certificates for and I hope the final automated version of the LE client will handle (or offer to handle) such common situations itself.


I have no get CERT and it is close.


i think LE documentation should just mention that in examples i.e. -d -d to cover them.


Yes, that is an excellent example that should be provided in the beta client documentation. And the functionality should be included in the final released full automation. Thanks.

Public beta rate limits

I’m running many machines depending on dyndns domains. So now I’m stuck with not getting a cert for them, because all the other customers where faster then me.

“Too many certificates already issued for:”

Will there be a whitelist for dyndns providers endings, because they’re only giving out subdomains to their customers?

Within the closed beta I didn’t stumble across this problem… And now I’m also unable to renew my cert.


It would be great if the exceptions are not only for dyndns domains but also for huge communities like There are more than 200 subcommunities each having their own subdomain and many using their own servers and taking care of their own server infrastructure and thus needing their own certificates.
Right now has already reached the limit of 10 certificates.