The ">" at the end is a known bug on how the logs are displayed. The connection refused error actually means that the target domain has the Scrapy Cloud IP(s) blocked, so the solution would be to use Crawlera as a proxy.
1 Comment
nestor
said
over 6 years ago
Answer
Hi,
The ">" at the end is a known bug on how the logs are displayed. The connection refused error actually means that the target domain has the Scrapy Cloud IP(s) blocked, so the solution would be to use Crawlera as a proxy.
Jenny Palarca
Hi,
I am encountering this issue when running the spider:
[scrapy.core.scraper] Error downloading <GET http://www.yalwa.com>: Connection was refused by other side: 111: Connection refused.
As you notice, the string ">" is identified as part of the starting url. How should I fix this?
My spider works when I run on my local machine so I am confused why it is not working in scrapinghub.
Can you help me please?
Thank you.
Hi,
The ">" at the end is a known bug on how the logs are displayed. The connection refused error actually means that the target domain has the Scrapy Cloud IP(s) blocked, so the solution would be to use Crawlera as a proxy.
nestor
Hi,
The ">" at the end is a known bug on how the logs are displayed. The connection refused error actually means that the target domain has the Scrapy Cloud IP(s) blocked, so the solution would be to use Crawlera as a proxy.
-
Unable to select Scrapy project in GitHub
-
ScrapyCloud can't call spider?
-
Unhandled error in Deferred
-
Item API - Filtering
-
newbie to web scraping but need data from zillow
-
ValueError: Invalid control character
-
Cancelling account
-
Best Practices
-
Beautifulsoup with ScrapingHub
-
Delete a project in ScrapingHub
See all 446 topics