[BUG] Rate limit always hit
See original GitHub issueThe problem
As reported here, all requests to the jsonrpc
API are failing with
{
"jsonrpc": "2.0",
"error": { "code": 1042902, "message": "Too many requests." }
}
The problem is probably due to the same id being used in each request.
What is the current behavior?
Any request for translation fails.
What is the expected behavior?
Requests do not trigger rate limit IP blocks unless a specific client makes too many requests in a given time frame.
Environment
All versions.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:11 (2 by maintainers)
Top Results From Across the Web
Rate limit best practices
For org-wide rate limits, the three headers show the limit that is being enforced, when it resets, and how close you are to...
Read more >GitHub Error: Rate Limit Exceeded - Coder Diaries
When GitHub throws "Rate Limit Exceeded" error, the cause is exceeding the number of requests allowed per hour. Find out how to solve...
Read more >Discord API Rate Limiting: A Troubleshooting Guide
Generally, developers hit this rate limit when their community grows and their Discord bots need to process more requests.
Read more >Be prepared: 3 ways to handle rate limits | by Cathal Horan
While the reset option is one way to deal with rate limiting, you may want more granular control over your rate limit handling....
Read more >What does "rate limit exceeded" mean? (UPDATED)
If you use up your 100 API calls in the hour then you will see the “rate limit exceeded” message in TweetDeck and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I made a new package in which you can use your own API key. Let me know if this works for you @morsedl
Perhaps you should mentioned all this on the github page? 😃