[Down Time] Card throws 'maximum retries exceeded' error

[anuraghazra]

Hi everyone, I see that all personal access tokens are currently failing, thus you will see the "Maximum retries exceeded" error.

I'm looking into the issue to figure out what caused it.

Ideally, it should be fixed in an hour when the PATs get rest.

Details

Public instance information

Explanation

---

Hey everyone, sorry for the recent downtimes.

For the sake of transparency, we get a huge amount of requests per month (it's kind of mind boggling for a side project which I built just for fun). Here's the vercel dashboard statistics:

As you can see even with 73% of the responses being cached by vercel the amount of live requests are huge, and the bottleneck here is Personal Access Tokens

Each PAT have 5000 points, and based on the complexity of the GraphQL query & resource limitations set by GitHub, it's actually very very low considering that amount of requests.

To circumvent the issue, we currently have 7 PATs (thats 35k points) which sometimes get exhausted. Thanks to @rickstaa we are going to add few more probably bumping it up to 10 or 12, hopefully that could help alleviate the downtimes.

Note: That these downtimes are temporary, and only lasts for 1hour, since PATs regenerate after 1 hour

---

So whats the idea way?

https://github.com/anuraghazra/github-readme-stats/issues/1471#issuecomment-979306704 Deploy on your own vercel instance. WHY? It's easy to do, free & reliable.

• It reduces loads on our vercel instance.
• Your own PAT will give you more concrete stats including private stats
• It ensures that there won't be any downtime on your profile stats because you are the only one who is gonna hit your URL

Originally posted by @anuraghazra in https://github.com/anuraghazra/github-readme-stats/issues/2130#issuecomment-1270624232

[rickstaa]

@rickstaa @anuraghazra this appeared again

Thanks for letting us know. 👍

[Ddhruv-IOT]

It's down again

[rickstaa]

It's down again

That looks like a different error I will check.

[rickstaa]

Duplicate of #2380.

[showierdata9978]

How is this a dupe, this is #1471

[rickstaa]

How is this a dupe, this is #1471

Good point I accidentally closed the main issue. 😅

[FaraiMajor]

https://github-readme-stats-sigma-five.vercel.app

this fixed it for me. added sigma five

[RedHeadphone]

Deploying own Vercel works for few hours then again Maximum retries exceeded error is returned from the API, my guess is that github has updated some limitation on usage of PAT

[rickstaa]

retries

@RedHeadphone This is strange for your personal Vercel instance it should be more than enough. You can check how many requests you get in the Vercel interface. 🤔 Github gives users 5000 points, and I never had problems. Maybe you are still referring the public Vercel instance in your README.

[RedHeadphone]

@RedHeadphone This is strange for your personal Vercel instance it should be more than enough. You can check how many requests you get in the Vercel interface. 🤔 Github gives users 5000 points, and I never had problems. Maybe you are still referring the public Vercel instance in your README.

The Vercel Analytics doesn't seem to show number of requests. And no I am referring to my new vercel instance in README. One strange thing to be noted is that the a PAT which was giving Maximum retries exceeded in one of my vercel instance, using same PAT on other vercel instance seems to be working.

I have mentioned about same in this issue

[rickstaa]

@RedHeadphone This is strange for your personal Vercel instance it should be more than enough. You can check how many requests you get in the Vercel interface. 🤔 Github gives users 5000 points, and I never had problems. Maybe you are still referring the public Vercel instance in your README.

The Vercel Analytics doesn't seem to show number of requests. And no I am referring to my new vercel instance in README. One strange thing to be noted is that the a PAT which was giving Maximum retries exceeded in one of my vercel instance, using same PAT on other vercel instance seems to be working.

I have mentioned about same in this issue

You can find this information under the Usage tab in the general Vercel dashboard. I think the best option is to create a new PAD. 👍

[Bigyls]

Thanks for this solution, this is working for me (18 January 2023).

This section: https://github.com/anuraghazra/github-readme-stats#deploy-on-your-own-vercel-instance and this YouTube video tutorial: https://www.youtube.com/watch?v=n6d4KHSKqGk&feature=youtu.be&t=107 combined have resolved my problems

[rayennecandido]

@rickstaa @anuraghazraisso apareceu de novo https://www.youtube.com/watch?v=n6d4KHSKqGk&t=107s

[jamesthesnake]

Seems to have happened again.

[filipporomani]

@anuraghazra yup, it's happening again!

[jventura1738]

I think it's happening again

[Bigyls]

I think it's happening again

This is working for me (18 January 2023).

This section: https://github.com/anuraghazra/github-readme-stats#deploy-on-your-own-vercel-instance and this YouTube video tutorial: https://www.youtube.com/watch?v=n6d4KHSKqGk&feature=youtu.be&t=107 combined have resolved my problems

[jventura1738]

I think it's happening again

It's working now. 03/06/2023 12PM EST

[mehmetaligumusler]

Seems to have happened again.

[huanmeng-qwq]

Seems to have happened again.

[WeismannS]

Happened again today!

[ennioVisco]

Today as well:

[kms0219kms]

It is happening again, in 00:39 25/03/2023 in GMT+7.

[rickstaa]

It is happening again, in 00:39 25/03/2023 in GMT+7.

Thanks for letting us know. This is a known limitation of GitHub's GraphQL API (see https://github.com/anuraghazra/github-readme-stats/issues/1471). I have sent @anuraghazra a new PAT. Meanwhile, deploy your own Vercel instance or try the experimental GitHub action.

[showierdata9978]

You could swap PAT's every 30 minutes, if they are close to the limit, with a backup one for 30 minutes while the original one refreshes its use limit

[rickstaa]

You could swap PAT's every 30 minutes, if they are close to the limit, with a backup one for 30 minutes while the original one refreshes its use limit

Thanks for the suggestion. Unfortunately, we already use a similar mechanism in our code base (see https://github.com/anuraghazra/github-readme-stats/blob/32998295b7ef9742ea0168213807d7e8ec5c72a6/src/fetchers/stats-fetcher.js#L146C9-L170).

[jventura1738]

It's back again

[t3dium]

[rjscdev]

again

[mb6ockatf]

I have this error, too: I tried to self-host on Vercel following instructions in README.md, but got the following error:

Warning: Could not identify Next.js version, ensure it is defined as a project dependency.
--
19:22:17.839 | Error: No Next.js version could be detected in your project. Make sure `"next"` is installed in "dependencies" or "devDependencies"
19:22:18.429 | Deployment completed
19:22:18.001 | NEXT_NO_VERSION: No Next.js version could be detected in your project. Make sure `"next"` is installed in "dependencies" or "devDependencies"

May be it can be fixed with this

I dont't know what to do because i do not know javascript at all

Will Maximum retries exceeded error will go away soon, without any interference? I guess that's how apikeys usually work - there's certain number of requests available for period of time, then the counter is reset.

[davina708]

Can anyone help me with this issue?

[AbhayaShankar]

Something went wrong! file an issue at https://tiny.one/readme-stats Maximum retries exceeded Please add an env variable called PAT_1 with your github token in vercel Happened again

[AbhayaShankar]

[changeweb]

I have this error as well.

[NamitBhutani]

is there some down time going on? Because I hosted on my own on vercel, but I still get this issue of Maximum tries exceeded.

[showierdata9978]

is there some down time going on? Because I hosted on my own on vercel, but I still get this issue of Maximum tries exceeded.

how popular is your profile, if you get over 1000 visits per hour (?) it would do that

[NamitBhutani]

is there some down time going on? Because I hosted on my own on vercel, but I still get this issue of Maximum tries exceeded.

how popular is your profile, if you get over 1000 visits per hour (?) it would do that

No, not that famous ...

[RobThree]

Experiencing the same:

[KraXen72]

happening to me as well with PAT_1

[ev1025]

I have created a project on Vercel and deployed it, but the GitHub token keeps getting deleted, causing this error to occur repeatedly. What should I do?

[Himan10]

@ev1025 @KraXen72 hey guys, sorry for the tag but I just encountered this issue as well, just want to know how did you resolve it ? It says adding an environment variable PAT_1 with the GitHub token but I am not sure what its usage ?

[Vallek]

Same error here with PAT_1. I'm pretty sure i don't have a lot of viewers on my profile😅

[AshwanthramKL]

Still exists

[adriannylelis]

Hello! I resolved this just add a variable that increases the token's addition (sigma-five) in order to solve the problem like this: Before: <img height="120em" src="https://github-readme-stats.vercel.app/api/top-langs/?username=adriannylelis&layout=compact&langs_count=7&theme=dracula"/> After adding (sigma-five) : <img height="120em" src="https://github-readme-stats-sigma-five.vercel.app/api/top-langs/?username=adriannylelis&layout=compact&langs_count=7&theme=dracula"/>

And the problem was solved. But they say If to many people switch to @sigma-five's branch that instance will likely reach GitHub's rate limits too. This is discussed in https://github.com/anuraghazra/github-readme-stats/issues/2149

[jdevfullstack]

back then, there was the suggestion

https://github-readme-stats-git-masterrstaa-rickstaa.vercel.app

now, I'm restoring it to the original

https://github-readme-stats.vercel.app

and it's working again

[FahadBinHussain]

Please fix this ASAP

[qwerty541]

Please fix this ASAP

@FahadBinHussain Sometimes you can see these error because our public instance is being rate-limited by underlying GitHub API. You can deploy your own instance using your own GitHub API token in order to fix this or wait until the public instance is longer rate-limited.

[FahadBinHussain]

Please fix this ASAP

@FahadBinHussain Sometimes you can see these error because our public instance is being rate-limited by underlying GitHub API. You can deploy your own instance using your own GitHub API token in order to fix this or wait until the public instance is longer rate-limited.

Yeah, I have read that. However, I am currently facing certain circumstances which prevent me from deploying my own instance. That's why I am seeking assistance here to rectify the issues with the public one.

But, thank you. Since the issue has been resolved.

[qwerty541]

Please fix this ASAP

@FahadBinHussain Sometimes you can see these error because our public instance is being rate-limited by underlying GitHub API. You can deploy your own instance using your own GitHub API token in order to fix this or wait until the public instance is longer rate-limited.

Yeah, I have read that. However, I am currently facing certain circumstances which prevent me from deploying my own instance. That's why I am seeking assistance here to rectify the issues with the public one.

But, thank you. Since the issue has been resolved.

Unfortunately, there is not much we can do with the public instance. We are limited by the number of requests from the GitHub API. In theory, we can increase the already large number of API tokens that the public instance uses, but this will not solve the problem. Firstly, only the owner of the repository can do this, and secondly, the number of users is constantly growing and very soon we will again face the same problem. Currently the best way to avoid this issue is deploying own instance, if you have any idea how we can resolve it with public one feel free to share.

[Stk-79]

Please fix this ASAP

@FahadBinHussain Sometimes you can see these error because our public instance is being rate-limited by underlying GitHub API. You can deploy your own instance using your own GitHub API token in order to fix this or wait until the public instance is longer rate-limited.

Yeah, I have read that. However, I am currently facing certain circumstances which prevent me from deploying my own instance. That's why I am seeking assistance here to rectify the issues with the public one. But, thank you. Since the issue has been resolved.

Unfortunately, there is not much we can do with the public instance. We are limited by the number of requests from the GitHub API. In theory, we can increase the already large number of API tokens that the public instance uses, but this will not solve the problem. Firstly, only the owner of the repository can do this, and secondly, the number of users is constantly growing and very soon we will again face the same problem. Currently the best way to avoid this issue is deploying own instance, if you have any idea how we can resolve it with public one feel free to share.

Read everything available to fix this issues along with this two #2402 #2404 ..Hope it will be up again. Thanks