github-readme-stats
github-readme-stats copied to clipboard
anuraghazra
Maximum retries exceeded. (deployed to my own Vercel)
Describe the bug
As mentioned above, I met the same problem even if I deploy it to my own Vercel.
It asked me to add my PAT_1 env variable, but I had added one with access to my repos.
You can see my repo here.
It appears like the following.
Sincere thanks.
Expected behaviour
No response
Screenshots / Live demo link
Additional context
Moreover, after configuring my personal domain, I will be very glad to provided it for others to use! :)
It's working right? It usually takes a few minutes for everything to get set up, so maybe that's why it didn't work at first.
It's working right? It usually takes a few minutes for everything to get set up, so maybe that's why it didn't work at first.
alright, I'll check it later as Vercel told me it was ready before...
It's working right? It usually takes a few minutes for everything to get set up, so maybe that's why it didn't work at first.
I'm grateful that it finally worked perfectly now, and I'm willing to provide my domain for others:
From @CLCK0622
https://readme-stats.clckblog.space/
My readme stats are currently having this issue. How exactly did you fix it?
My readme stats are currently having this issue. How exactly did you fix it?
Eh, I just waited for about an hour and it worked well. I'm also not that clear why this is so weird.
@anuraghazra Excuse me, it seems that some people also have the same issue that the component will work well in about half an hour after deploying. I don't really know if this is by design but I think it would be better if you can add this to your tutorial for deployment on Vercel. (this really worried me before)
I also have the same issue with my own Vercel. It's been like this the entire day and still not working. I even tried to redeploy the project but did not have any luck so far.
Updates: It came back suddenly.
I also have the same issue with my own Vercel. It's been like this the entire day and still not working. I even tried to redeploy the project but did not have any luck so far.
Updates: It came back suddenly.
This kind of problem do happen before, and it's hard to say when it will return normal. Anyway, happy to hear that good message!
In my case
seems like &count_private=true problem
remove it and everything is working again
i try to revert it but the same issue is back. /sad
so i can only remove it
so having the same problem. Trying to understand if the issue self-resolved or if everyone is saying they updated their Vercel and then it resolved after an amount of time passed???
@dAtiuyy, this issue is for those who have deployed to their own Vercel instance.
Since you're using Anurag's instance, please see #2415.
so having the same problem. Trying to understand if the issue self-resolved or if everyone is saying they updated their Vercel and then it resolved after an amount of time passed???
I suppose it's caused by some strange problems of the project. However, it seems really weird that it will be solved after a moment. Maybe due to the local cache? idk why
In my case seems like
&count_private=trueproblem remove it and everything is working again i try to revert it but the same issue is back. /sad so i can only remove it
maybe you can try to add it back now? I didn't do anything but waited and it recovered automatically.
In my case seems like
&count_private=trueproblem remove it and everything is working again i try to revert it but the same issue is back. /sad so i can only remove itmaybe you can try to add it back now? I didn't do anything but waited and it recovered automatically.
yeah，it's working now，maybe the local cache causing this issue
@dAtiuyy, this issue is for those who have deployed to their own Vercel instance.
Since you're using Anurag's instance, please see #2415.
thanks, I am facing the same issue! deploying own instance might solve it!
It should be fixed for now. If you run into problems, please comment below. 👍
It should be fixed for now. If you run into problems, please comment below. 👍
y exactly, I just wanted to let more people see this issue. now that there's new solution, it no longer matters. thx anyway