Something went wrong! Maximum retries exceeded

[FleetAdmiralJakob]

Describe the bug

Everyone on my website cannot view the stats!

Expected behaviour

It just works

Screenshots / Live demo link

Additional context

My website: https://www.roessner.tech/about

[micash545]

same

[rickstaa]

@FleetAdmiralJakob and @micash545 This is a known issue when the public server is overloaded (See #1471). The error should go away when the server is not rate-limited anymore. The best solution is to deploy your own Vercel instance (see https://github.com/anuraghazra/github-readme-stats#deploy-on-your-own-vercel-instance).

[jaydeepkhatri]

Same issue👀👀
Thanks @rickstaa for the solution link 👍

[SAD0XER]

I am facing the same issue but mine is a little different, I have deployed the project on vercel with all perfect procedures, and the project also working fine. but after a month the token gets expires and there is an error like this 👇👇⬇️⬇️

so, on the vercel, I add another token & still showed the same error, I delete the project and redeploy it again with a new token however showing that same error.

What to do now? @rickstaa @anuraghazra Please help.

[rickstaa]

I am facing the same issue but mine is a little different, I have deployed the project on vercel with all perfect procedures, and the project also working fine. but after a month the token gets expires and there is an error like this 👇👇⬇️⬇️

so, on the vercel, I add another token & still showed the same error, I delete the project and redeploy it again with a new token however showing that same error.

What to do now? @rickstaa @anuraghazra Please help.

That's strange. The steps provided in the 🛠️ Step-by-step guide on setting up your own Vercel instance of https://github.com/anuraghazra/github-readme-stats#deploy-on-your-own-vercel-instance should work. When I follow them I don't run into problems. 🤔 Do you point the on your readme to your Vercel URL instead of the public one?

[SAD0XER]

Yes.
I am pointing on my own vercel deployment.
Not a public URL.

[rickstaa]

Yes. I am pointing on my own vercel deployment. Not a public URL.

It looks like your Vercel instance no longer exists. I think you are replying to it. Ensure you enable the repo permission when creating the PAT and add it under the PAT_1 env variable in Vercel.

[![sad0xer's GitHub Statistics](https://github-readme-statistics-sad0xer.vercel.app/api?username=sad0xer)](https://github.com/anuraghazra/github-readme-stats)```

[SAD0XER]

Yess!
Finally done😁.
I deploy it again with new domain. And it's working perfectly.

This is my 2nd try deployment.
During the 1st try deployment, I was changed default domain to old domain.

(My old domain: github-readme-statistics-sad0xer.vercel.app)

So, my 1st question is, it failing to show stats card because I was changed default domain to old domain?

And 2nd question is what happens if my PAT expires? Does it affects to stats cards Or this stats project deployment?

I have these questions because I am completely new OS contributor on Github 😅

[milovangudelj]

For me it's kind of working, but not really.

I forked the repo, deployed it to Vercel with my own domain name, added the required env variable and on GitHub it still shows the error message.

Visiting https://stats.milovangudelj.com/api?username=milovangudelj shows the stats, but on my profile's README it's bugged.

Is the request being cached and it still shows the old one from before the redeployment?
And if so, can I force a clean request in some way?

[rickstaa]

@milovangudelj You are right. It could be the cache. You can purge the Vercel cache by waiting 4 hours or appending a random string to an API call (i.e. https://stats.milovangudelj.com/api?username=milovangudelj&random=random). However, since you recently deployed your Vercel instance, that's not the problem. You can also purge the GitHub CDN cache as explained in #1471 (comment).

[milovangudelj]

Yeah, that could have solved it. But I was probably too impatient cause now it's displayed properly. It was just a matter of time 🕐

[kernaltrap8]

what the heck its broken again 😭

[rickstaa]

@JamesIsWack it's due to the popularity of the repository, I'm afraid. The graphQL API limits are being reached again. The best way to fix this is to deploy your Vercel instance (see https://github.com/anuraghazra/github-readme-stats#deploy-on-your-own-vercel-instance).

@anuraghazra Were you able to check whether the PATs I sent you were still valid using #2178? I can send you new PATs if you want.

[rickstaa]

It should be solved for now! Feel free to comment on #1471 if things strat to happen again.