Twitter Response code 429. Error message: Response code 429 (Too Many Requests): target website might be blocking our access
See original GitHub issueRoutes
Error message: Response code 429 (Too Many Requests): target website might be blocking our access
Full routes
https://your_host.test/twitter/user/caddyserver
Related documentation
https://docs.rsshub.app/en/install/#docker-deployment
What is expected?
When I buit rsshub by docker-compose and run it at my own server, It worked about 2 months, but it can’t work today, and displayed the error mesage below:
Looks like something went wrong
Route requested: /twitter/user/caddyserver
Error message: Response code 429 (Too Many Requests): target website might be blocking our access, you can host your own RSSHub instance for a better usability.
Helpful Information to provide when opening issue:
Path: /twitter/user/caddyserver
Node version: v14.18.3
Why did this hapen? How to fix it?
What is actually happening?
When I buit rsshub by docker-compose and run it at my own server, It worked about 2 months, but it can’t work today, and displayed the error mesage below:
Looks like something went wrong
Route requested: /twitter/user/caddyserver
Error message: Response code 429 (Too Many Requests): target website might be blocking our access, you can host your own RSSHub instance for a better usability.
Helpful Information to provide when opening issue:
Path: /twitter/user/caddyserver
Node version: v14.18.3
Why did this hapen? How to fix it?
Deployment information
Self-hosted
Deployment information (for self-hosted)
OS: Ubuntu 21.04 x86_64 docker Version: 20.10.7 rsshub:https://hub.docker.com/r/diygod/rsshub
Additional info
When I buit rsshub by docker-compose and run it at my own server, It worked about 2 months, but it can't work today, and displayed the error mesage below:
Looks like something went wrong
Route requested: /twitter/user/caddyserver
Error message: Response code 429 (Too Many Requests): target website might be blocking our access, you can host your own RSSHub instance for a better usability.
Helpful Information to provide when opening issue:
Path: /twitter/user/caddyserver
Node version: v14.18.3
Why did this hapen? How to fix it?
### This is not a duplicated issue
- [X] I have searched [existing issues](https://github.com/DIYgod/RSSHub/issues) to ensure this bug has not already been reported
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:16 (2 by maintainers)
Top Results From Across the Web
How to Fix 429 Too Many Requests Error - Kinsta
The HTTP 429 error is returned when a user has sent too many requests within a short period of time. The 429 status...
Read more >How to Fix 429 Too Many Requests Error Code - Hostinger
HTTP 429 will block the suspicious IP address or user to protect the website. This way, it can prevent hackers from getting into...
Read more >How to Resolve WordPress Error 429 Too Many Requests
As the error message suggests, there are too many requests being made on your website. The problem is these requests can be from...
Read more >What an HTTP Error 429 Means & How to Fix It - HubSpot Blog
A 429 response is not technically an error — it's a response from a server, · For example, if a user is trying...
Read more >429 Error – Too Many Requests HTTP Code Explained
Whether you are a web developer or you are a regular internet user, you might have encountered a 429 error. It means that...
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 FreeTop 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
Top GitHub Comments
The reason why this error occurs is that the API method RSSHub uses is outdated, instead of “Too Many Requests” (though Twitter does return this status code). I have updated the route with the latest API method, please check #9471.
I find it maybe Twitter api has reached its limit;try to self-host one and use your twitter api token