Lego: 429 Too Many Requests Rate Limit Error

Created on 28 Apr 2017 · 11Comments · Source: go-acme/lego

At Heroku, we've been seeing the following frequently in our error logs:

acme: Error 429 - - <html> <head><title>429 Too Many Requests</title></head> <body bgcolor="white"> <center><h1>429 Too Many Requests</h1></center> <hr><center>nginx</center> </body> </html>

My understanding after speaking with LE is that this is the Overall Rate limit of 20 reqs/second.

We had hoped that ee0018c855fa43a43f29280a5be2e4b94f9ac991 and 45beff7ed309e190408d7ac1c89a7b7751596a73 would address this issue, but there still seems to be a problem.

CC @jsha

Source

RBeaudoin

👍1

All 11 comments

A quick look at the logs shows that you do seem to successfully stay under 20 reqs/second in general. How many times per day do you get this error? Can you share the IP addresses from which you get it?

jsha on 29 Apr 2017

👍1

@jsha thanks for looking into this, we are seeing this 2-3 times a day in production.

Unfortunately, that is the only information we get back in the error so I won't be able to provide the IP addresses.

RBeaudoin on 29 Apr 2017

If it's only 2-3 times a day, I wouldn't worry about it too much. It could be slight differences between xenolf/lego's internal rate limiting implementation and how we count rate limits on the server side. If you see an increase, please let us know!

jsha on 3 May 2017

We're now seeing it 7-9 times a day the past two days.

RBeaudoin on 3 May 2017

@jsha I can easily trigger it on staging with a fixed IP, could it be useful for you ?