SOCKET ERROR - RECEIVE error: socket closed

giosal commented 7 years ago

I get this error on several machines.

I tested on all NH locations (EU, USA, CN, JP, IN, BR) with 1.7.5.12 and 1.7.5.13. I read one of the issues saying that I need to use different bitcoin addresses for machines on different network.

BUT:

all my machines are on the same network starting with 188.185
now I have 173 machines running
I had to reinstall several machines after windows update bsod'd on them
before update I had 225 machines running without problem.

Please advise. If I use different bitcoin adresses, then I'll have to use different stats page for each address, right?

giosal commented 7 years ago

Nothing?

giosal commented 7 years ago

this seems to be an issue related to network as tracert doesn't finish with success. any advice on firewall?

giosal commented 7 years ago

so, for several days all 223 workers were connected, but now they started to lose connection again. what's the problem? @S74nk0

giosal commented 7 years ago

only 193 workers have connection now...

giosal commented 7 years ago

now only 176 workers have connection, what's happening?

giosal commented 7 years ago

@S74nk0 @nicehashdev I also tried to start mining with another Bitcoin address, it still doesn't connect... so there seems to be a problem with you servers. I tried on EU, USA, HK, JP, IN and BR

smithinoz commented 7 years ago

Hi, yes I have the same issue. Started 12 hours ago down from 200 to 0. All mine are on the same network (public IP). Only 1 will connect, but the web site shows 0 with 0 hash. No issues with other pools. Looks like Nicehash suspect a bot attack and shut them down,

Genrymoney commented 7 years ago

https://new.nicehash.com/help/repeatedly-getting-socket-error-socket-closed

CrizzzSombiii commented 7 years ago

Same problem.

clarity99 commented 7 years ago

Same problem and I don't think the explanation on nicehash applies to this case - when it starts happening, it keeps going on all the time, and no mining happens at all. if i change to a different location it works ok for some hours, then again socket closed all the time. Then switch pool and again ok for some time. It can happen from different machines at the same time, with very different CPU configurations (one a VM, one a i5 3.4 ghz desktop).

[2017-10-19 13:16:44] : Connected. Logging in... [2017-10-19 13:16:44] : SOCKET ERROR - RECEIVE error: [2017-10-19 13:16:44] : Pool connection lost. Waiting 10 s before retry. [2017-10-19 13:16:54] : Connecting to pool cryptonight.eu.nicehash.com:3355 ... [2017-10-19 13:16:54] : Connected. Logging in... [2017-10-19 13:16:54] : SOCKET ERROR - RECEIVE error: socket closed [2017-10-19 13:16:54] : Pool connection lost. Waiting 10 s before retry. [2017-10-19 13:17:04] : Connecting to pool cryptonight.eu.nicehash.com:3355 ... [2017-10-19 13:17:04] : Connected. Logging in... [2017-10-19 13:17:04] : SOCKET ERROR - RECEIVE error: socket closed [2017-10-19 13:17:04] : Pool connection lost. Waiting 10 s before retry. [2017-10-19 13:17:14] : Connecting to pool cryptonight.eu.nicehash.com:3355 ... [2017-10-19 13:17:14] : Connected. Logging in... [2017-10-19 13:17:14] : SOCKET ERROR - RECEIVE error: socket closed [2017-10-19 13:17:14] : Pool connection lost. Waiting 10 s before retry. [2017-10-19 13:17:24] : Connecting to pool cryptonight.eu.nicehash.com:3355 ... [2017-10-19 13:17:24] : Connected. Logging in... [2017-10-19 13:17:24] : SOCKET ERROR - RECEIVE error: socket closed [2017-10-19 13:17:24] : Pool connection lost. Waiting 10 s before retry. [2017-10-19 13:17:34] : Connecting to pool cryptonight.eu.nicehash.com:3355 ... [2017-10-19 13:17:34] : Connected. Logging in... [2017-10-19 13:17:34] : SOCKET ERROR - RECEIVE error: socket closed [2017-10-19 13:17:34] : Pool connection lost. Waiting 10 s before retry. [2017-10-19 13:17:44] : Connecting to pool cryptonight.eu.nicehash.com:3355 ... [2017-10-19 13:17:44] : Connected. Logging in... [2017-10-19 13:17:44] : SOCKET ERROR - RECEIVE error: socket closed [2017-10-19 13:17:44] : Pool connection lost. Waiting 10 s before retry. [2017-10-19 13:17:54] : Connecting to pool cryptonight.eu.nicehash.com:3355 ...

qbac commented 7 years ago

I have the same problem:

[2017-10-22 16:19:02] : Connecting to pool cryptonight.eu.nicehash.com:3355 ... [2017-10-22 16:19:02] : Connected. Logging in... [2017-10-22 16:19:02] : SOCKET ERROR - RECEIVE error: socket closed [2017-10-22 16:19:02] : Pool connection lost. Waiting 10 s before retry (attempt 280). [2017-10-22 16:19:12] : Connecting to pool cryptonight.eu.nicehash.com:3355 ... [2017-10-22 16:19:12] : Connected. Logging in... [2017-10-22 16:19:12] : SOCKET ERROR - RECEIVE error: socket closed [2017-10-22 16:19:12] : Pool connection lost. Waiting 10 s before retry (attempt 281). [2017-10-22 16:19:22] : Connecting to pool cryptonight.eu.nicehash.com:3355 ... [2017-10-22 16:19:27] : Connected. Logging in... [2017-10-22 16:19:27] : SOCKET ERROR - RECEIVE error: socket closed [2017-10-22 16:19:27] : Pool connection lost. Waiting 10 s before retry (attempt 282). [2017-10-22 16:19:37] : Connecting to pool cryptonight.eu.nicehash.com:3355 ... [2017-10-22 16:19:37] : Connected. Logging in... [2017-10-22 16:19:37] : SOCKET ERROR - RECEIVE error: socket closed [2017-10-22 16:19:37] : Pool connection lost. Waiting 10 s before retry (attempt 283).

... ...

illtellyoulater commented 7 years ago

I am seeing this right now, anyone? Just yesterday I had it working with no issues at all.

Update: it must be a problem at a region-specific NiceHash end, temporarily choosing another region fixes it.

mojimi commented 6 years ago

I had this problem with both the Brazilian and American server, switched to European and it worked

mojimi commented 6 years ago

Nevermind, now the European is also giving the same problem

Cryptosynapse commented 6 years ago

This is happening to me also - only with cpu mining not gpu mining. All works well, then socket error. I restart cpu mining then all is well again for some time. Initially the problem was not as frequent, now it is happening all the time and I can't keep cpu mining open. GPU mining is fine.

BTW - I am not getting the retry messages.

mojimi commented 6 years ago

I am using a very weak intel i5 (50 mh/s) just to test NiceHash before buying better geat, is this issue related to having a weak setup? I'm kinda afraid to upgrade now.

semtex41 commented 6 years ago

Still seeing this problem, it continues to retry every 10 seconds and fails.

AlexVirlan commented 6 years ago

I just checked my workers. I have the same problem since last night. Any idea why?

dashony commented 6 years ago

Same issue here with both workers. It works for 1-2 hours or less sometimes and it fails on both machines with the above messages over and over again. It would not resolve on its own until I manually change servers and then I might get another hour or less until it stops working again, then no server would work. I also tried different wallet addresses on different workers and no difference. Any luck anyone? (i might need to stick with Kryptex, as it doesn't seem to fail)

dseeker commented 6 years ago

same issue. works for a few hours, then stopped working. Restart, same problem. was connecting only to EU, then tried USA, worked again. a few hours passed, now cant connect to any of the servers. was excited with nicehash, but this is a total dealbreaker

dseeker commented 6 years ago

I enabled a VPN connection and servers starting responding. Maybe an issue with ISPs blocking miners?

dashony commented 6 years ago

I’ve tried the VPN and worked for a little while and same thing happened again. Let us know @dseeker if you get a sturdy 48 hours before you get banned. I believe we’re getting a soft ban, that’s why we get disconnecred.

dseeker commented 6 years ago

can't say for 48h, cause I shut it down once a day. but it got much better than without the VPN. before the error would come within 15/30 minutes and stop all mining. With VPN I get the error but then it's followed by "All pools are dead. Idling..." and a few seconds later it starts again.

So it's definitely not a local issue with the software, either ISP or like you said some kind of server ban

dseeker commented 6 years ago

@dashony yeah, after about 12h I started getting the error again without recovery. Changed location of the VPN and it started working again. Damn... Can't be the case that everyone using NiceHash has the same issue. perhaps due to banning slower machines when pool is full?

mojimi commented 6 years ago

In the case of cryptonight yes, NiceHash cryptonight pools have a fairly high difficulty so if you're too slow you will get socket timeout all the time. If this is your case just learn to mine Monero directly using XMR-STAK and another pool

If this is not your case, try using NiceHashLegacy which is fairly more updated than this one ironically.

J0SH912 commented 6 years ago

I was having the same problem, created a new wallet and now it is working fine.

dashony commented 6 years ago

@J0SH912 I’ve tried different wallets a few days ago and it worked for a few hours then ran into the same issue. I think @mojimi is right. I only do CPU mining and as many above we seem to have the same issues under the same scenario and we’re getting some soft bans from the servers.

emerzon commented 6 years ago

Same issue here. My IPs keep getting banned after some 20/30 minutes running. I am also doing CPU mining with low hashrate. Is there some fix/workaround?

orphiler commented 6 years ago

same issue over here 👎 help pliz i use server rdp to mine it's CPU

[2018-01-12 13:30:17] : Start mining: MONERO [2018-01-12 13:30:17] : Starting double thread, affinity: 0. [2018-01-12 13:30:17] : hwloc: memory pinned [2018-01-12 13:30:17] : Starting double thread, affinity: 1. [2018-01-12 13:30:17] : hwloc: memory pinned [2018-01-12 13:30:17] : Fast-connecting to cryptonight.hk.nicehash.com:3355 pool ... [2018-01-12 13:30:17] : Pool cryptonight.hk.nicehash.com:3355 connected. Logging in... [2018-01-12 13:30:17] : SOCKET ERROR - [cryptonight.hk.nicehash.com:3355] RECEIVE error: socket closed [2018-01-12 13:30:47] : Fast-connecting to cryptonight.hk.nicehash.com:3355 pool ... [2018-01-12 13:30:48] : Pool cryptonight.hk.nicehash.com:3355 connected. Logging in... [2018-01-12 13:30:48] : SOCKET ERROR - [cryptonight.hk.nicehash.com:3355] RECEIVE error: socket closed

GalballyJ commented 6 years ago

same problem here but on a smaller scale. all the machines from location1 cannot connect and get sent a RESET after login. machines ni location 2 and 3 work ok tho. same error on all the pools so its not region specific

orphiler commented 6 years ago

and what is the solution ?

https://mailtrack.io/ Sent with Mailtrack https://chrome.google.com/webstore/detail/mailtrack-for-gmail-inbox/ndnaehgpjlnokgebbaldlmgkapkpjkkb?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality

2018-01-12 15:03 GMT+01:00 GalballyJ notifications@github.com:

same problem here but on a smaller scale. all the machines from location1 cannot connect and get sent a RESET after login. machines ni location 2 and 3 work ok tho. same error on all the pools so its not region specific

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nicehash/NiceHashMiner/issues/1041#issuecomment-357245963, or mute the thread https://github.com/notifications/unsubscribe-auth/Ahu88dNdmKa1g6fuoPiMrSBeQ9beoQ9Zks5tJ2YfgaJpZM4N9DJF .

pfilias commented 6 years ago

I just started with nicehash today and am getting this issue right from the get-go. Nobody has found a solution yet?

Mine also outputs:

SOCKET ERROR - SEND error: An established connection was aborted by the software in your host machine.

That's nuts, because I have disabled my Norton firewall.

I did a little more digging with Norton and found this:

Category: Intrusion Prevention Date & Time,Risk,Activity,Status,Recommended Action,IPS Alert Name,Default Action,Action Taken,Attacking Computer,Destination Address,Source Address,Traffic Description 1/20/2018 5:18:56 PM,High,An intrusion attempt by cryptonight.usa.nicehash.com was blocked.,Blocked,No Action Required,System Infected: Bitcoinminer Activity 6,No Action Required,No Action Required,"cryptonight.usa.nicehash.com (198.11.220.44, 3355)","DESKTOP-K0P1NLV (192.168.1.100, 52698)",cryptonight.usa.nicehash.com (198.11.220.44),"TCP, Port 3355" Network traffic from cryptonight.usa.nicehash.com matches the signature of a known attack. The attack was resulted from \DEVICE\HARDDISKVOLUME8\USERS____\APPDATA\ROAMING\NHM2\BIN\XMR-STAK-CPU\XMR-STAK-CPU.EXE. To stop being notified for this type of traffic, in the Actions panel, click Stop Notifying Me.

xberg commented 6 years ago

Same problem here. New to Nicehash. 2 workers. Worked fine for 1 week and today I have been blocked. Of course no fishy activity on my side. Sometimes I am able to connect again for a few minutes, then I lose the connection with the server. Tried both CPU and GPU and different algos. Disabled any firewall or anti virus. Each worker has 2 CPU running + 1 GPU. EDIT: lasted 3 hours and then restarted without me changing anything.

nicehashdev commented 6 years ago

Please note that if your miner does not send any share in 5 minutes your connection will be temporarily blocked.

The difficulty for mining Cryptonight is very high at the moment because a lot of miners are mining it and miners with better hardware get shares faster than you.

Kind regards, NiceHash Team

On 28 Jan 2018, at 20:36, xberg notifications@github.com wrote:

Same problem here. New to Nicehash. 2 workers. Worked fine for 1 week and today I have been blocked. Of course no fishy activity on my side. Sometimes I am able to connect again for a few minutes, then I lose the connection with the server. Tried both CPU and GPU and different algos. Disabled any firewall or anti virus.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nicehash/NiceHashMiner/issues/1041#issuecomment-361089306, or mute the thread https://github.com/notifications/unsubscribe-auth/AKXVzsXGdMrMoXr7PSTZmSOV3TsTBqKtks5tPMxNgaJpZM4N9DJF.

xberg commented 6 years ago

Here we go again: both my miners stopped at the same time. No more connection. One connected to US, the other to Europe. All on different algo. I'm losing mining time with this problem. Is there a way to set an alternative mining pool?

thecadman99 commented 6 years ago

Same problem- 20 miners work for 24 hours or so, then off for the same amount of time. Change wallet and still no connection. Really need help with this!

dseeker commented 6 years ago

I'm wondering if something like this helps, has anyone tried? https://github.com/xmrig/xmrig-proxy

AlexVirlan commented 6 years ago

I have a working solution! I'm working on an app that can manage all this disconnections and keep the NHM working. I just need just a little bit more time for some final testing, and I will release it for free.

emerzon commented 6 years ago

According to the docs, it cannot be used with Nicehash.

2018-01-30 10:24 GMT+01:00 D See Ker notifications@github.com:

I'm wondering if something like this helps, has anyone tried? https://github.com/xmrig/xmrig-proxy

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nicehash/NiceHashMiner/issues/1041#issuecomment-361529212, or mute the thread https://github.com/notifications/unsubscribe-auth/AZkvd9pveb4JqLuDewLBSXfFCXxIHHLuks5tPt-wgaJpZM4N9DJF .

emerzon commented 6 years ago

Awesome!!! Waiting for it :)

2018-01-30 10:28 GMT+01:00 AAv.Soft notifications@github.com:

I have a working solution! I'm working on an app that can manage all this disconnections and keep the NHM working. I just need just a little bit more time for some final testing, and I will release it for free.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nicehash/NiceHashMiner/issues/1041#issuecomment-361530612, or mute the thread https://github.com/notifications/unsubscribe-auth/AZkvd0g0tXoIULAFoKrxnvga9yU1eDHSks5tPuCggaJpZM4N9DJF .

AlexVirlan commented 6 years ago

@emerzon Wait until you see it. It won't affect the connection. It does't even touches the connections or anything else about the NHM's system or protocol. I'm doing this release to help those people who have the "socket problem".

xberg commented 6 years ago

@AAv-Soft That's fantastic news. So what exactly is the root cause of this error?

AlexVirlan commented 6 years ago

@xberg Thank you for your interest. As @nicehashdev mentioned, the NH pool is configured in such a way that "if your miner does not send any share in 5 minutes your connection will be temporarily blocked ". Because as the difficulty for mining increases, miners with better hardware get shares faster. So you get blocked for not submitting results and for trying to get in every few seconds. So this app will check your CPU or GPU status, and if you are not mining for a period of time, it will automatically stop mining, wait until the block time is over, then switch the mining server and start again. And you won't have to do this by hand.

xberg commented 6 years ago

@AAv-Soft Somehow I doubt this is the real reason. Otherwise why would ALL my miners stop at exactly the same time? All using different algos. Do you think that just because 1 worker is inefficient nicehash blocks all? If that's the case they have a real problem.

AlexVirlan commented 6 years ago

@xberg

What NHM version are you using?
Are you mining on CPU and GPU at the same time or only one of them?
Are you mining with all algos on the same BTC address?

xberg commented 6 years ago

@AAv-Soft

Nicehash 1.8.1.16 legacy
Yes: CPU and GPU at the same time
Yes: all algos and all workers on the same address.

mojimi commented 6 years ago

@nicehashdev Ok but why not implement different difficulty ports like every cryptonight pool? The whole appeal of cryptonight is that you can mine using your cpu, what's the point if you can only mine with 500h/s+?

AlexVirlan commented 6 years ago

@mojimi Exactly my idea. That's the problem. @xberg "3. Yes: all algos and all workers on the same address." Well, my theory is that they block the wallet address.

xberg commented 6 years ago

@mojimi I am getting blocked with over 2500 h/s in cryptonight so I really don't think this explanation is correct. @AAv-Soft If that's the case it's a serious bug on their side. Imagine a mega farm in which someone connects a small laptop to demo mining. The laptop under performs and the whole farm is blocked :) Or worse: I could connect my laptop to your wallet and block you? Nonsense.

I think @nicehashdev does not know the root cause and just came up with the first idea he had. Which of course is the natural thing to do, but the issue deserves more exploration.

mojimi commented 6 years ago

@xberg I mine 2400 h/s Cryptonight to NiceHash and had no problems.

Have you tried using the legacy miner? Despite the name it is the more updated version.

But here's how I do it; I use xmr-stak miner and point it to NiceHash's Cryptonight pool, I use the BR server as its closer to me, works like a charm.

nicehash / NiceHashMiner-Archived

SOCKET ERROR - RECEIVE error: socket closed #1041