-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting many 429 errors lately when calling the API #162
Comments
Hey, I have just received the following error: Some calls also work. |
Hi guys, thanks for the report! I can confirm that I got a bunch of spurious 429s in manual testing. There is indeed a rate limit of 10 requests per second (with a burst size of 50), but given that you haven't changed anything on your side I doubt you're hitting that. My first guess was that we're reaching the maximum capacity for our current setup, but upgrading the server hasn't fixed the situation. My next guess is that either I screwed up configuring traefik's rate limit middleware or that that middleware has a bug. I have temporarily completely disabled rate limiting - can you confirm that you're no longer getting 429s? |
Hey, thanks for the quick response. |
Hey @jdemaeyer, |
Thanks a lot for the fast responses! I'll be playing around with the rate limit configuration for a bit so you might run into a few errors in the next hours |
Hello,
I am getting many 429 errors lately - I did not change something significantly on my end.
Has something changed on the API? Is there a rate limit now, maybe? What would that be, so that I can adjust accordingly.
Thanks for your help!
The text was updated successfully, but these errors were encountered: