Maximum retries exceeded" error.

[MustafaAliCetinkaya]

Describe the bug

Personal access tokens are currently failing, I see the "Maximum retries exceeded" error.

Expected behaviour

No response

Screenshots / Live demo link

No response

Additional context

No response

[jimbolimbo3]

Me too, unfortunately

[DalpatRathore]

Some server PAT limits or depletion causes the known issue, I am facing it too. The best solution, for now, is to deploy on your own instance (see #1471).

[itsmanibharathi]

4
I too have same issue

[anuraghazra]

Hi it should resolve within an hour, our PATs are invalidated.

But a better option for would be to deploy github-readme-stats on your own Vercel instance.
https://github.com/anuraghazra/github-readme-stats#deploy-on-your-own-vercel-instance

Pros:

• No downtime
• Private commits will also be counted

[IamManchanda]

Hi @anuraghazra ... I have self deployed it (changed maxDuration to 10 too as I am on a Hobby Plan)
=> https://github-readme-stats-ruddy-six.vercel.app

But still getting Maximum retries exceeded error

[fatimakay]

Facing the same issue

[nathanredblur]

Me too

[San3-Cod3]

Still have this issue, and attempting to deploy my own is asking for a phone number for verification which I will not give under any circumstances; don't even have a number attached to my GitHub account either way as far as I know. Very unnecessary asking for this, in my opinion.

[KatarzynaChmielecka]

and also I'm bug buddy ;)

[ruchernchong]

Hi @anuraghazra ... I have self deployed it (changed maxDuration to 10 too as I am on a Hobby Plan) => https://github-readme-stats-ruddy-six.vercel.app

But still getting Maximum retries exceeded error

2nd this. I am also facing the same problem with my own hosting.

[Scemist]

Hi @anuraghazra ... I have self deployed it (changed maxDuration to 10 too as I am on a Hobby Plan) => https://github-readme-stats-ruddy-six.vercel.app

But still getting Maximum retries exceeded error

Same here, I deployed my own hosting in vercel with the correct PAT_1 env variable with correct token permissions. The problem doesn't look in the host.

[ajfm88]

The "most used languages" one is back and working as normal, but the github stats one

https://github-readme-stats.vercel.app/api?username=*yourusernamehere*&show_icons=true&theme=transparent

is still not working.

[KatarzynaChmielecka]

The "most used languages" one is back and working as normal, but the github stats one

https://github-readme-stats.vercel.app/api?username=*yourusernamehere*&show_icons=true&theme=transparent

is still not working.

For me both not working.

[SyafaHadyan]

[SyafaHadyan]

The "most used languages" one is back and working as normal, but the github stats one

https://github-readme-stats.vercel.app/api?username=*yourusernamehere*&show_icons=true&theme=transparent

is still not working.

Both not working

[SyafaHadyan]

Working on GitHub Mobile

[anuraghazra]

Same here, I deployed my own hosting in vercel with the correct PAT_1 env variable with correct token permissions. The problem doesn't look in the host.

@Scemist can you double check on your vercel dashboard that the PAT_1 is marked as "production"?

Here's the docs for adding env:
https://vercel.com/docs/concepts/projects/environment-variables

If it still doesn't work, try deploying it again & bust the cache while hitting the URL by adding a random param like api/?ver=2

[hello-sabira]

Same problem here too :(

[KatarzynaChmielecka]

For me work now, but this stats is falsy. It still counts last year :(

[claudiotancredi]

Hi it should resolve within an hour, our PATs are invalidated.

But a better option for would be to deploy github-readme-stats on your own Vercel instance. https://github.com/anuraghazra/github-readme-stats#deploy-on-your-own-vercel-instance

Pros:

• No downtime
• Private commits will also be counted

I solved it by deploying my own Vercel instance. In addition to what is already reported here, there are other few things that I did at the end of the process. You should:

1. Go on the Deployment tab of the Vercel project. Then, under Deployment Status, expand Assigning Domain and copy the Custom Domain;
2. Go to your profile README.md and be sure to change the url that you use so that it starts with your Custom Domain that you copied in step 1. For me, instead of having https://github-readme-stats.vercel.app it was https://github-readme-stats-ruby-one.vercel.app .

As you can see on my profile README, it appears to be working properly.

[ruchernchong]

Hi it should resolve within an hour, our PATs are invalidated.
But a better option for would be to deploy github-readme-stats on your own Vercel instance. https://github.com/anuraghazra/github-readme-stats#deploy-on-your-own-vercel-instance
Pros:

• No downtime
• Private commits will also be counted

I solved it by deploying my own Vercel instance. In addition to what is already reported here, there are other few things that I did at the end of the process. You should:

1. Go on the Deployment tab of the Vercel project. Then, under Deployment Status, expand Assigning Domain and copy the Custom Domain;
2. Go to your profile README.md and be sure to change the url that you use so that it starts with your Custom Domain that you copied in step 1. For me, instead of having https://github-readme-stats.vercel.app it was https://github-readme-stats-ruby-one.vercel.app .

As you can see on my profile README, it appears to be working properly.

This is working for me.

[ghost]

Is there any way this can be fixed without deploying yourself on Vercel?

Will this issue keep happening, or is it a bug that can be fixed by the maintainers?

[SyafaHadyan]

Is there any way this can be fixed without deploying yourself on Vercel?

Will this issue keep happening, or is it a bug that can be fixed by the maintainers?

I deployed on Vercel for free, fork the repo, change the max duration in vercel.json from 30 to 10 and make PAT(Classic).

Or you can see the instructions Here

[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

[ghost]

@RedHeadphone - So you have to continuously redeploy after the PAT limit is reached?

[RedHeadphone]

that did make the API work for first time, but now even after updating PAT with new one, still old error is returned Maximum retries exceeded

[RedHeadphone]

I created a new project in vercel using same PAT which was giving me Maximum retries exceeded, the new vercel project seems to be working. I am not sure but I think this issue might lie with vercel.

[mojixcoder]

I'm having this problem too.

[rickstaa]

Duplicate of ##1471.

[ukaemma2]

I RESOLVED IT WITH NEWER VERSION >>>

[mk3709]

Maximum retries exceeded Please add an env variable called PAT_1 with your github token in vercel what should be done