Scrapebox ALL Proxies 302 IP Blocked (started recently)

[freller]

I'm still OK with Yahoo but Google is a nightmare.

From all that's being said I get the impression that public proxy lists are getting very quickly banned by Google AND they're very quickly jumping on multi-threaded requests using the same complex operators, regardless of the IP's being used. It's simple stats really - how many NATURAL simultaneous requests come in for, say, inurl:/register intext:"upcoming" intext:"published" intext:"submit" intext:"Tag Cloud" -inurl:.php etc.?

Whatever the real reasons this has all started to 'terminate with prejudice' in the last month or so.

 

[utuxia]

I'm still OK with Yahoo but Google is a nightmare.

From all that's being said I get the impression that public proxy lists are getting very quickly banned by Google AND they're very quickly jumping on multi-threaded requests using the same complex operators, regardless of the IP's being used. It's simple stats really - how many NATURAL simultaneous requests come in for, say, inurl:/register intext:"upcoming" intext:"published" intext:"submit" intext:"Tag Cloud" -inurl:.php etc.?

I never scrape google with more than 1 thread when using advanced operators.

 

[directaxcess]

Scrapebox support has told me that the dev team is trying to bypass this issue at the moment so let's see what happens. I'll just use the single threaded harvester but even that's barely working.

 

[utuxia]

Yeah. it's becoming a real problem for me too.

 

[Dan Da Man]

I am getting 307 Error for blog analyzing and do follow blog analyzer.

Anyone else getting this? Started happing 2 days ago. I am using 200 private proxies

 

[directaxcess]

Yeah. it's becoming a real problem for me too.

Yea man, I really hope Scrapebox gets this sorted out soon. I think to expedite this however, everyone should open a support ticket with Scrapebox support so they can see that its a real issue and get a fix out asap. I haven't been able to harvest anything properly for two weeks now, so no fresh backlinks for me . Stupid Google, first the penguin and now this... come on.

 

[123again]

I believe this is SB's problem but not proxy problem, just wait program update from SB

 

[123again]

I think it is not SB's problem. Google controls what constitutes and IP ban. How would scrapebox be able to work around an ip ban?

If IP ban of course it is not SB problem
But it is too early to say it is IP ban,you can find from above replies some test the "banned IP" on webbrowser but it worked ,so it is not IP ban but SB's misjudge, I guess the real reason should be some small change on google search result but SB not catch the new update.

 

[directaxcess]

Ahh. yeah. Sorry about that, if it works in browser w/o ban (and hitting refresh a lot) then it might not be a real ban.

It's probably the fact that Google is detecting searches from a large # of proxies for the same footprints/keywords -- however, if this were the case, shouldn't the proxies work in single threaded harvester (especially when they're Google pass)? It's surprising to me that the single threaded harvester is getting blocked by Google; how is that even possible considering the fact that the software is making only one query at a time using GOOGLE PASS proxies? It just doesn't add up -- I'm pretty sure Scrapebox's proxy judge is probably messed up but I hope they come up with a fix soon.

 

[Junkfood00]

Yeah, this started to get annoying. Have the same issue here. We're now forced into paying to use the scrape tool.

 

[directaxcess]

The 302 IP ban is a temporary ban, and sure if they see the same query past page 2, it is obviously an automated query.

Yea but all my proxies are blocked from the beginning, it's not like they're able to harvest something from the first page and THEN get banned... all my proxies just immediately return a 302 IP ban -- how is Google doing that?

 

[itos84]

I also have the 302 IP Ban problem, and not one Google pass proxy from the Scrapebox harvester is working. So the Google harvester is useless right now. Hope the Scrapebox team can fix this soon. Some weeks ago I didnt have this problem.

 

[awsomnick1]

Working fine for me for google, i checked a batch of 3k from my sources and got 1k and i scraped google multithreaded fine for like 12k results and stopped it

 

[Junkfood00]

Working fine for me for google, i checked a batch of 3k from my sources and got 1k and i scraped google multithreaded fine for like 12k results and stopped it

I'm not sure if you're allowed to promote your services like that but I'll save your link in case I need proxies later..

 

[loopline]

Scrapebox support has told me that the dev team is trying to bypass this issue at the moment so let's see what happens. I'll just use the single threaded harvester but even that's barely working.

Yeah, I talked to them about it too. Its actually being widely talked about on the internet and affecting all SEO tools. The issue is that google has recently tightened down on IP bans. They aren't executing with any rhyme or reason, so its hard to pin point. Like if you do a proxy test, and you will get X google passed proxies, then do another test immediately thereafter, a ton of them will be blocked. Its basically that google has changed the rules of the game, and everyone playing the game is not trying to reinvent the strategy they are using.

I scrape with private proxies and public. Right now I am pretty much only using private proxies, with no issues. Although, there are still public proxies to be had for sure. Proxygo for instance is still putting out good lists etc...

 

[john1444]

For those using Proxygoblin and getting 302 error and proxy blocked should know that this tool only scrape proxies from the search engines, servers of free IP which thousands of other people have access to and use at the same, therefore this kind of IP is never going to be reliable for a second.

I have been using my IP for over 3 weeks now and still very usable, active and fast.

 

[proxygo]

ty for the comments loopline.

well im port scanning lists of public proxys from isp's around the world
because url scraping public proxies is a waste, there over used. to few.
at least with port scanning multiple isp blocks im still getting an average
of 1.5k - 2 k google passed proxies per list twice a day every day for the
last 28 months and these can not be scraped . only port scanned .
but no issues here

 

[directaxcess]

ty for the comments loopline.

well im port scanning lists of public proxys from isp's around the world
because url scraping public proxies is a waste, there over used. to few.
at least with port scanning multiple isp blocks im still getting an average
of 1.5k - 2 k google passed proxies per list twice a day every day for the
last 28 months and these can not be scraped . only port scanned .
but no issues here

Haha I didn't understand all that technical stuff... mind explaining it a little bit more? I don't have a problem with scraping Google pass proxies, I can easily get 600 Google pass from my own public proxy sources (not Scrapebox built in), but when I actually go to harvest, most if not all of them return a 302 IP blocked error. I see in your signature that you are sharing lifetime access to Scrapebox Google pass proxies? Just PM'd you for a sample to see if they work in my Scrapebox and if they do then I wouldn't mind that lifetime subscription at all.

 

[loopline]

Haha I didn't understand all that technical stuff... mind explaining it a little bit more? I don't have a problem with scraping Google pass proxies, I can easily get 600 Google pass from my own public proxy sources (not Scrapebox built in), but when I actually go to harvest, most if not all of them return a 302 IP blocked error. I see in your signature that you are sharing lifetime access to Scrapebox Google pass proxies? Just PM'd you for a sample to see if they work in my Scrapebox and if they do then I wouldn't mind that lifetime subscription at all.

They work, proxygo is legit. I have watched him on screen sharing as he port scans and does what he does. He is the real deal. He is the only provider I know that does this, I can't say No one else does, but he provides solid working lists. I have had his lifetime service for over a year now and its always been good.

The short of it is, proxygo goes straight to the source and cuts out the middle man. When you scrape a list of public sources, these are lists of proxyies that someone has port scanned and then shared publicly, then they get scraped from that list and reshared a hundred places online and every one scrapes them and uses them, and they die.

Proxy go goes out and scans blocks of IP ranges to find out if they have any working proxies, when he finds them he shares them directly only with his paid buyers, which is a pretty tight nit group. We use them, they last much longer then scraped public proxies cause he scans ports and ip ranges that he finds that aren't being shared. In fact I don't use them daily, but when I want to do a big scraping one, I will go back and download his lists that are days old and the new ones and shove them all in, cause his old lists still have a high success rate cause there aren't being widely used.

Anyway, thats my 2 cents. But as for you issue its either 1 of 2 things. If you retest those 600 proxies you get you will likely see a lot of them then fail, thats because google is cracking down a lot lately on banning ips that get used a lot. If thats not the case, then Ill bet your using advanced operators, in which case they play by different rules and I explain that here:
[video=youtube_share;P9CbGhfc1aY]http://youtu.be/P9CbGhfc1aY[/video]

 

[ShabbySquire]

Thanks Loopline for your video, should help in cutting down the G bans.