8

I already have my node up and running using docker images with default configuration, so how can i change it to run in private node so that I can run few sentry nodes connected to public network and then connect my private node to sentry nodes to avoid exposing my baker node publically.

I already know this, so I need a solution using docker images.

Improve this question
6

When you launch the docker node with ./mainnet.sh start, you can add extra arguments such as --private-mode --peer AAA.BBB.CCC.DDD:PORT (you probably need to specify --peer to connect your private node to your public node).

Improve this answer
8
  • Thanks for the information. I already have my node running as public node. Now if i stop the node container and then start it with private node flag, will there be any side effect to my current setup (like connection failure with previously connected node or some other unexpected error) OR i should be good to go?
    – Sachin Tomar
    Feb 4 '19 at 12:43
  • 1
    It should work, but you will probably notice some connections being rejected. That's not a problem, disregard them.
    – lefessan
    Feb 4 '19 at 18:13
  • I think there is some syntax error in above configuration options. it should be --peer=AAA.BBB.CCC.DDD:PORT . An = instead of <space>
    – Sachin Tomar
    Feb 5 '19 at 18:12
  • I used this command ./mainnet.sh start --private-mode --no-bootstrap-peers --bootstrap-threshold=1 --connections 1 --peer <public-node-ip> But all i get is incoming connections rejected but my node is not getting connected to my public node.
    – Sachin Tomar
    Feb 14 '19 at 7:29
  • Did you also specify the port, ie ˋ—peer host:port` ? Note that, if the public node is already full, it will reject your connection.
    – lefessan
    Feb 14 '19 at 17:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.