pytrends
pytrends copied to clipboard
GeneralMills
Script I made was working before, now it shows Read Timeout error
Hi, I have been using a script to get Google Trends data but today it suddenly showed this error HTTPSConnectionPool(host='trends.google.com', port=443): Read timed out. (read timeout=5)
Is it a problem in my code or somewhere else?
same here, likely google modified their api proxy policy, I'm going to see if sleeping longer can avoid this issue.
I'm having the exact same problem. First the time out error now the 429 error.
Also have this same issue, sleeping longer has not done much. Has anyone had success in fixing this?
Same issue here. Are you all using AWS or something? I've run it once on my local PC and it ran smoothly but on aws I'm getting 429.
Same issue here on my pc and on AWS. AWS instance has been blocked for over 10 days. 2 other computers I tried started right from the get go with timeouts.
I am getting the same error running this from my pizero from my home.
EDIT: I disabled my Pi-Hole software running on another device and it seemed to work for one trend pull. I went to the Google Trends page and any trend I was searching was not loading. I disabled the Pi-Hole software and searches started working. Rebooted my pizero and ran my script to pull 70 trends and it competed the first and spat out the error again on the second pull.
Same problem here, it has been three days since I am getting error 429 on my EC2 instance. A greater sleep or timeout has not resolved the problem.
I got the same problem and narrowed it down to the related_queries() function. Other functions seem to be working well.
Hope to see a solution for it anytime soon!
I got the same problem and narrowed it down to the
related_queries()function. Other functions seem to be working well. Hope to see a solution for it anytime soon!
Nope. All others same issue.
Same issue here. Are you all using AWS or something? I've run it once on my local PC and it ran smoothly but on aws I'm getting 429.
@iJohnMaged I'm just curious but did you made too many requests before getting 429 on your AWS instance?
Same issue here. Are you all using AWS or something? I've run it once on my local PC and it ran smoothly but on aws I'm getting 429.
@iJohnMaged I'm just curious but did you made too many requests before getting 429 on your AWS instance?
Nope. I started getting it on my 3rd request, locally I can get away with 2500 requests before getting any 429s and sleeping for 60s solves it.
Reporting similar issue from AWS - multiple regions tested in EU and US with new public IPs, all to the same result: only 1-3 requests allowed per period, the rest end up with a 429 - local seems to be just like before. It would appear google has decided to severely restrict AWS IP ranges from using the service.
Do you think it'll still be throttled to 3 requests/min if you move to GCP?
Do you think it'll still be throttled to 3 requests/min if you move to GCP?
Working fine on GCP :)
@iJohnMaged How many request can be send from GCP?
Could be that this limit is only applied to AWS??? Is this 2-3 request per minute visible somewhere???? or is just known now by trrial and error (reported experience)?
I thought this was a different error than the 429 reported time a go https://github.com/GeneralMills/pytrends/issues/435
Also How many time do I need to sleep between request? 1 minute or 1 hour? or it varies?
@iJohnMaged How many request can be send from GCP?
Could be that this limit is only applied to AWS??? Is this 2-3 request per minute visible somewhere???? or is just known now by trrial and error (reported experience)?
I thought this was a different error than the 429 reported time a go #435
Also How many time do I need to sleep between request? 1 minute or 1 hour? or it varies?
I think I'm getting about 2.5~3K on GCP almost with 5 seconds + random delay.
On AWS it's completely blocked, from the first request, at least for me.
Having similar issues - running on AWS and no luck but works sporadically on local.
Anyone on aws having any luck?
Yes I am also facing the same issue. When run locally, it works fine. But on AWS server I keep getting the 429 error. So is this problem due to the AWS? Does anyone face this issue on GCP?
I'm hitting 429s on GCP.....
It's running (20 + random) seconds between requests and get's blocked within 10ish hours....
EDIT:
I got with working by dropping the parameters when setting up TrendReq and increasing my delay to 60 seconds:
Change this -
pytrends = TrendReq(hl='en-US', tz=360)
To this -
pytrends = TrendReq()
AWS was still blocked from the first request.
