429 new-order error: A new certificate is not being issued

Help
1

Hello!
My domain is: mail.omsksanepid.ru
( crt.sh | mail.omsksanepid.ru )

Please specify by what limit the intervals were exceeded when trying to issue a domain certificate mail.omsksanepid.ru

There is no information about this in the response of your servers (usually, with such an error, the server adds a Retry-After to the header with an interval after which it is possible to repeat the request or a message with information about which limit has been exceeded).

Error text:
ClientResponseError(RequestInfo(url=URL('https://acme-v02.api.letsencrypt.org/acme/new-order'), method='POST', headers=/', 'Accept-Encoding': 'gzip, deflate', 'User-Agent': 'Python/3.12 aiohttp/3.9.3', 'Content-Length': '1099')>, real_url=URL('https://acme-v02.api.letsencrypt.org/acme/new-order')), (), status=429, message='Too Many Requests', headers=https://acme-v02.api.letsencrypt.org/directory;rel="index"', 'Replay-Nonce': 'OkLCVishxFmyXgC-RteQn0RSbfnyeV6JM5EiJ92EtG9kyRUc-OA')>)

2

I agree the message is confusing. Is the faulty message your only concern?

It looks like you are reaching the new-order request limit of 300 requests per second. Although, the docs say that should receive a 503 error and a retry-after. But, your message is a 429. So, I am not sure if the docs are wrong or we are seeing something different.

All rate limits, including the 300 per second new-order limit, are described here: Rate Limits - Let's Encrypt

Is it possible you made more than 300 requests in a second? If so, can you explain more about the need for you to do that?

4 Likes