You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After adding a plot NFT, the pool info cannot be obtained. Errors of this sort appear in debug.log once per minute:
2021-07-09T02:10:40.203 farmer chia.farmer.farmer : ERROR Exception in GET /pool_info https://na1.pool.space, Cannot connect to host na1.pool.space:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1131)')]
Moreover, the difficulty and authentication_token_timeout for the plot fail to be set (warnings spam debug.log.)
To Reproduce
Steps to reproduce the behavior:
Either add a plot NFT in the GUI client, or chia plotnft create -s pool -u <pool>.
If added in the GUI client, errors will begin to appear in debug.log. If added from the command line, the error will be visible immediately.
Desktop
OS: linux
OS Version/Flavor: arch linux, fully up to date
Chia version: 1.2.0, from the unofficial AUR package.
Apologies, but I'm unable to build the source so I can't test this. But I'm guessing it ought to be done regardless (why else is mozilla-ca in the source tree?)
The text was updated successfully, but these errors were encountered:
Describe the bug
After adding a plot NFT, the pool info cannot be obtained. Errors of this sort appear in
debug.log
once per minute:Moreover, the difficulty and authentication_token_timeout for the plot fail to be set (warnings spam
debug.log
.)To Reproduce
Steps to reproduce the behavior:
chia plotnft create -s pool -u <pool>
.debug.log
. If added from the command line, the error will be visible immediately.Desktop
Proposed solution
In _pool_get_pool_info(), pass a custom SSL context to aiohttp.ClientSession, as is done in fetch() in server.py.
Apologies, but I'm unable to build the source so I can't test this. But I'm guessing it ought to be done regardless (why else is mozilla-ca in the source tree?)
The text was updated successfully, but these errors were encountered: