ERROR: connecting to full node (libp2p): no good addresses #9415
-
I am having trouble spinning up my miner due to possible connectivity issue with the full node API. Lotus miner config
Full node config
$FULLNODE_API_INFO
Running the miner
Anything immediately jump out as obvious? The miner is obviously communicating with the full node API to get the chain state before outputting the error. So the issue must be with the listen/announce addresses in the full node Libp2p section, whose ports (6671, 6672) are properly forwarded by the gateway to the indicated private IP of the full node (192.168.1.31). Additionally, the miner libp2p port (6672) is forwarded to the miner private IP, so I am lost on the issue (I have had this setup working before on a previous mainnet version earlier in the year). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Try to remove |
Beta Was this translation helpful? Give feedback.
Try to remove
http
fromLibp2p.AnnounceAddresses
from daemon config and restart the daemon. This should allow miner to connect with the daemon over libp2p and add the protected peer.