My private node is not connecting to the peer mentioned in the start command

Question

I used below command to start my private node:

./mainnet.sh start --private-mode --no-bootstrap-peers --bootstrap-threshold=1 --connections 1 --peer=`public_node_ip`:9732

My public_node is already running with connections to its peers.

Now my private node logs just shows "incoming connection rejected due to untrusted source" and my private node just does not connect to the public node.

I even checked the config.json file, my public_node_ip was there against "bootstrapped-peers" key.

What else I should do to connect my private node to my public node?

Answer 1

The incoming connection rejected due to untrusted source is most certainly due to a previous non-private run on the same IP. Your IP is known as a potential peer, so other nodes try to connect. It is not a problem, your node will simply reject these connections.

Maybe your public node was saturated. It is important that your public node also has your private node in its trusted peers. So your public node should also be run with --peer=private_node_ip:port or with your private node IP in the config.json file.

It is very important that the public node consider the private node as trusted. If not, the private node might be kicked during connections maintenance phase.