blockchain is being created with the private IP not the public IP

Question

Hello

when I install multichain on VM ( I tried it with both Microsoft Azure and Google cloud ), then create my blockchain and then create the genesis block, the blockchain is being created with the private IP for the virtual machine, not the static public IP of the virtual machine, while the VM already has a static public IP.

when I get blockchain info it shows like this

    "nodeaddress" : "chain1@10.128.0.2:6467",

This issue makes troubles when creating another node and trying to connect.

how can I let the blockchain using the static public IP ? in another way, how to change this IP setting in the blockchain info?

thanks

Answer 1

The nodeaddress you see in getinfo contains MultiChain's best guess as to its most useful external IP address. However it will accept incoming connections on any IP address for the server on which it's running. When you first run MultiChain you should see multiple node addresses shown on the command line, if the server has more than one IP address.

Comments

I have a similar but a little different problem. I set up a network with a couple network nodes.
Some of them connect twice using both the public AND private ip. How can I prevent that? Under "Node Information"/"Connected Nodes" it shows me the node is connected but its connected two times, using both the public and private ip. Thank you

---

First it's not a problem if there are duplicate connections between nodes. Second if you want to prevent this, you can use the bind runtime parameter which tells the node to listen on a specific IP address only.