search

nicehash / NiceHashMiner-Archived

NiceHash easy to use CPU&GPU Miner
840 stars 327 forks source link

SOCKET ERROR - RECEIVE error: socket closed #1041

Open giosal opened 7 years ago

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:

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

xberg commented 6 years ago

@mojimi Yes: I use the legacy 1.8.1.16.

xberg commented 6 years ago

@mojimi : what do you mean by you point it to Nicehash's CN pool? I just define the "service location". Do you precisely define the pool? As in: stratum+tcp://cryptonight.eu.nicehash.com:3355 ?

mojimi commented 6 years ago

@xberg I meant that I don't use NiceHash's miner, I use XMR-Stak Cryptonight miner as I know it will always be the most profitable in my hardware.

Just set the pool config as "cryptonight.eu.nicehash.com:3355" and enable the NiceHash option, its pretty simple

xberg commented 6 years ago

Sometging interesting just happened with EthDcrMiner64: ETH: Stratum - connecting to 'daggerhashimoto.eu.nicehash.com' <159.122.29.199> port 3353 ETH: Stratum - Connected (daggerhashimoto.eu.nicehash.com:3353) GPU0 t=55C fan=13% Socket was closed remotely (by pool) ETH: Job timeout, disconnect, retry in 20 sec...

this lasted about 10 minutes, followed by: ETH: Stratum - connecting to 'daggerhashimoto.eu.nicehash.com' <159.122.29.199> port 3353 ETH: Stratum - Connected (daggerhashimoto.eu.nicehash.com:3353) ETH: Authorized Setting DAG epoch #7... Setting DAG epoch #7 for GPU0 GPU0 DAG creation time - 3724 ms Setting DAG epoch #7 for GPU0 done GPU0 t=60C fan=20% ETH: 01/31/18-12:55:20 - New job from daggerhashimoto.eu.nicehash.com:3353 (FAILOVER 2)

And since then it's been using this failover2.

Has Nicehash changed anything for the better?

AlexVirlan commented 6 years ago

@xberg about what you said "Or worse: I could connect my laptop to your wallet and block you? Nonsense.". I do have some theory about the problem, hear me out.

So, you get blocked (on Europe) and you CAN mine on another pool (also known as "server" or "service location" in NHM). But you get blocked on all of the pools eventually and you need to wait for some time (I think that is around 60 minutes). The big question here is what information do they use to block a specific machine. I think that the BTC Address must be involved so they can track it trough the platform and pools. But they can also do a fingerprint (or unique ID) for every machine (I used this technique for licensing on other projects in the past). For example: Some_Hardware_Info + Some_Software_Info + Wallet_Address = The_Fingerprint (or even include some network info or the public IP) Doing this you can solve the "I could connect my laptop to your wallet and block you?" problem, because they can block a specific connection, on a specific machine, with a specific wallet address.

I didn't have time to look around in the NHM source code yet, but I will do this as soon as I can. If everyone saw something, please tell me.

xberg commented 6 years ago

Again I was connected to FAILOVER 1 after being disconnected for a few minutes, so everything seems to be working fine now. The error I had was: Socket was closed remotely by pool.

But in a minute or 2 I was connecting to the failover pool.

I will continue monitoring this but it's looking promising.

gagstheminer commented 6 years ago

I guess this problem has not been resolved yet.. I used to get this socket error, but it would go away for a while if I restarted my router / modem. Thinking it is a soft ban from the service provider, I switched to another service provider but the problem persists...

gjta commented 6 years ago

Is anyone still having this problem? I am new to nicehash, and meanwhile my gpu#1 is running fine getting 65.273mh/s, my cpu1 with cryptonight is not running at all and im also getting the error msg after trying to connect:

"socket error - send error: an established connection was aborted by the software in your host machine"

Any update or information on how this can be fixed would be much appreciated, many thanks in advance.

AlexVirlan commented 6 years ago

@gjta Mine using ONLY your GPU and see what happens. Then post a feedback here if you want.

gjta commented 6 years ago

@AAv-Soft okay so I turned off the CPU, and clicked start on NH again. GPU works fine, and only one window opened once I clicked start which shows "core l algorithm 'equihash' total speed: 678,331729 h/s" etc etc,

Fyi my current CPU is an intel i7 8700k coffee lake 3.7ghz, if that helps.

emerzon commented 6 years ago

TL;DR: Don't worry about this error if your hash rate is not super low.

TL;DR2: Slow clients are not supported by nicehash.

Nicehash imposes a 10 min timeout on each connection. For Cryptonight on CPU you will normally everyday have over 10 mins without any communication to server due to the high difficulty currently. When required your client will establish a new connection and life goes on. The problem is if your hash rate is too low, it means that you will reach timeout very often, thus, triggering a soft ban on your IP.

Em seg, 12 de mar de 2018 13:29, gjta notifications@github.com escreveu:

@AAv-Soft https://github.com/aav-soft okay so I turned off the CPU, and clicked start on NH again. GPU works fine, and only one window opened once I clicked start which shows "core l algorithm 'equihash' total speed: 678,331729 h/s" etc etc,

Fyi my current CPU is an intel i7 8700k coffee lake 3.7ghz, if that helps.

— 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-372293240, or mute the thread https://github.com/notifications/unsubscribe-auth/AZkvdxB7EH3q3hJwDBab8r-KnE-BVgUpks5tdmoqgaJpZM4N9DJF .

gjta commented 6 years ago

@emerzon sir can you kindly explain that in plain english, this my first day starting this journey, are you saying that my hash rate is too slow? hence the timeout i am getting?

AlexVirlan commented 6 years ago

@gjta

can you kindly explain that in plain english

The mining difficulty is very high, so CPUs can't mine as fast as GPUs (or ASIC miners). And if you mine on your CPU, you (most likely) won't be able to submit any hashes faster than 10 minutes, so NH will give you a "time out".

Read more about this by "googleing" around.

emerzon commented 6 years ago

This i​s specific to Cryptonight. Modern CPU will most of the times be able to send a share in less than 10 minutes, but not always. So in these cases you may see a time-out, but your client will eventually recover. Now if your CPU is too slow and will always send shares in periods greater than 10 minutes, you will get a soft ban.

2018-03-12 13:46 GMT+01:00 AAv.Soft notifications@github.com:

@gjta https://github.com/gjta

can you kindly explain that in plain english

The mining difficulty is very high, so CPUs can't mine as fast as GPUs (or ASIC miners). And it you mine on your CPU, you (most likely) won't be able to submit any hashes faster than 10 minutes, so NH will give you a "time out".

Read more about this by "googleing" around.

— 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-372297412, or mute the thread https://github.com/notifications/unsubscribe-auth/AZkvd67IID9LtHsekZ_vGOrkxjrm1c68ks5tdm4VgaJpZM4N9DJF .

gjta commented 6 years ago

@AAv-Soft thank you sir for the clarification. Is there a way around this? so it can be resolved and I am able to run this algorithm?

@emerzon many thanks for that, that makes more sense.

gjta commented 6 years ago

@AAv-Soft thank you sir for the clarification. Is there a way around this? so it can be resolved and I am able to run this algorithm?

AlexVirlan commented 6 years ago

@gjta If you have a GPU, don't worry about mining Cryptonight with your CPU. The GPU is much more faster. For now, there's no way around this, since the NH servers are programmed to time-out the slow miners. Stay subscribed to this page and you will get notified about possible changes.