[go: up one dir, main page]
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

429 Too Many Requests You have sent too many requests in a given amount of time. #276

Open
dannysale opened this issue Sep 27, 2024 · 1 comment
Open

429 Too Many Requests You have sent too many requests in a given amount of time. #276

dannysale opened this issue Sep 27, 2024 · 1 comment
Labels
problem question

Comments

@dannysale
Copy link

So I have hosting with Namecheap, and do not have problems running other blog platforms, or anything else. However, when I install Chyrp Lite, and begin enabling modules, after 3 or so cases of doing so, I get:

429 Too Many Requests
You have sent too many requests in a given amount of time.

I asked Namecheap about this, and they say it's the software making the requests. Would you happen to know if this is accurate?

I've had Chyp Lite installed on other hosts in the past, and did not experience this. So, how might my current host be interacting with the software so that this could take place? Is there something I should look for in able to resolve the matter?

Your help is appreciated.
@xenocrat
Copy link
Owner
xenocrat commented Sep 27, 2024 •
edited
Loading

Hello there,

Any hosting provider can decide their own trigger for a 429 response, so there is no universal right answer to avoiding this issue. It could be that Namecheap have their hosting set on a 429 hair trigger, which you just need to be aware of and work around. Some troubleshooting thoughts:

  1. Did Namecheap give you any indication what they consider the maximum acceptable number of requests per second/minute/hour? What are the thresholds that cause their rate limiting to trigger? They may not be willing to share this with you, but it’s worth asking.
  2. What modules did you enable? Have you noticed a combination of modules that causes the issue? Any self-developed modules?
  3. 429 responses should include a Retry-After header which tells you how long you must wait before the 429 resets and requests return to being served as normal. Again, this can be any length of time the provider chooses. Good to know for troubleshooting purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
problem question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xenocrat @dannysale