ScrapeBox Proxy Error?

[Alra]

Hi, all -

I just started using SB last week. I recently put on a VPS for long-term scraping.

I went out and got the 10 free Webshare proxies to test out. Harvesting URLs from keywords yields zero results, 10 errors.

Webshare says that those public proxies might have been flagged, let's upgrade to a paid plan, which I did.

Same issue.

Upon testing scraping, I get:

HTTP: 0 , SOCKET: Connection reset by peer

Upon testing proxies, most of them receive a Google 302 error.

I've looked around with little in the way of a solution.

Any ideas?

 

[Sweetfunny]

Please go to Settings >> Harvester Engines Configuration >> Select Google, then click "Test Engine" Do you get search results returned here? Then click the Next button do you also get results for the next page.

If you do then the reason for your issue is your proxies are not working for Google, because the engine test feature is identical to the harvester except it does not use proxies. You can then add a proxy on this Window where it says "Proxy to test engine" and repeat the test to see if it's the proxy not working or something else.

 

[Alra]

Please go to Settings >> Harvester Engines Configuration >> Select Google, then click "Test Engine" Do you get search results returned here? Then click the Next button do you also get results for the next page.

If you do then the reason for your issue is your proxies are not working for Google, because the engine test feature is identical to the harvester except it does not use proxies. You can then add a proxy on this Window where it says "Proxy to test engine" and repeat the test to see if it's the proxy not working or something else.

Yep, still getting the same error using the proxies.

 

[ATuringtest]

Turn off proxies turn off all search engines except Bing and scrape a common keyword.
Then if that works, turn proxies on and scrape with bing
If that works it means your proxies are not passing the the Google public test.

 

[Alra]

Turn off proxies turn off all search engines except Bing and scrape a common keyword.
Then if that works, turn proxies on and scrape with bing
If that works it means your proxies are not passing the the Google public test.

That's what I've been doing. No luck.

 

[ATuringtest]

Here's my suggestion

Go to @deki33 's BST

Buy the $10 trial, use that, if it doesn't work nothing lost, they will refund the cost if you contact them with 2 hours.
I use them for scraping on a legit licensed copy of SB. Never had one problem as long as you carefully read the threads rules.
If that fails then find another VPS.

 

[710fla]

If you're scraping Google you need rotating proxies or else they will be banned by Google for a day

 

[Alra]

If you're scraping Google you need rotating proxies or else they will be banned by Google for a day

Nope, I'm scraping Bing exclusively.

 

[Alra]

Here's my suggestion

Go to @deki33 's https://www.blackhatworld.com/seo/storm-proxies-premium-dedicated-proxies-sneaker-tickets-instagram-facebook-twitter-pinterest.894566/
Buy the $10 trial, use that, if it doesn't work nothing lost, they will refund the cost if you contact them with 2 hours.
I use them for scraping on a legit licensed copy of SB. Never had one problem as long as you carefully read the threads rules.
If that fails then find another VPS.

I've tried this on a different machine, and I've tried public proxies, but I guess it could be the VPS...

 

[ATuringtest]

Nope, I'm scraping Bing exclusively.

Can you ping google/bing from your VPS or open a web browser and see if it allows you out ?

 

[Alra]

Can you ping google/bing from your VPS or open a web browser and see if it allows you out ?

Yep - and it's scraping Bing just fine using a VPN. The proxy providers can't find a problem on their end.

Also, I guess I forgot to put this in the original post, but I'm using Win Server 2016 and scraping Bing exclusively.

 

[Takenotes]

Proxy is the reason. I have post my results in some other threads.