Per https://community.letsencrypt.org/t/beta-program-announcements/1631 there are rate limits in Private Beta. This thread was closed. What will be rate limits in Public Beta, if any?

[image] gutschke: If you need more than that, maybe it would make sense to add your domain to the public suffix list (effectively lifting this limit)? Please do not suggest that. Being in the list has important implications on how browsers and clients will treat your domain. You should not re…

Certainly I could stagger them (and have) - for that specific limited case, however, I also have a similar situation where staggering them isn’t really that user friendly and the shared-deployment doesn’t work either since it’s spread across lots of different developers with different systems. In m…

Fair enough. I should have been a little more verbose. If you have lots of different sub-domains, there is a good chance that these subdomains are entirely independent (e.g. they are in fact delegated to different owners). In that case, marking the top-level domain as a public suffix is probably th…

Agree completely on the domain not belonging on the public list when it’s different subdomains because each is a different server/service. In a third case of mine (student and individual desktops systems at a university) - for that, their designated top level subdomain would likely be completely app…

Long thread, but the issue is very relevant. Imagine having to wait 7 days before being able to take the next step, since most people issuing are developers and not end clients, this means we delay the delivery of our work by a full week because there was an error on some script (that we used to ge…

[image] dreamerworks: since most people issuing are developers and not end clients, this means we delay the delivery of our work by a full week because there was an error on some script (that we used to generate the certificates). Use the staging server ! (As is said on the rate limits documen…

There might be different meanings of “developer” here :wink: I’m assuming @Osiris is meaning an ACME script developer, and hence absolutely correct. I have a feeling that @dreamerworks is possibly meaning a website / animation / … developer and is placing the work they do for their client on a …

The problem is these limits are being hit for real use - not staging/development. Right now - with both renewals AND new certs counting against the 20/week limit - if you already have 100+ certs in use, it is really easy to have used up the 20 in renewals, and then suddenly it’s several days before…

Good point :slight_smile: Perhaps the rate limit form would be the answer for @dreamerworks problem.

[image] nneul: Right now - with both renewals AND new certs counting against the 20/week limit - if you already have 100+ certs in use, it is really easy to have used up the 20 in renewals, and then suddenly it's several days before you create any new cert. From the rate limits documentation : …

Public beta rate limits

Issuance Tech

nneul December 22, 2016, 5:06pm 127

Topic		Replies	Views
Too many certificates already issued - rate limit? Issuance Tech	41	19733	January 13, 2017
New rate limit question Uncategorized	22	8895	April 19, 2016
Certificates/Domain Limit Problem Issuance Policy	22	6629	June 23, 2016
Rate limit reached based on the error message, but logs says different Help	27	1918	November 4, 2021
Too many certificates already issued Server	24	78326	May 23, 2017

Public beta rate limits

Related topics