Recent Scrapebox Proxy Issue, everyone should note

The last update 1.15.36 from yesterday should solve most proxy issues.
At least, it did for us during the test of the new code.

Proxies working in FF and not is SB means you have a google cookie which allow that proxy to work... delete the google cookies, and turn js off, and the proxy might not work anymore in google search.

About IP test: IP test will do a test to check if your IP is transparent or not.
 
Proxies working in FF and not is SB means you have a google cookie which allow that proxy to work... delete the google cookies, and turn js off, and the proxy might not work anymore in google search.

I already told you that I don't use js in FF and I have cookies off and the proxies still work in FF but not in SB. So that is not the issue.
 
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.

Good to know.

The proxy issue, though, was happening with both the old and new harvesters when I opened this thread.

UPDATE

I'm running a test right now with the 1.15.36 update and the new harvester because I hadn't used the new harvester yet since the update a couple days ago, aaannd... So far so good!

This makes me happy. And I hope other people begin reporting positive results as well. Please let us know!

And thank you SB for fixing it. :)

Some suggestions for the future:

1. You should keep in touch with people who put in support tickets and don't be so quick to assume the problem is on their end. I put in a lot of effort and time to get to the root of this and I don't think you guys gave me fair credit there. I'm not getting paid for it, you are. Just some customer feedback here..

2. I don't like how SB doesn't have an option to use or not use transparent proxies (assuming what gregs posted is true). Many are passing G00G test but failing IP test. Well, when I use those proxies they work fine for scraping and other things, so to not consider them working or "good" isn't acceptable for me, and I would suspect others would agree. They should be considered in some way, like state that they are "good" but transparent or something. Because out of about 60 proxies i just tested that pass G00G test, only 12 passed the IP test. So how do I sort out the transparent ones?
 
Last edited:
So far so good!
Not so good :(

I've found after update that proxies on one exact port are always mark as FAILED.

The last update 1.15.36 from yesterday
About IP test: IP test will do a test to check if your IP is transparent or not.
What kind of transparency are we talking about? Because from what I see many of transparent proxies (L3) passes IP test.

So what exactly check "IP Test"?
 
using transparent proxies doesnt matter if its for scraping
sup gregstereo my first user to my service all those yrs ago
anyways. transparent proxies only matter if u intend to try
and post with public proxies and for that fix is easy. download
forum proxy leecher..install a good proxy judge set connections
to 200 test your list only use the level 1/2 to test in s/box if u only
intend to post..if your scraping how ever you can throw anything in
to test
 
Not so good :(

I've found after update that proxies on one exact port are always mark as FAILED.


What kind of transparency are we talking about? Because from what I see many of transparent proxies (L3) passes IP test.

So what exactly check "IP Test"?

Forget transparent proxies. When I posted that, I might have been somewhere else :)

What port is always FAILED for you?

What I meant to say is, IP test does a test to see if the proxy is hiding your IP or not.
 
i will just add i did s/box update today.
now for the last few days around mid-day
ive averaged 7-800g passed today it was 920
tonight 12 hrs later wich is always lower for me
remained the same just over 500
 
What port is always FAILED for you?

New update 1.15.37 fix it.

What I meant to say is, IP test does a test to see if the proxy is hiding your IP or not.

But still it's not completely true because transparent proxy isn't able to hide your IP and SB can mark L3 proxy in IP Test as PASSED. Why? What exactly IP Test check?

All the best. :)
 
New update 1.15.37 fix it.



But still it's not completely true because transparent proxy isn't able to hide your IP and SB can mark L3 proxy in IP Test as PASSED. Why? What exactly IP Test check?

All the best. :)

I wont post here how ScrapeBox's proxy harvester/tester is functioning internal, but as I wrote earlier, it will test if a sever can receive your real ip (BAD), or just see the proxy ip (GOOD)
 
using transparent proxies doesnt matter if its for scraping
sup gregstereo my first user to my service all those yrs ago
anyways. transparent proxies only matter if u intend to try
and post with public proxies and for that fix is easy. download
forum proxy leecher..install a good proxy judge set connections
to 200 test your list only use the level 1/2 to test in s/box if u only
intend to post..if your scraping how ever you can throw anything in
to test

Hey proxygo - yeah, I just noticed in this thread that there was a lot of people indicating that they might be using the old harvester, and to help sort things out figured I'd call attention to that. Hope it's helping people get things sorted.

Reading the last few posts after yours, it sounds like things are headed in a better dircection at least.
 
Forget transparent proxies. When I posted that, I might have been somewhere else :)

What port is always FAILED for you?

What I meant to say is, IP test does a test to see if the proxy is hiding your IP or not.

The problem is that if a proxy isn't hiding my IP, it gets marked as FAILED, even if it passes g00g check. Now I can't use perfectly good proxies. :rolleyes:
 
The problem is that if a proxy isn't hiding my IP, it gets marked as FAILED, even if it passes g00g check. Now I can't use perfectly good proxies. :rolleyes:

Yes, thats the correct way. Why would you use a proxy which will just leak your IP?
 
@gregstereo, So when I keep "ignore goo" ticked, I get many IP test passed proxies, but when I transfer them into the proxies area and try to scrape a keyword, I get 0 results. And when the "ignore goo" box is unticked, I get a few g-approved (four), and with these I scraped some urls. My question is: what good are the IP passed proxies, since you can't scrape with them, and what function do they serve?
 
@gregstereo, So when I keep "ignore goo" ticked, I get many IP test passed proxies, but when I transfer them into the proxies area and try to scrape a keyword, I get 0 results. And when the "ignore goo" box is unticked, I get a few g-approved (four), and with these I scraped some urls. My question is: what good are the IP passed proxies, since you can't scrape with them, and what function do they serve?

They're not mutually exclusive, they're daisy-chained. goo passed proxies can pass the IP test; the goo test checks if the proxy is blocked by goo; the IP test checks if the proxy is leaking your info to the world.

If you ignore gooooooooooogle when testing proxies, that kind of implies that you aren't going to scrape from the search engine.

Here's real-life examples:

Non-goog tested, IP passed proxies are good for posting to sites that you have previously scraped, or to lists you have downloaded, etc. It's a matter of speed:

if you're looking to scrape goog, run PR checks, etc., run both tests (goog+IP test checks that goog isn't blocking a proxy and that the proxy isn't leaking)

if you're just looking to post to an existing list, run only the IP test

Make sense?
 
Last edited:
Make sense?

Yes, it does, thank you very much for the explanation. I let SB scrape proxies all night with the "ignore g" unchecked. This morning I find it has found about 200. So I hit export and save to disc, but when I opened the file it was empty. I had already closed SB and therefore lost all the proxies -- man was I p***ed.
Sorry to impose on you, gregstero, but can you explain why SB went through the save proxies motion and actually saved nothing? When the "ignore g" was checked, the proxies were saved nicely to a file.
 
Why is that up to SB to decide?

Because people want to protect/hide their own IP's as much as possible.
And this is what ScrapeBox provide.

If you want to use proxies which are leaking you real ip, then just add them to the proxy memo without having ScrapeBox test them, easy as that.
 
Because people want to protect/hide their own IP's as much as possible.
And this is what ScrapeBox provide.

If you want to use proxies which are leaking you real ip, then just add them to the proxy memo without having ScrapeBox test them, easy as that.

I wish it were that easy, but it's not.

Most proxy testers have a function showing whether or not the proxy is transparent, anonymous, high anonymous or elite, and SB doesn't for some reason. Instead, it makes a decision for me and blankets my proxies into 2 categories: working and not working. But the not working work!

So... SB is not the best proxy tester, for sure. The rest of the software is great though ;)
 
I wish it were that easy, but it's not.

Most proxy testers have a function showing whether or not the proxy is transparent, anonymous, high anonymous or elite, and SB doesn't for some reason. Instead, it makes a decision for me and blankets my proxies into 2 categories: working and not working. But the not working work!

So... SB is not the best proxy tester, for sure. The rest of the software is great though ;)
Tensegrity, what proxy tester do you recommend?
 
@equalizer:

On your earlier question to me, I've no idea what happened when you saved proxies in sbox. Does the scenario you described happen consistently, or was it a one off? I've never had that issue with sbox.

And personally, my experience with sbox and proxies has been quite positive. It does a very specific job for its proxy tester and (IMO) it does it very well. I get what Tensegrity is saying as far as reporting of type of proxy, but SB doesn't do that. As far as a proxy tester in general, IMO you can't go wrong with Charon:

http://www.blackhatworld.com/blackh...rty-guide-charon-free-good-proxy-checker.html
 
Back
Top