1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Scrapebox, Private Proxies & VPS

Discussion in 'Black Hat SEO' started by akazzz, Mar 13, 2012.

  1. akazzz

    akazzz Regular Member

    Joined:
    Dec 17, 2011
    Messages:
    377
    Likes Received:
    149
    Location:
    Building The Empire
    So I just got my vps from bermanhosting and tested out my private proxies over on scrapebox.
    Results: 3/20 passed.

    So I requested another 20, and tested them out straight away.
    Results: 4/20 passed.

    I'm not sure which side is causing the problem. I already authorized my vps' ip to work with my private proxies. What is causing the problem here?

    I went on to test out my private proxies over at Sick Submitter and it says all the proxies are ok.

    Are there any step-by-step solution to get private proxies to work on my VPS with scrapebox? Cause from what I know, its just 1) authorized my proxies 2) plug in my proxies 3) Run
     
  2. SuperLinks

    SuperLinks Elite Member

    Joined:
    Jul 14, 2008
    Messages:
    2,903
    Likes Received:
    847
    Location:
    New York
    Scrapebox has been having issues with the latest version and their IP testing for Proxies.

    I'm not entirely sure as to what exactly the problem is since I haven't updated any of my Scrapebox's to the latest versions but apparently its having problems.

    It COULD be that, but I'm not positive. Who is your proxy provider?
     
  3. akazzz

    akazzz Regular Member

    Joined:
    Dec 17, 2011
    Messages:
    377
    Likes Received:
    149
    Location:
    Building The Empire
    IPXPRT from BST. I'm not sure what's the problem because from what I can assume, its either my vps or my proxy provider.
     
  4. LakeForest

    LakeForest Supreme Member

    Joined:
    Nov 11, 2009
    Messages:
    1,269
    Likes Received:
    1,802
    Location:
    Location Location
    The problem wouldn't be the VPS. Scrapebox is currently figuring out proxy accuracy, and it is difficult to do since they judge it based on Google's search and that's changing all the time. You can't even scrape with a really old version of SB.

    Just use your private proxies for now, but don't test them. If they don't scrape and if you can't post, get a new proxy provider. (make sure your proxies are actually dedicated)

    I'm running 1.15.38 and 1.15.42 and I combine my google passed proxy lists in both versions to scrape and everything works fine. It's ridiculous to have to do this, but it works :\

    To post, don't listen to the tester. Get your proxies, post with them, check the status of each proxy and make sure it's not dead.
     
  5. akazzz

    akazzz Regular Member

    Joined:
    Dec 17, 2011
    Messages:
    377
    Likes Received:
    149
    Location:
    Building The Empire
    I was using my private proxies and all tested "Ok" 2 updates ago before I got my vps. So, you're saying scrapebox had problem with their proxy accuracy within these 2 updates?

    How do you check the status of each proxy by not going through the tester?
     
  6. LakeForest

    LakeForest Supreme Member

    Joined:
    Nov 11, 2009
    Messages:
    1,269
    Likes Received:
    1,802
    Location:
    Location Location
    There were 4 updates in like 2 days lol. The accuracy problem was really apparent in 1.15.38, a few versions before that things were alright.

    Then 1.15.39 happened...And the world went to hell for a little. New harvester, more columns of info, lost almost all intuitiveness.

    Now, 1.15.42, things are a lot better.

    I usually go balls to the wall and post without checking when using private, and if it doesn't post or the success rate is way too low, I'll check. I test in .38 and .42.

    EDIT: wait, tested "OK"? The old harvester! when everything made sense! now it's about PASSED and FAILED. lol what version # were you using? Was it 1.15.31 - .35? This is like an antique collector's item show.
     
  7. danny1

    danny1 Regular Member

    Joined:
    Oct 8, 2009
    Messages:
    269
    Likes Received:
    112
    Agree that the Proxy Tester was broke between v1.15.39 - 1.15.41

    One way would be to do a quick harvest to make sure the proxies are not blocked; by not using the multi-threaded harvester, you can visually see if they get blocked or not. Another way is to use the old Tester; uncheck: Options > Use new harvester.

    You can also roll back to previous versions (pre-1.15.39) from the Help menu.