NiceHashMiner-Archived
NiceHashMiner-Archived copied to clipboard
nicehash
SOCKET ERROR - RECEIVE error: socket closed
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?
this seems to be an issue related to network as tracert doesn't finish with success. any advice on firewall?
so, for several days all 223 workers were connected, but now they started to lose connection again. what's the problem? @S74nk0
@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
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,
https://new.nicehash.com/help/repeatedly-getting-socket-error-socket-closed
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 ...
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).
... ...
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.
I had this problem with both the Brazilian and American server, switched to European and it worked
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.
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.
Still seeing this problem, it continues to retry every 10 seconds and fails.
I just checked my workers. I have the same problem since last night. Any idea why?
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)
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
I enabled a VPN connection and servers starting responding. Maybe an issue with ISPs blocking miners?
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.
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
@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?
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.
I was having the same problem, created a new wallet and now it is working fine.
@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.
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?
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
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
