[SCRAPEBOX-ISSUE] Google TEST result ALWAYS FAIL for proxy

hatworld3388

Registered Member
Joined
Mar 24, 2020
Messages
78
Reaction score
5
Hi All,

I purchased the private proxy from MPP and the seller double-checks all of the proxies I bought is fine with google, but i still have the issue to use them on my scrapebox,I am guessing there is one reason caused this because china side is ban to use google,so I used VPN to surf the internet.

Besides, anyone met this issue and how to fix it, now I could not harvest any of URLs.

scrapebox-fail.png
 
If you do a test and try to scrape Google for 1 simple keyword using those proxies, do you get results back? If not what is listed in the error file when you go to Help >> Show Error Log, and then view harvester.log and also proxymanager.log ?

You can XXX out your proxy IP, user, pass etc we dont need any personal info just the errors.
 
Use rotating proxies to avoid your IP getting banned by Google
 
Hi all just tried again for this part

whether i use the proxy or not,the error on the harvest.ini showing connetion time out

it means no any URLS got
 
I'm from China too and have the same issue.
When I Click Test Engine from Harvester Engine Configuration. The error message shows -1 connect time out.
The error log shows socket error #10054. Connection reset by peer.

Can you help me fix it?
@loopline
 
I'm from China too and have the same issue.
When I Click Test Engine from Harvester Engine Configuration. The error message shows -1 connect time out.
The error log shows socket error #10054. Connection reset by peer.

Can you help me fix it?
@loopline
Something is killing the connection. So this is most often security software, but can a router etc.

so add an exception for the entire scrapebox folder in all security software, and whitelist scrapebox in your router.

Also if your using public proxies it could just be the proxies.
 
Something is killing the connection. So this is most often security software, but can a router etc.

so add an exception for the entire scrapebox folder in all security software, and whitelist scrapebox in your router.

Also if your using public proxies it could just be the proxies.
thanks for your reply.
I already removed all security software. and I use private proxies from MPP.
The problem still exists.
 
thanks for your reply.
I already removed all security software. and I use private proxies from MPP.
The problem still exists.
are you on windows 10? Because if you removed the security software, then windows defender will take over - and you have to hack the registry to get windows defender to actually stop. Not saying you should hack the registry just pointing it out. So adding exceptions is the way to go vs disabling windows defender, in general.

that said, it could be a router. You can try a mobile dongle, or friends network or try connecting direct and bypass the router, if thats an option.

Another test is turn off the proxies and try it does it still happen?
 
Hi All,

I purchased the private proxy from MPP and the seller double-checks all of the proxies I bought is fine with google, but i still have the issue to use them on my scrapebox,I am guessing there is one reason caused this because china side is ban to use google,so I used VPN to surf the internet.

Besides, anyone met this issue and how to fix it, now I could not harvest any of URLs.

View attachment 139645
I have same problem for this . Did you find the way to solve this??
 
Your in china using a vpn or your ips are just blocked by google?
Yes,im in china too and face same issue with them . I did try serval proxies and still not able to use scrapebox properly. And I try to test the proxies on the web browser . It cannot show the google engine.
 
1645195066187.png
I got zero result on google harvest when i use proxies .And bing engine seems harvest properly.
 
You have a ton of errors, go to help >> show error log >> harvester - what are the errors?
Hello,Loopline.Long time no see.I used different proxy list and it didnt show erros on harvester now. But there was a lot error on the proxy log.
Please check 20220524222331.png
 
Get a VPS and try again, if you think China location to be the issue. If that does not solve the issue, try changing the proxy provider. Either should fix the issue.
 
Hello,Loopline.Long time no see.I used different proxy list and it didnt show erros on harvester now. But there was a lot error on the proxy log.
Please check View attachment 211866
Hey mate, are those on private/shared private or what kind of proxies?

500 is a network type error, that could be just overloaded proxies or whatever. 403 is forbidden thats odd. Did all the proxies test out as passed?

302 is likely on google, thats an ip block error, that usually goes away with 48 hours of no use on google.

0 is a socket error, it kind of means scrapebox knows there was an error but windows did not tell scrapebox specifically an error code. So this could be security software or the router, so whitelist scrapebox in all that.

Unless these are public proxies then all these kinds of errors are normal.
 
Get a VPS and try again, if you think China location to be the issue. If that does not solve the issue, try changing the proxy provider. Either should fix the issue.
I ask my friend who outside china to test the scrapebox, it seems work properly with some cheap proxies.And I also try some expensive proxies which will cost me at least 100 USD to do the test in China . It can work too but not very smooth .So I believe there are two reason for the errors:1.location 2.proxies quality
 
Hey mate, are those on private/shared private or what kind of proxies?

500 is a network type error, that could be just overloaded proxies or whatever. 403 is forbidden thats odd. Did all the proxies test out as passed?

302 is likely on google, thats an ip block error, that usually goes away with 48 hours of no use on google.

0 is a socket error, it kind of means scrapebox knows there was an error but windows did not tell scrapebox specifically an error code. So this could be security software or the router, so whitelist scrapebox in all that.

Unless these are public proxies then all these kinds of errors are normal.
I believe those are private proxies. And they passed the anonymous test but not google test .
 

Attachments

  • 0220525091656.png
    0220525091656.png
    96.5 KB · Views: 14
Back
Top