+- ScrapeBox Forum (https://www.scrapeboxforum.com)
+-- Forum: ScrapeBox Main Discussion (https://www.scrapeboxforum.com/Forum-scrapebox-main-discussion)
+--- Forum: General ScrapeBox Talk (https://www.scrapeboxforum.com/Forum-general-scrapebox-talk)
+--- Thread: Connection reset by peer / Socket Error # 10054 (/Thread-connection-reset-by-peer-socket-error-10054)
Connection reset by peer / Socket Error # 10054 - thedudezor - 12-01-2016
I seem to be running into this problem more and more often since the past few SB updates have been pushed out. While I have not tried to reverting back to a older version yet, but I wanted to see if anyone else has seen or knows what might be causing this issue.
The short version is, when I start a custom harvester it will run through a small list of keywords, then hit a wall and just error out over and over again. When I view the harvester error log, I see line after line of:
HTTP: -1 Socket Error # 10054
Connection reset by peer.,
RE: Connection reset by peer / Socket Error # 10054 - loopline - 12-01-2016
Are you using public or private proxies?
Ive had a few other people say this, but typically this is consistent with security software. So you reach a threshold (the wall) and then it errors because the connections are being hijacked and closed.
So set Scrapebox as trusted/allowed in all security software. Taking care that you whitelist becuase just disabling will only stop new rules from forming.
RE: Connection reset by peer / Socket Error # 10054 - thedudezor - 12-01-2016
I'm using public proxys and yes the issue goes away if I use my host IP as the exit point. I know blocking can be a issue, but this seems to be something different.
Thank you for the idea of checking anti-virus, firewall. I disabled these and put my computer into the DMZ and made no difference. Only step left I guess is to bypass my router to see if that may be dropping the connections somehow. Not sure why something may have changed, its the same gear I've been using for well over a year now.
RE: Connection reset by peer / Socket Error # 10054 - thedudezor - 01-06-2017
This issue seems to have been addressed in the latest version 2.0.0.82
Now the error logs show the actual reason the error's occurred and isn't hitting a brick wall and just error'ing out in large batches with out even making a attempt to crawl the destination.
RE: Connection reset by peer / Socket Error # 10054 - loopline - 01-08-2017
Glad that its sorted, the .82 version attempted to fix it and it has for everyone I have talked to.