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

Rate Limit 403 #36

Open
jaikishantulswani opened this issue Apr 17, 2021 · 3 comments
Open

Rate Limit 403 #36

jaikishantulswani opened this issue Apr 17, 2021 · 3 comments

Comments

@jaikishantulswani
Copy link

@rmarot @hisxo Gitgraber throwing 403 even after using 70+ tokens.

@baxter2
Copy link
Contributor

baxter2 commented Apr 18, 2021

Are you using tokens generated by the same Github account? If so according to this https://docs.github.com/en/rest/overview/resources-in-the-rest-api#rate-limiting you can only make 5000 request an hour even between all of your OAuth tokens. So perhaps you've gone over that limit?

For API requests using Basic Authentication or OAuth, you can make up to 5,000 requests per hour. Authenticated requests are associated with the authenticated user, regardless of whether Basic Authentication or an OAuth token was used. This means that all OAuth applications authorized by a user share the same quota of 5,000 requests per hour when they authenticate with different tokens owned by the same user.

If you want to make 10000 request an hour, you will have to create another OAuth token from a different Github account then you will be able to increase your rate limit count.

@jaikishantulswani
Copy link
Author

jaikishantulswani commented Apr 18, 2021

@baxter2 Thank you for your quick reply on this, so basically how many accounts should I have to use to run gitgraber in monitor mode?

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
@jaikishantulswani @baxter2 and others