Closed zengzengzenghuy closed 1 year ago
Feedback from Dappnode team: Setting static peers and adding bootnodes for Nethermind client will solve the issue for now:
--Network.Bootnodes="<enode>,<enode>,..."
--Discovery.Bootnodes="<enode>,<enode>,..."
--Network.StaticPeers="<enode>,<enode>,..."
replace the enode with enode from bootnodes_execution.yaml
Closing issue if there are no further complaints
What
Starting from Feb 17, some of the users running on Dappnode are facing several issues:
There is no issue reported from users who run Nethermind on bare metal.
Consensus client(Teku) on Dappnode has no issue finding peers.
User who configures bootnode manually is able to find 3 peers on Nethermind.
Potential reason: