Error 429 - too many certificates already issued for:

Hey there,

any chance to find out why I’m getting Error 429 - too many certificates already issued for:
Last Cert for this Domain was issued on 31.07.2017 (

Guess it’s because of some Subdomains - but not sure?
And I would need the Cert for this Domain rather fast … as current one is expired … :wink:

Andreas Schnederle-Wagner

Have a look at:
webpage attached with txt (1.6 MB)

aahhh - didn’t know I can do Wildcard Queries with % … thx for that @rg305! :wink:

But I still don’t find the reason why I get 429 Error - all those * CERTs should NOT account against the Limit - as this Domain is listen on the PSL:

PSL List Entry:

// Futureweb OG :
// Submitted by Andreas Schnederle-Wagner

Maybe @cpu can have a look at why this is happening.
Going over the list, it does seem that all the names are included in the PSL.
If you can, please give an example of a domain that produced the error 429 message. itself throws the Error - our Main Domain … :-/

{“type”:“urn:acme:error:rateLimited”,“detail”:“Error creating new cert :: too many certificates already issued for:”,“status”:429}

I see.
Yes, it seems the math is a bit off, which should be something like:
count all ( OR * )
minus PSL listed ( * OR * )

But seems to be including just:
count all ( OR * )
which exceeds your allowed.

1 Like

@futureweb, your issue may be related to this thread: [Solved] Rate limit increase didn't seem to take
Please try it again and let us know if it is still ongoing.

Even if you had genuinely exceeded the rate limit, you should still be able to get a renewal of an existing certificate. Have you tried requesting a certificate with the exact same set of domains as one of the recently expired ones for For example as on -,,, - that way you might at least get a cert to get you back up and running on HTTPS for now.


I’m guessing that public suffix subdomains are still being counted towards the registered domain’s rate limits. That is, all the certificates issued for are exempted from rate limits, but these certificates are still counted towards the rate limits for, which is not exempted.

There was a similar issue with the rate limits for the exact match of the public suffix domain:

@cpu or @jsha can confirm if this is what is really happening and if they intend to fix it or if you should request a rate limit exemption for to work around it.

1 Like

Yep, that is correct. As someone pointed out above, you should be able to renew any existing certificates you have. You may also be interested to read about, which should decrease the pain in this situation a bit.

If you’re trying to issue for new domains under (but not under and finding that you can’t, you may want to fill out the rate limit request form at the bottom of

BTW a small note since it’s nonintuitive: wildcards have a special meaning in the public suffix list. * in the list means that is a public suffix, and so is, and so on.


@rg305 - thx for your effort in helping me on that! :wink:
@jmorahan - thx for the Tipp with renewing the exact same/existing Cert - did the Trick to get the Cert up & running again! :smile:
@Patches - that’s the problem! :frowning:

@jsha - thx for confirming - as we need to issue some NEW Certs under I filled the “rate limit request form” as advised - hope it gets processed quick :slight_smile:

Thank you all for the help, bye from sunny Tirol, Austria


@jsha - any chance to speed up the “rate limit request” a little bit? Because of the “PSL Subdomains count against non PSL Parent Domain” I can’t issue some new Certs we really would need … :frowning:


I’ve bumped your request.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.