Skip to content
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

User getting 429 error #54

Open
djotaku opened this issue Oct 31, 2021 · 8 comments
Open

User getting 429 error #54

djotaku opened this issue Oct 31, 2021 · 8 comments

Comments

@djotaku
Copy link

djotaku commented Oct 31, 2021

User of my software https://github.com/djotaku/ELDonationTracker is getting 429. I'm able to change my user ID to be her without issue. I used my software today so I know I'm not hitting the API too hard. Ideas on why she can't access the API?

Thanks

@timmixell
Copy link
Contributor

Hey @djotaku , the 429 indicates that the user in question was rate limited. We try to be as lax as possible with the rate limiting policy while still ensuring platform stability. Improving the integration experience is something I'm hoping we can revisit well ahead of game day 2022 to mitigate these kinds of issues. In the meantime: have you verified the user in question is still encountering the rate limit response?

@Technical-13
Copy link
Contributor

Hey @timmixell - we actually talked about this yesterday in the donordrive-support channel of Discord. You can find the discussion at https://discord.com/channels/301922093258375179/363006542880047104/904398150628937758

@keithdhodo
Copy link

@timmixell
I can attest that I am getting a 429 error in my application which is triggering requests to the donordrive API every three minutes.

How is the system determining when it should return 429? Is this based on an IP address for a client? It seems like no matter what I am doing right now I'm getting 429.

@Technical-13, I am not able to access that discord. What is the code for donordrive-support so I can join the discord on behalf of my group?

@djotaku
Copy link
Author

djotaku commented Nov 2, 2021

Hey @djotaku , the 429 indicates that the user in question was rate limited. We try to be as lax as possible with the rate limiting policy while still ensuring platform stability. Improving the integration experience is something I'm hoping we can revisit well ahead of game day 2022 to mitigate these kinds of issues. In the meantime: have you verified the user in question is still encountering the rate limit response?

She's still having the issue. It's my usual app, so she's not doing anything to cause rate limiting since it's not checking too often and it works for me using the same app. I was going to try a "fake" User-Agent if that would help with CloudFare, but I'd prefer to do things the right way if I can.

@Technical-13
Copy link
Contributor

@Technical-13, I am not able to access that discord. What is the code for donordrive-support so I can join the discord on behalf of my group?

https://discord.gg/XDqaYAcehM

@timmixell
Copy link
Contributor

A 3 minute interval shouldn't be kicking off any restrictions. I'll need to take this to our infrastructure team for further guidance. I see the convo you all are having in the Discord channel. We may reach out to you individually if we need additional information. Thanks!

@keithdhodo
Copy link

My issues has been resolved. Resolution: I added user-agent headers and worked with the DonorDrive team to get my value I was passing for user-agent added to an allowed list.

Headers = {
USer-Agent: {myvalue}
}

@djotaku
Copy link
Author

djotaku commented Nov 3, 2021

My user is OK now. Not sure if she got a new IP address or if it was coincidental. Feel free to close if everyone else is satisfied with the current situation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants