Thanks a lot!
Now is ok.

From EUROPE market: { "success": true, "logs": [ { "timestamp": "2019-10-04T15:41:26.316Z", "level": "INFO", "poolVerificationMessage": "POOL_HOST_RESOLVED_TO_IP", "params": { "HOST": "prohashing...

Here is raw data from NH pool_verificator From USA market: { "success": false, "logs": [ { "timestamp": "2019-10-04T15:18:26.047Z", "level": "INFO", "poolVerificationMessage": "POOL_HOST_RESOLVED_TO_IP", "params&quo...

I have no ideas yet, but I have some information. Pool verification from NH to prohashing.com:3448 returns different result check for EUROPE and USA markets. Pool verification from NH qubit server for EUROPE market. NH EUROPE server IP address: 35.233.15.36 : root@ubuntu:~/nicehash/_pool_verificator...

I have just created 14 new test orders.
Four started with normal difficulty=4, and the remaining 10 are in dead status due to low pool difficulty.


https://pasteboard.co/IAqaYap.png

Steve Sokolowski wrote: ↑Thu Oct 03, 2019 8:43 am The URL is still unable to be contacted from the mining servers.

Can you try this URL?

https://api2.nicehash.com/main/api/v2/m ... lgorithms/

Verification process from different NH regions: root@ubuntu:~/nicehash/_pool_verificator$ ./pool_verify.sh USA Success: false Pool host prohashing.com resolved to IP 50.225.198.65 Connecting to Stratum proxy for region: USA Selected mining algorithm: Qubit Sending mining subscribe request Sending lo...

Nicehash uses new API for the new platform. Old platform with v1 API does not work since 4 august 2019 I suppose you must change all difficulty check for all algorithms you use. Here is the documentation for API v2: https://docs.nicehash.com/ wget https://api2.nicehash.com/main/api/v2/mining/algorit...

I have some new information for you.
New order successfully started if d=4 parameter is added to the password field: (a=qubit,d=4)
This indicates a problem with minimal difficulty settings on your side.

Hello, Steve!

Nothing changed