Repository navigation
[INFO] Common Error Codes (PLEASE CHECK FIRST) #1772
Description
Here you can find common error codes. Please check this list and the existing issues before creating a new issue. For commonly asked questions, see the FAQ.
General errors
Maximum retries exceeded
This is likely caused by the public Vercel instance reaching one of the Github GraphQL limits. Multiple PAT tokens have been used to overcome these limits (see github-readme-stats/blob/master/src/common/retryer.js) but due to the popularity of GitHub-readme-stats, they sometimes run out. The best solution is to deploy your own Vercel instance. Please check this guide on how this is done. You can find more information on this problem in #1471. You can also use #1471 to check if the Public Vercel instance is down and to let us know the limits are continuously being reached.
⚠️ PLEASE READ⚠️ Only comment on #1471 if nobody has commented in the last three days or if you have information that could help us solve the problem. If there already is a recent comment or the
label is attached, we are aware of the issue and are working on it. 🤓 Comments like "+1" and "same here" don't help anyone; they pressure the maintainer and spam their inbox. 💥
Activity
[-]Common error codes (PLEASE READ FIRST)[/-][+]COMMON ERROR CODES (PLEASE READ)[/+][-]COMMON ERROR CODES (PLEASE READ)[/-][+]COMMON ERROR CODES[/+][-]COMMON ERROR CODES[/-][+]Common Errors[/+][-]Common Errors[/-][+]Common Error Codes (Please check first)[/+][-]Common Error Codes (Please check first)[/-][+]Common Error Codes (PLEASE CHECK FIRST)[/+]rickstaa commentedon May 18, 2022
Please comment below if you think an error code is missing from this list 👍🏻.
[-]Common Error Codes (PLEASE CHECK FIRST)[/-][+][INFO] Common Error Codes (PLEASE CHECK FIRST)[/+]xorinzor commentedon May 20, 2022
rickstaa commentedon May 20, 2022
@xorinzor Thanks for letting us know. I, however, meant #1471. Somebody already flagged the problem there, so I added the
label to show that we are aware of the issue. I updated the text in this issue to:
For now, I would advise people to deploy their own Vercel instance to lower the server load. Please check this guide on how this is done
bit0x43 commentedon May 20, 2022
rickstaa commentedon May 21, 2022
@cristian-rincon Please limit the discussion of the
Maximum retries exceedederror to #1471.rickstaa commentedon May 24, 2022
@duaneking, thanks for your message. The
hideparameter is working fine for me:Can you maybe share the syntax you are using and a screenshot of the error message you receive?
duaneking commentedon May 24, 2022
Any attempt to use the hide param multiple times results in this error:
In this case for the use of:
https://github-readme-stats.vercel.app/api/top-langs/?username=duaneking&hide=XML,CSS&theme=tokyonight&layout=compact&hide=rich%20text%20format&langs_count=8I see that this is fixable by simply using it only once, but the expectation I had was that options would be merged. You may want to update the docs or fix the issue to provide better compatibility.
28 remaining items
Harkirattttt commentedon Sep 24, 2023
Hello can you please help me fix this error?
jonesy-b-dev commentedon Oct 25, 2023
Getting this error, didnt see it anywhere here yet. Way to fix it?
qwerty541 commentedon Oct 26, 2023
Answered in #3429 (comment)
Chhunneng commentedon Nov 11, 2023
I got error on github
qwerty541 commentedon Nov 12, 2023
Hey, @Chhunneng! The problem is with GitHub's CDN. The only way to solve this is to create a GitHub action. You can track progress on this feature at #2179.
ci: filter anuraghazra#1772 from top-issues-dashboard
dapphari007 commentedon Dec 11, 2025
HosseinHeydari2004 commentedon Dec 26, 2025
rickstaa commentedon Dec 27, 2025
As we are no longer sponsored by Vercel (see this April 2024 message), we can no longer reliably operate the public instance at its current scale. The public endpoint remains available, but users should expect downtime.
To provide a stable alternative, we have released a new GitHub Action, which is now the recommended way to use the project. This approach is significantly more stable and allows for more accurate tracking as improvements are introduced.
Alternatively, you can deploy the project on your own instance, which has been the recommended setup for years and supports private data.
HosseinHeydari2004 commentedon Dec 28, 2025
@rickstaa
Thank you. 🙏
ci: filter anuraghazra#1772 from top-issues-dashboard
ci: filter anuraghazra#1772 from top-issues-dashboard
ci: filter anuraghazra#1772 from top-issues-dashboard