Recent Scrapebox Proxy Issue, everyone should note

and that response is plausible
remember if u share a source of proxies
with thousands of people. chances are half the list
u just tested is dead because 10k others did the same
the key is a source not many use
 
Well I guess I'll be finding out if SB is going to work for me here tonite- maybe it will take me a while before I get banned lol. :rolleyes: I opened ticket with the powers that be at SB and got this reply today:

No there is nothing wrong with the proxy checking its highly accurate. The problem is that hundreds of people could be simultaneously using those same proxies. In fact if 100 people were all just running them thru the proxy checker it could ban them from google, because in order to accurately proxy check them, it has to pull a google search results page, and the sheer volume of users proxy checking them can ban IPs. Not to mention if you keep proxy checking them over and over again and everyone else does too then that could do it.

However there is nothing wrong at all with the proxy checker.

Regards, ScrapeBox and ScrapeJet Support.


It's too bad they gave you that answer because it is not accurate. If a proxy I use through firefox and other proxy testers works fine to connect to google then the proxy is not blocked. The fact that it is showing as blocked by SB means their software is broken. Not only that, but I even tried using my private proxies in SB and they are showing up as blocked, but again work fine in FF and other proxy tools.

Obviously the answer they gave you is definitely wrong if I am the only one using my private proxies.

It's kinda crazy that they would be acting this way. Their customer support went from being great to being terrible for me. I've already been over this with them and they are now ignoring me because I proved them wrong and they don't want to fix their software, apparently. Definitely a big disappointment.

Good thing I'm a programmer and can just write my own tools :D
 
It's too bad they gave you that answer because it is not accurate. If a proxy I use through firefox and other proxy testers works fine to connect to google then the proxy is not blocked. The fact that it is showing as blocked by SB means their software is broken. Not only that, but I even tried using my private proxies in SB and they are showing up as blocked, but again work fine in FF and other proxy tools.

Obviously the answer they gave you is definitely wrong if I am the only one using my private proxies.

It's kinda crazy that they would be acting this way. Their customer support went from being great to being terrible for me. I've already been over this with them and they are now ignoring me because I proved them wrong and they don't want to fix their software, apparently. Definitely a big disappointment.

Good thing I'm a programmer and can just write my own tools :D

1. Get a proxy sbox tell you is ip blocked
2. Delete ALL your firefox cookies related to google
3. Turn javascript of in firefox, maybe using NoScript addon for ForeFox.
4. Set the proxy in firefox
5. Do a search.

2 things can happen:
1) The proxy is blocked
2) Google was able to set a new cookie (because you had javascript enabled) and the proxy will work again

There might be also a ScrapeBox update coming, which improves the proxy tester related to google.
 
Last edited:
1. Get a proxy sbox tell you is ip blocked
2. Delete ALL your firefox cookies related to google
3. Turn javascript of in firefox, maybe using NoScript addon for ForeFox.
4. Set the proxy in firefox
5. Do a search.

2 things can happen:
1) The proxy is blocked
2) Google was able to set a new cookie (because you had javascript enabled) and the proxy will work again

There might be also a ScrapeBox update coming, which improves the proxt tester related to google.

I have FF set up in complete stealth mode. No images, no javascript, no cookies. And the proxies work fine.

Trust me, I've tried everything. I was a hardcore scrapebox user for some time, that is why this issue is so disappointing to me.
 
look at it this way. scrapebox is worth a few hundred $ at least
so consider this. would u have payed 2-300$ for s/box with a perfect
working proxy tester. or 59$ knowing the proxy tester is a bit glitchy
but it still works to some degree. i no which ide have.

and im sorry but if i can find 7-800google passed proxies a day even
with a glitchy proxy tester so can you.
hell all i use is 30% public scraped proxies - 70% public port scanned
proxies all done with free tools.. some people dont try hard enough
the words on a plate spring to mind.

you all no the issues with the tester, so quit whining and get to
work doing some productive research on how to find public proxies
with port scanning, less whining more work. theres hundreds of proxies
available for port scanners to find...
 
Last edited:
you all no the issues with the tester, so quit whining and get to
work doing some productive research on how to find public proxies
with port scanning, less whining more work. theres hundreds of proxies
available for port scanners to find...

I appreciate the high standard you are trying to set, but I think you are out of line. This thread is about trying to solve the problem with SB, not pretending it doesn't exist. It's about dealing with a broken g00gle scraper.

Also, how do you know people aren't port scanning proxies? You must think you are psychic or something..
 
Last edited:
2 things I have to mention:
1) Google changed things
2) A little bug related to proxies redirecting to non-English speaking countries

There will be an update coming soon, stay tuned. We are currently testing the new code.
 
When harvesting proxies i get the malware proxy warning now dont know what is going on. just did the last up date and still nothing..Hope it gets fix soon...just did a harvest of 323 proxies and only 1 that passed not good numbers
 
Last edited:
i tested 5k proxies today 2k scraped 3k port scanned
700 passed google - 1 tip your proxy sources are bad

ps
Tensegrity

if people are port scanning and still cant get any
working this might be an obvious answer with no
dis respect then > means the ip ranges are bad <
try my philosophy > must try harder
 
Last edited:
i tested 5k proxies today 2k scraped 3k port scanned
700 passed google - 1 tip your proxy sources are bad

ps
Tensegrity

if people are port scanning and still cant get any
working this might be an obvious answer with no
dis respect then > means the ip ranges are bad <
try my philosophy > must try harder

You seriously have some sort of brain malfunction.

For the last effin' time, MY PROXIES ARE NOT BAD. They work perfectly fine. They just don't work in SB. Do you understand this concept? Cuz it seems to be completely lost on you.

I bet you ate paint chips as a child.
 
so all your proxys fail scrapebox
mine do not thats a concept i can follow
 
Great.
It still doesn't change the fact that there is a problem with SB.

By posting here claiming your proxies work fine over and over and going on and on about how you port-scan your proxies blah blah blah, and ads for your proxy service in your avatar and sig, it seems to me that the only reason you have to post in this thread is to advertise your service. I think people got the point, so you can just stop posting about things that are irrelevant to the issue now.

If you want to offer a solution along with proof of how your solution solves the SB problem so that we can use it for scraping G00gle again (one that doesn't involve buying proxies from you or port scanning since neither of those fixes SB to work with our proxies), then I think people would be interested in hearing about it.
 
no if u bother to read anything im saying which your not
lets face it no is disputing there isnt a problem with the
proxy tester. if you bother to read what im saying is rather
simple, yes its flawed, but by scraping less used sources of
public proxies > and port scanning your own < you will get by.
can you follow this concept
 
I give up -- it's like talking to a wall.

Anyway, for anyone who's looking for answers:

I've been seeing better results today. Still plenty of proxies are showing up as blocked in SB but not in real life, but it's not nearly as bad as it was before. I'm seeing better results by not using the IP test in the 'Manage Proxies' screen.

Hope this helps anyone with this trouble.
 
I give up -- it's like talking to a wall.

Anyway, for anyone who's looking for answers:

I've been seeing better results today. Still plenty of proxies are showing up as blocked in SB but not in real life, but it's not nearly as bad as it was before. I'm seeing better results by not using the IP test in the 'Manage Proxies' screen.

Hope this helps anyone with this trouble.

Could you explain what the difference is with the "IP Test" checkbox and what it actually does differently on and off?

Cheers
 
ip check off means the test isnt done against google
so instead of a list of proxies per say were only
say that list is 1000 proxies only say 100 would pass
the google check, with ip check off, probably 500 or so
will pass but, dont think the 500 will work to google scrape
because trust me they wont.. it might be a little more
but not that much
 
I give up -- it's like talking to a wall.

Anyway, for anyone who's looking for answers:

I've been seeing better results today. Still plenty of proxies are showing up as blocked in SB but not in real life, but it's not nearly as bad as it was before. I'm seeing better results by not using the IP test in the 'Manage Proxies' screen.

Hope this helps anyone with this trouble.

That's a good idea..thnx! I was pretty confused at SB's answer to my questions about this whole issue since I mentioned they were *private* proxies..so how could hundreds of other ppl be testing them..? :y:
Anyway..onward and upward!
 
My Squid proxies are working but they are much slower than the average, I hope that will be fixed anytime soon. I also have a problem scraping Google, only yahoo works.
 
Could you explain what the difference is with the "IP Test" checkbox and what it actually does differently on and off?

Cheers

Honestly, I have no clue. It's never been explained anywhere that I know of. As far as I can tell, though, it's not a g00gle check.

That's a good idea..thnx! I was pretty confused at SB's answer to my questions about this whole issue since I mentioned they were *private* proxies..so how could hundreds of other ppl be testing them..?

Exactly.

My Squid proxies are working but they are much slower than the average, I hope that will be fixed anytime soon. I also have a problem scraping Google, only yahoo works.

Right, that is what this thread is all about. The proxies still work in other sections of the software, just nothing that has to do with g00gle, apparently.
 
Could you explain what the difference is with the "IP Test" checkbox and what it actually does differently on and off?

The presence of the IP Test box in the window titled "Manage Proxies" indicates that you are using the OLD proxy harvester.

In the main Scrapebox window click Options and click Use New Proxy Harvester.

After doing that, when you return to the Manage Proxies window, you should no longer see the "IP Test" checkbox and you will now see an "Ignore Goog" checkbox in its place.

I've tried to sort through this thread and see if I could offer anything helpful, so there you go. Maybe someone who is having problems could test with the NEW proxy harvester/tester. Maybe do one test run that ignores goog and one that does NOT ignore goog. Hope this helps.

peace - gregs.

peace - gregs.
 
Back
Top