search

YoRyan / nuxhash

A NiceHash cryptocurrency mining client for Linux.
GNU General Public License v3.0
264 stars 164 forks source link

SSL: CERTIFICATE_VERIFY_FAILED #76

Open alexberian opened 3 years ago

alexberian commented 3 years ago

I am running nuxhashd on an nvidia-docker container on Linux mint 20. Benchmarking appears to work fine, but when it is done and tries to actually mine, I get the following outputs from nuxhashd -v --show-mining

root@c11c8e7bd385:/# nuxhashd -v --show-mining
nuxhashd initial setup
Wallet address: CENSORED_FOR_PRIVACY
Worker name: leftcomp
Region (eu/usa/hk/jp/in/br): usa

CUDA device: GeForce RTX 2060 (GPU-2688049b-5a38-fe14-279b-71f07226f080)
  excavator_cryptonightV7: 558.04  H/s
  excavator_keccak: 835.19 MH/s
  excavator_decred:   2.96 GH/s
  excavator_daggerhashimoto_pascal:  17.66 MH/s, 988.93 MH/s
  excavator_x16r:   8.35 MH/s
  excavator_pascal:   1.40 GH/s
  excavator_daggerhashimoto_decred:  27.11 MH/s, 867.57 MH/s
  excavator_lyra2z:   2.67 MH/s
  excavator_equihash:   0.00  H/s
  excavator_daggerhashimoto:  27.42 MH/s
  excavator_lyra2rev2:  53.02 MH/s
  excavator_cryptonightV8: 552.29  H/s
  excavator_blake2s:   4.52 GH/s
  excavator_neoscrypt:   1.01 MH/s
2021-02-17 01:34:38,356 INFO: Querying NiceHash for miner connection information...
2021-02-17 01:34:38,364 DEBUG: Starting new HTTPS connection (1): api2.nicehash.com:443
2021-02-17 01:34:38,423 WARNING: NiceHash stats: HTTPSConnectionPool(host='api2.nicehash.com', port=443): Max retries exceeded with url: /main/api/v2/public/simplemultialgo/info/ (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),)), retrying in 5 seconds
2021-02-17 01:34:43,433 DEBUG: Starting new HTTPS connection (1): api2.nicehash.com:443
2021-02-17 01:34:43,492 WARNING: NiceHash stats: HTTPSConnectionPool(host='api2.nicehash.com', port=443): Max retries exceeded with url: /main/api/v2/public/simplemultialgo/info/ (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),)), retrying in 5 seconds
2021-02-17 01:34:48,503 DEBUG: Starting new HTTPS connection (1): api2.nicehash.com:443
2021-02-17 01:34:48,558 WARNING: NiceHash stats: HTTPSConnectionPool(host='api2.nicehash.com', port=443): Max retries exceeded with url: /main/api/v2/public/simplemultialgo/info/ (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),)), retrying in 5 seconds
2021-02-17 01:34:53,568 DEBUG: Starting new HTTPS connection (1): api2.nicehash.com:443
2021-02-17 01:34:53,623 WARNING: NiceHash stats: HTTPSConnectionPool(host='api2.nicehash.com', port=443): Max retries exceeded with url: /main/api/v2/public/simplemultialgo/info/ (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),)), retrying in 5 seconds
2021-02-17 01:34:58,634 DEBUG: Starting new HTTPS connection (1): api2.nicehash.com:443
2021-02-17 01:34:58,689 WARNING: NiceHash stats: HTTPSConnectionPool(host='api2.nicehash.com', port=443): Max retries exceeded with url: /main/api/v2/public/simplemultialgo/info/ (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),)), retrying in 5 seconds
2021-02-17 01:35:03,697 DEBUG: Starting new HTTPS connection (1): api2.nicehash.com:443
2021-02-17 01:35:03,754 WARNING: NiceHash stats: HTTPSConnectionPool(host='api2.nicehash.com', port=443): Max retries exceeded with url: /main/api/v2/public/simplemultialgo/info/ (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),)), retrying in 5 seconds
Terminated

The Terminated only shows up because I killed the process manually. It would keep repeating the same error otherwise, and I cannot stop it with Ctrl-C.

I have a docker container set up the same way working just fine with nuxhashd on my Ubuntu 16.04 machine. It is also worth noting that this error occurs even \emph{outside} the docker container, which leads me to believe that it is not the docker container's fault.

Thanks for your time!