After network host accept the new node and store in whitepaper:
The new node occur error message as below:
{"level":"info","msg":"Node Manager listening on :22004...","time":"2021-05-20T08:01:47Z"}
Fatal: Raft-based consensus requires either (1) an initial peers list (in static-nodes.json) including this enode hash (e6cbf3b626d51e5848a15e89317dee213525319e79045b571d7f21ecdbc8fc64), or (2) the flag --raftjoinexisting RAFT_ID, where RAFT_ID has been issued by an existing cluster member calling `raft.addPeer(ENODE_ID)` with an enode ID containing this node's enode hash.
rpc call eth_coinbase() on http://localhost:22000: Post "http://localhost:22000": dial tcp 127.0.0.1:22000: connect: connection refused
rpc call eth_coinbase() on http://localhost:22000: Post "http://localhost:22000": dial tcp 127.0.0.1:22000: connect: connection refused
rpc call eth_coinbase() on http://localhost:22000: Post "http://localhost:22000": dial tcp 127.0.0.1:22000: connect: connection refused
rpc call eth_coinbase() on http://localhost:22000: Post "http://localhost:22000": dial tcp 127.0.0.1:22000: connect: connection refused
After network host accept the new node and store in whitepaper:![image](https://user-images.githubusercontent.com/185872/118950886-2eb3e180-b98d-11eb-999e-58f48a84b537.png)
The new node occur error message as below: