Nooby aint got a scooby with Socket Error #10054

MrThingy

Newbie
Joined
Aug 18, 2020
Messages
25
Reaction score
3
Hi guys and girls,

From what I can see this might be the best place to get some help with a very annoying Socket error.

I'm new to BHW and hope you are a nice bunch :)

I'm having issues with Scrapebox Socket Error #10054 despite closing all Malware Bytes and other running processes. Allowed in Firewall too so I am not sure what to do.

Any ideas? I am beginning to wonder if in an old job my machine has been hacked although it seems clean.

Thanks a mill

MrThingy
 

Attachments

  • SB.png
    SB.png
    18.5 KB · Views: 21
Thats a socket forcibly closed error. So proxies, especially public proxies can cause this.

Even when you shut down many security software they still fire on existing rules, so you need to add exceptions for the entire scrapebox folder in all security software.
 
Sir, thank you.

I did as you asked and reduced the number of threads the email harvester was running. Seems to have done the trick! It's now just running very slooooowly. :weep:
 
Great glad that sorted it! Sometimes a system cant handle so many threads per an instance, but if your on windows you can run an unlimited number of scrapebox instances on that machine. So you can thus break up your list and essentially speed things up that way. Windows tends to like more instances running less threads as opposed to 1 instance running lots of threads.

 
Matt, you're a legend. Thanks pal. How will I go on with Storm Proxies if I have a 40/10 subscription. Guessing multi instances will likely get me a ban? I've noticed the *FREE Proxy sites even using GSA are all a bit suspect now. I would have otherwise split proxies from Private/Public but the public ones are as effective as a chocolate teapot of late...
 
Matt, you're a legend. Thanks pal. How will I go on with Storm Proxies if I have a 40/10 subscription. Guessing multi instances will likely get me a ban? I've noticed the *FREE Proxy sites even using GSA are all a bit suspect now. I would have otherwise split proxies from Private/Public but the public ones are as effective as a chocolate teapot of late...
Not sure what your asking. Just lower total connections.

If your running 4 instances, divide your total connections by 4. So you have a 40/10 so thats 10/2.5 (obviously round the 2.5 down or up depending).
 
Back
Top