urn:ietf:params:acme:error:rateLimited

[Mosandl]

Hello,

we get this error since 1 week. we don't know from where this request are comming. How we can identify this?

ERROR: An error occurred while sending post-request to https://acme-v02.api.letsencrypt.org/acme/new-order (Status 429)
Details:
HTTP/2 429
server: nginx
date: Thu, 21 Oct 2021 07:50:06 GMT
content-type: application/problem+json
content-length: 203
boulder-requester: 315421
cache-control: public, max-age=0, no-cache
link: https://acme-v02.api.letsencrypt.org/directory;rel="index"
replay-nonce: 0102hdKAQq5T2nwvukoEgF4-PIZQjBmVC2ravkHWm_L9fuc
{
"type": "urn:ietf:params:acme:error:rateLimited",
"detail": "Error creating new order :: too many currently pending authorizations: see Rate Limits - Let's Encrypt",
"status": 429
}

Thanks

[griffin]

Welcome to the Let's Encrypt Community, Thomas

This is a telltale sign of a malfunctioning ACME client. This tool can help clear things up:

https://tools.letsdebug.net/clear-authz

[jple]

Hi! Do you also have monitoring set up on your side so that you know when you are approaching this limit?

You might be getting that many certs or as Griffin mentioned, it might be a buggy ACME client. If you are monitoring your pending authorizations and can't see where these are, it's likely your ACME client is leaking authorizations somewhere.

We can raise the pending authorizations rate limit but if your ACME client is leaking authorizations, it will just fill up again!

[Mosandl]

Hi

Can you change the limit for both accounts I pasted by mail ?

Then we can Analyse better on our side

Thanks

[Osiris]

@Mosandl

Then we can Analyse better on our side

I don't fully understand: how does increasing the rate limit help you with analysing your malfunctioning ACME client?

[rg305]

They can see MORE malfunctions / hour - LOL

[Mosandl]

yep you are true. i think we should use a new account as it looks like that someone else within our department is doing something with it.

I already shared one a account by mail and we will create a second one wich you will get soon.
The form is also filled up. please extend then the limits again, like we had in the other account as we are running a demo environment with more than 30.000 DNS entry's.

thanks.

[jple]

Hey community team! I realize this request is a bit tricky as it has a lot of history with Let's Encrypt. I will follow up with the OP to iron out any remaining wrinkles.

Thanks again for all your work!