Nicehashminer: Can't get profitability data

[isazon4ik]

A few days on all rigs this problem started. Tried different versions - from 1.8.0.2 to 1.8.2.0 Pre, the problem is present everywhere. The checkbox "ignore the loss of the Internet connection" is removed, as seen in the screenshot.

[Munchies55]

Im having the same issue, auto-start mining brings up the same "cant get profitability data" error and wont start mining, but if i close the error and click start it will start mining with no issue. version: 1.8.1.4

[ShortCircuit1]

I am having the same problem. When 1.8.. not work, 1.7.. working without problem

[pet1777798]

один день проработал и все

[isazon4ik]

@DillonN man, it's important

[Picoskop]

@isazon4ik I am having the same issue but first i get this error

after i press yes to continue and i press start i get this one

The problem is my internet connection is working perfect (i have internet access) but from some reason i can't make connection to nicehash servers. And i can't even do benchmarks. Anyone has any idea why? Am i banned from nicehash servers? Or something else? But i never even connected to them in the first place :(
Claymore for ethereum is working perfectly but i wanted to switch to nicehash to check it out and i am unable to connect but i can download miners from some reason (unknown aswell). Btw i tryed to turn off IPV6 and still the same issue.
Can someone please help with what should i try next?
P.S. i am using nicehash 1.8.1.5 and have tryed it on 1.8.1.4 and 1.8.2.0. Everywhere is the same error.

[DillonN]

NHML requires a connection to NH servers to mine or benchmark. Many things can cause it to not connect, like server problems, firewall, ISP problems, etc. None of these can be fixed from NHML

@Munchies55 NHML constantly retries to connect, it's likely here it was able to connect before you clicked OK and so it mined properly. This is something I can look into improving - a more intuitive way to notify there is no connection that goes away if the problem is fixed, especially when automining

[isazon4ik]

@DillonN Dude, the NHML is started from the BAT file, how to press the OK button? Do something already, tired of constantly going to the rigs and pressing this OK button. Because of this problem, I already lost 24h revenue. It's easier then to stop using the NHML and go to the pools.

[ShortCircuit1]

why 1.7.6.3 work okey? 1.8 not okey. why ping, teamview, mining work ok? internet lost? NO!

[ShortCircuit1]

I think NHML must starting "without internet", may be start with randomly or last algo, but NHML can not stopping with window!!!!

[Munchies55]

@DillonN That would be great, i have only ever gotten the, "cant get profitablity data" error never the "no internet connection" one,

I have also tried disabling IPv6 which didnt help and also added outbound and inbound firewall rules for the NHML program, which also didnt fix the problem, neither did running as administrator, it always comes up whenever i have autostart mining on.

[aeratus]

Hello colleagues!!!
At me too produces an error.
It is not possible to get NiceHash profitability data. If you are connected to the Internet, try again later. On versions 1.8.1.1; 1.8.1.3; 1.8.1.5. This is for those that I worked.

[DmitryDMR]

@DillonN can you disable "cant get profitablity data" error window and run mining with last more profitable algos? i get this error very, very often

[Spritor]

same issue with both 1.8.1.5 and 1.8.2.0 pre. anyone found any solution yet ?

[adri76]

I have the same problem, I can only use 1.7.5.13, all the newer versions has the "no internet connection" problem. I have tried everything.
1.7.5.13 works perfectly and I pinged all the servers no problem, but every version from 1.8..... does not work.

[chelnydiablo]

+1 достала ошибка. в день по нескольку раз.

14.11.2017 18:17:17|Debug|WebSocket.sendHttpRequest|A response to this request:
HTTP/1.1 503 Service Temporarily Unavailable
Date: Tue, 14 Nov 2017 15:17:18 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=d47eb7675ab682a56f0917aadeeaf7208
1510672638; expires=Wed, 14-Nov-18 15:17:18 GMT; path=/; domain=.nicehash.com; H
ttpOnly
Server: cloudflare-nginx
CF-RAY: 3bdaefd948368fe7-DME
14.11.2017 18:17:17|Fatal|WebSocket.connect|Not a WebSocket handshake response.
14.11.2017 18:17:17|Debug|WebSocket.closeHandshake|Was clean?: False
sent: False
received: False
[18:17:18] [SOCKET] Connection closed: An error has occurred while connecting.
[18:17:19] [SOCKET] Socket connection unsuccessfull, will try again on next devi
ce update (1min)

в логах:

[

2017-11-14 18:15:20] [INFO] [ComputeDeviceManager.Query] QueryCudaDevices END
[2017-11-14 18:15:20] [INFO] [ComputeDeviceManager.Query] Skipping AMD device detection, settings set to disabled
[2017-11-14 18:15:20] [INFO] [ComputeDeviceManager.Query] Cuda NVIDIA/CUDA device count GOOD
[2017-11-14 18:15:20] [INFO] [ComputeDeviceManager.Query] AMD GPU device count GOOD
[2017-11-14 18:15:21] [INFO] [ComputeDeviceManager.Query] virtual memory size GOOD
[2017-11-14 18:15:21] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:21] [INFO] [SOCKET] Attempting reconnect in 0 seconds
[2017-11-14 18:15:21] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:22] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:24] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:25] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:26] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:27] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:29] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:30] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:31] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:33] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:34] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:35] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:36] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:38] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:39] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:40] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:41] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:43] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:44] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:45] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:15:46] [INFO] [NICEHASH] Bitcoin rate get
[2017-11-14 18:15:47] [INFO] [NICEHASH] Current Bitcoin rate: 6642.20
[2017-11-14 18:15:47] [INFO] [NICEHASH] Setting environment variables
[2017-11-14 18:15:47] [INFO] [NICEHASH] Trying to enable/disable Windows error reporting
[2017-11-14 18:15:47] [INFO] [NICEHASH] Current DontShowUI value: 1
[2017-11-14 18:15:47] [INFO] [NICEHASH] nvidiasetp0state returned error code: 3
[2017-11-14 18:16:46] [INFO] [SOCKET] Attempting reconnect in 26 seconds
[2017-11-14 18:17:12] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:17:14] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:17:15] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:17:16] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:17:18] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:17:19] [INFO] [SOCKET] Socket connection unsuccessfull, will try again on next device update (1min)
[2017-11-14 18:18:18] [INFO] [SOCKET] Attempting reconnect in 26 seconds
[2017-11-14 18:18:45] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:18:46] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:18:46] [INFO] [SOCKET] Socket connection unsuccessfull, will try again on next device update (1min)
[2017-11-14 18:18:47] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:18:48] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:18:50] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:18:51] [INFO] [SOCKET] Socket connection unsuccessfull, will try again on next device update (1min)
[2017-11-14 18:19:50] [INFO] [SOCKET] Attempting reconnect in 22 seconds
[2017-11-14 18:20:12] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:20:14] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:20:15] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:20:16] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:20:17] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:20:19] [INFO] [SOCKET] Socket connection unsuccessfull, will try again on next device update (1min)
[2017-11-14 18:20:46] [INFO] [SOCKET] Attempting reconnect in 20 seconds
[2017-11-14 18:21:06] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:21:08] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:21:09] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:21:10] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:21:11] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:21:13] [INFO] [SOCKET] Socket connection unsuccessfull, will try again on next device update (1min)
[2017-11-14 18:21:46] [INFO] [SOCKET] Attempting reconnect in 21 seconds
[2017-11-14 18:22:07] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:22:09] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:22:10] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:22:11] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:22:12] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:22:14] [INFO] [SOCKET] Socket connection unsuccessfull, will try again on next device update (1min)
[2017-11-14 18:22:46] [INFO] [SOCKET] Attempting reconnect in 16 seconds
[2017-11-14 18:23:02] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:23:04] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:23:05] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:23:06] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:23:07] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:23:09] [INFO] [SOCKET] Socket connection unsuccessfull, will try again on next device update (1min)
[2017-11-14 18:23:46] [INFO] [SOCKET] Attempting reconnect in 29 seconds
[2017-11-14 18:24:15] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:24:17] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:24:18] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:24:19] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:24:21] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:24:22] [INFO] [SOCKET] Socket connection unsuccessfull, will try again on next device update (1min)
[2017-11-14 18:24:46] [INFO] [SOCKET] Attempting reconnect in 20 seconds
[2017-11-14 18:25:06] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:25:08] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:25:09] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:25:10] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:25:12] [INFO] [SOCKET] Connection closed: An error has occurred while connecting.
[2017-11-14 18:25:13] [INFO] [SOCKET] Socket connection unsuccessfull, will try again on next device update (1min)
[2017-11-14 18:25:46] [INFO] [SOCKET] Attempting reconnect in 11 seconds

[dstarcev]

Cloudflare is randomly banning websocket requests to https://api.nicehash.com/v2/nhm

Cloudflare произвольно блокирует соединение вебсокетов https://api.nicehash.com/v2/nhm

[danialmoghaddam]

Come on guys! It is so obvious that there is a problem. Have it fixed in the next version please. This is costing us some loss!

[Sav87]

It is necessary to change the algorithm of autorun, issuing messages and receiving data from the Internet.

[ShortCircuit1]

I'm tired of this error and switched to Linux. now everything works like a clock
я устал от этой ошибки и перешел на линукс. теперь все работает как часы

[Sav87]

add Pull request #625

[xtrime-ru]

@Sav87 сделал исправления для этой ошибки, их одобрили, но пока не включили в релиз.
Пока ждем релиз я скомпилировал его исправления:
https://github.com/xtrime-ru/NiceHashMinerLegacy-SMA-FIX/releases

[jesteroi]

I got the same problem with 1.8.1.8 not getting profitability data.

I checked my time sync and I was out by 1600ms. So I updated my time sync a couple times so it was down to within +/- 5ms and then ran NHLM again and it worked.

Can't say that this is what solved the problem for sure, but my NHLM is working again.

I used this: http://www.timesynctool.com/