GitHub 403 API rate limit exceeded - Approach to a solution?
Mazso opened this issue · 2 comments
Some (many?) UPM users are running into the problem that updating doesn't work. Instead, they are getting an error message from GitHub "403 API rate limit exceeded for 81.169.144.135".
Which is interesting: The IP address from the above error message is copied from a post on the MODx forum. But on at least one of my MODx installations I got the same error message with exactly the same IP address.
After some googling, I think this isn't a MOdx problem. GitHub actually has a bandwidth limit https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration. What is particularly interesting is that there is a very low rate for MacOS. See also this discussion: actions/runner-images#602
My wild guess: it doesn't matter if you hit the limit yourself - you'll get the error message when all users together hit the limit. And if you are on MacOS - bad for you. It doesn't matter if you reinstall UPM or use a personal GitHub token.
I have no suggestions on how to solve the problem. But maybe someone else will.
Have you seen the possible solutions to the problem on this page? Search for "GitHub API Rate Limit Exceeded" on that page.
Have you seen the possible solutions to the problem on this page? Search for "GitHub API Rate Limit Exceeded" on that page.
Sure. I tried it with an ugm_github_token - no luck. Which is odd: I have installations where there are no problems. But if I call another MODx site with the same IP, I get a 403 from GitHub - with an IP that I certainly never used. Trying it again after days doesn't help. Clearing the cache doesn't do anything, neither does reinstalling UPM.
I will try a local installation of the JSON version file.