Scrapebox proxies not working

Roi07

Registered Member
Joined
Apr 29, 2015
Messages
64
Reaction score
3
I got a pack of 10 dedicated private proxies located in the US for 20$ from a well known company here in BHW.
Anyway, after I loaded them into Scrapebox it scraped once from google and just stopped working.
If I test them it says theyr'e all google passed and annonymous, but when I try to scrape it just won't do anything (scrapes only from Bing).
I limited the amount of connections to 5 and still nothing.
Tried talking to the company, they exchanged the proxy to another list - again, worked for one scraping of 5000 url's and that's it - theyr'e dead.

Where's the problem?
 
Last edited:
It's my understanding the private proxies burn out very fast? I have more luck just using Red box GSA proxies. Just search "red box proxies" in the forums.

I got 40 google passed proxies off him the other night left it for 12 hours and scrapped 200k URLs.
 
It's my understanding the private proxies burn out very fast? I have more luck just using Red box GSA proxies. Just search "red box proxies" in the forums.

I got 40 google passed proxies off him the other night left it for 12 hours and scrapped 200k URLs.
You mean red-proxy?
For scrapebox I need private dedictaed proxies or shared ones? because theyr'e offering 10K list for 30$, or 10 private ip's for 22$.
 
I tried a new list from the same company once again, this time I even went with safer settings - only 3 connections.
I was able to scrape once from google and then they died... will it happen with every company or some of them provide better products?

*EDIT: I recived an email from the company saying that I got a refund. He said that he allocated the last list of proxies I was given from new servers and therefore the problem is on my side since I don't know how to operate the Scrapebox.

Well fine, I don't rule it out, but where does the problem stand?
I set my harvester on 3-5 connections with 30 seconds timeout.
 
Last edited:
i have not used it for years but i think there was a rule about 25% of the proxies set as connections.

mean 20 proxies - 4 connections .... your timeout seem ok
 
You're using 10 proxies and "limited the amount of connections to 5 and still nothing". Even limiting the amount of connections to 5 is way to much. Especially if you're using advanced operator footprints like inurl: site: etc

You're going to keep burning your proxies with Google if you don't start lowering your proxies connection ratio.

I usually get 100 semi dedicated proxies and scrape at a 1:10 ratio max with Google. Or in other words 10 connections
 
i have not used it for years but i think there was a rule about 25% of the proxies set as connections.

mean 20 proxies - 4 connections .... your timeout seem ok

You're using 10 proxies and "limited the amount of connections to 5 and still nothing". Even limiting the amount of connections to 5 is way to much. Especially if you're using advanced operator footprints like inurl: site: etc

You're going to keep burning your proxies with Google if you don't start lowering your proxies connection ratio.

I usually get 100 semi dedicated proxies and scrape at a 1:10 ratio max with Google. Or in other words 10 connections

I tried again with a new list, this time only 1 connection at a time with a timeout of 60 seconds. I don't think it could be safer than that.
Anyway, I get the same problem. scrapes for 4K links and dies. what should I do?
I tried checking each proxy manually by placing it as proxy in Firefox. google works, IP changed, but scrapebox does nothing.
 
Last edited:
I tried again with a new list, this time only 1 connection at a time with a timeout of 60 seconds. I don't think it could be safer than that.
Anyway, I get the same problem. scrapes for 4K links and dies. what should I do?
I tried checking each proxy manually by placing it as proxy in Firefox. google works, IP changed, but scrapebox does nothing.

If you turn off javascript in firefox that could be a useful test, but with javascript on its completely different, because Scrapebox uses sockets, which don't support javascript and so it works differently.

If you go to settings >> and uncheck the use custom harvester and uncheck the use multi threaded harvester, and then harvest, do you see a lot of ip blocked errors?
 
Back
Top