search

Chia-Network / chia-blockchain

Chia blockchain python implementation (full node, farmer, harvester, timelord, and wallet)
Apache License 2.0
10.83k stars 2.02k forks source link

[BUG] Mac-User "Current Difficullty" not show in pool section #7269

Closed Manintorn closed 3 years ago

Manintorn commented 3 years ago

1) Updated and synced Chia 1.2.0 both Windows and Macs 2) Used Madmax v0.1.1 through Windows 3) Created pool url on Mac 4) Add finished 19 Plots on Mac 5) No Current Difficulty shown 6) Was trying to add another pool, same problem

213184334_960689717808048_6025250632343297685_n

Manintorn commented 3 years ago

Windows has no problem with the same 19 plots

212409664_231828675284346_741452962309616133_n

loppefaaret commented 3 years ago

could you tell us what macos version - and if 11.x BigSur, is it the m1 arm based machine ?

korawong commented 3 years ago

i have same problem, macos version:big sur 11.4,macbook Air M1

Manintorn commented 3 years ago

I've got 3 Macs with the same lan line 1st Mac Mini 2020 with 11.4 BigSur - "Current Difficulty" not shown 2nd Mac Mini 2012 with 10.15.7 Catalina - "Current Difficulty" not shown 3rd Macbook Air with 11.4 BigSur - Work just fine

1 2 3

could you tell us what macos version - and if 11.x BigSur, is it the m1 arm based machine ?

Portago9 commented 3 years ago

I also have this issue on Win10

Hvataj

Tried adding on a diffrent, new wallet, but same result, not adding the difficulty and not farming...

Debug saying:

ERROR Exception in GET /pool_info https://eu1.pool.space, [ASN1] nested asn1 error (_ssl.c:4174) 2021-07-09T13:54:23.532 farmer chia.farmer.farmer : WARNING No pool specific authentication_token_timeout has been set for 35871076c61e54e5dcd7258ef79f1edc084df65c9759e1ea9579e668f2785e4b, check communication with the pool.

WARNING No pool specific difficulty has been set for 35871076c61e54e5dcd7258ef79f1edc084df65c9759e1ea9579e668f2785e4b, check communication with the pool, skipping this signage point, pool: https://eu1.pool.space

loppefaaret commented 3 years ago

ahh, this might stem from a CA certificate problem we have already solved, and is to be included in 1.2.1 release

Manintorn commented 3 years ago

ahh, this might stem from a CA certificate problem we have already solved, and is to be included in 1.2.1 release

sound good will wait for new release Cheers