Tried updating to 1.9.1.5 from 1.9.1.4. NHML doesn't seem to be able to connect to internet.
Tried turning off all firewalls - no result.
Had to roll back to 1.9.1.4


Same thing happening, just downloaded new version and getting same error
same here on 3 different computers
2 X windows 10 1809
1 X windows server 2016
Same here and I don't think it's version related as I've kept 0.23 and same socket exception 1015 thrown.
(can check this by enabling the debug console)
Also did a quick reinstall on another pc same thing.
Changed the internet connection to an entire new connection same thing.
One thing to mention is that the app downloads it's third party miners .. just can't access the servers (I think) to check the wallet status / do benchmarks / or mine obviously.
-this is what's shown in the console when the error message is thrown
-and this is what happens after choosing to continue even if no connection
Please let us know if the issue it's from the client app side or your servers etc. So we know to just wait until it is fixed instead of breaking our heads trying to find a go around.
Thanks and keep up the good work, nicehash team!
have the same issue at windows7 box
logs say about tls handshake error
looks as server want tls1.1 but client can tls1.2 only
have the same issue at windows7
looks as server want tls1.1 but client can tls1.2 only
What does this mean, if I may ask, what's tls? - if you check the console says something about a handshake :)
"An error has occurred during a TLS handshake. ---> System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> System.ComponentModel.Win32Exception: The function requested is not supported" - from my printscreens
Also changing the service location doesn't help!
(sorry I'm a noob in mining and coding so guess I'm just trying to point all the facts out maybe some of them help the most advanced of you)
However I still think they've changed something to the server side not on the client since the 1.9.0.23 version behaves the same.
Maybe they know of the issue so we should just give them time to resolve it.
same here
Thread opened on nicehash reddit page
[https://www.reddit.com/r/NiceHash/comments/c6p0bg/no_connection/]
Same problem here.... Older version working....
I'm getting this issue on 1.9.0.21, 1.9.0.23, 1.9.1.5, and Nicehash OS. Tried different methods of connections, even ran it on a virtual machine just to see if it was all my machines playing up.
It's a connection error. Not sure how some people are getting lucky on older versions as I've tried the same things. :/
Hoping the NiceHash staff aren't asleep!
I'm getting this issue on 1.9.0.21, 1.9.0.23, 1.9.1.5, and Nicehash OS. Tried different methods of connections, even ran it on a virtual machine just to see if it was all my machines playing up.
It's a connection error. Not sure how some people are getting lucky on older versions as I've tried the same things. :/
Weird thing .... seems the versions that it works on it's random - mine works fine on 1.9.0.21 so back to mining on that until this gets resolved
PS: also most of the people have done a reset after updating to the new version, I accidentally turned off the wall socket before I managed to update and the issued first appeard on the old version (1.9.0.23) immediately after the restart.
PS: ### I confirm version 1.9.0.21 is stable (checked the wallet statistics as well - the client is communicating with the server so it's up). You can copy the benchmarks over to the .0.21 version and start mining there took me 2 mins to get transition so this is the solution for me ... for the moment at least
it now works on my side not sure why.
I have tested many things, but now I am running without any registry tweaks and it connects
it now works on my side not sure why.
I have tested many things, but now I am running without any registry tweaks and it connects
Yep confirmed here as well 1.9.1.15 works for me as well... will stick to the 0.21 till things are confirmed in the morning by the community.
Reddit comment from nicehash. Was a problem on the server side. Works ok for me now (1.9.1.5)
Yep, confirm, now all is working. Definitely server side problem. I wonder how are they missed this in QA )))
Still not connecting
Most helpful comment
have the same issue at windows7 box
logs say about tls handshake error
looks as server want tls1.1 but client can tls1.2 only