ScrapeBox proxies- testing IP security always FAIL

4 replies
  • SEO
  • |
I'm having an "error timeout" and "error 0" everytime I test public proxies right after the "...testing ip security" process, I've tried using thousands and from different sources and it's always the same thing, what's going on?

thanks!
#fail #proxies #scrapebox #security
  • Profile picture of the author seoposter
    I haven't tested my copy for this lately, but the last time I checked it works fine. Could it be that the list of IPs you have is already overused by other SB users? If you are sourcing your list online, chances are you are using an already overused resource. Why not rent a list of IPs instead?
    {{ DiscussionBoard.errors[6890569].message }}
    • Profile picture of the author Digitalis
      Originally Posted by seoposter View Post

      I haven't tested my copy for this lately, but the last time I checked it works fine. Could it be that the list of IPs you have is already overused by other SB users? If you are sourcing your list online, chances are you are using an already overused resource. Why not rent a list of IPs instead?
      well, most people seem to scrape with public proxies, they should work atleast for that no?
      {{ DiscussionBoard.errors[6894531].message }}
  • Profile picture of the author johnben1444
    Does it occur immediately you click the test ip or it try to run before giving you the error.

    There are 3 issues that will likely cause this.

    1. Your firewall is blocking scrapebox.
    2. Your connection is weak or set too low.
    3. The use of public proxy is not advisable, they burn out quickly.
    Signature
    Grow your social media account, Spotify Streams, YT Views & IG Followers & More
    Software & Mobile APP Developer
    Buy Spotify, Facebook Bot & IG M/S Method
    {{ DiscussionBoard.errors[6894568].message }}
  • Profile picture of the author Jubu
    Scrapebox uses their own servers for proxy testing or something like that. The error you mention was coming up when they were under a DDoS attack. It should be good now.
    {{ DiscussionBoard.errors[6894631].message }}

Trending Topics