Rate limit errors despite rate adjustment approved

Hey LetsEncrypt,

We have rate limits adjusted approved (6000 per week) for two of our accounts we use to obtain certificates which we have been using since Sept 2022.
Since January 04 2024, we have started seeing rate limit errors for our domain despite using these accounts that have higher rate limits.
Upon checking usage on our end, we see usage below the approved rate limits.
We would like to know more why we would see the rate limit errors even though we are using rate limit adjusted accounts.

My domain is: eastus2.azure.devel.cpdev.cloud

We use GitHub - go-acme/lego: Let's Encrypt/ACME client and library written in Go client to obtain certificates

Below is the error message:
acme: error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rateLimited :: Error creating new order :: too many certificates already issued for "cpdev.cloud". Retry after 2024-01-12T02:00:00Z: see Rate Limits - Let's Encrypt

I have confirmed you are using an account approved for a rate limit of 6000.

However, it does appear your usage is hitting that.

parsed.issuer.organization="Let's Encrypt" and cpdev.cloud and parsed.validity_period.not_before: [2024-01-04 to 2024-01-11]

This Censys search shows 7,297 leaf certs (because it's based on calendar days, their data doesn't align exactly with ours). You need a free account but you can do that search on https://search.censys.io/

You should submit a new rate limit adjustment request and we can increase your usage.


If OP is somehow convinced they're not supposed to hit the current rate limit, maybe there's something wrong with their setup? Maybe a good idea to look into that before increasing the rate limit :slight_smile:


Coming back to close the discussion here.
The issue was on our side where we accidentally included this domain in other set of domains we were trying to get rate adjustment, and ended up having 1000 rate limit for this domain.

The issue was resolved after resubmitting rate adjustment form to bring back the rate limit to previous levels.

Thanks for input and suggestion here from LetsEncrypt.
This discussion can be marked as resolved.


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