When hostname is set to "0.0.0.0", cluster seed node can't be connected, why?

To config my Akka cluster, I’d like to use “0.0.0.0” to config hostname to avoid bother what specific local IP address is. But when I set hostname to “0.0.0.0” and set seed-nodes pointing to a local IP address, like the following screenshot shows:
image

then I got the following error output, showing seed node can’t be connected:

Dropping Handshake Request from [akka://director-engine@0.0.0.0:2551#-4630113785883271967] addressed to unknown local address [akka://director-engine@10.34.19.162:2551]. Local address is [akka://director-engine@0.0.0.0:2551]. Check that the sending system uses the same address to contact recipient system as defined in the ‘akka.remote.artery.canonical.hostname’ of the recipient system.

It only works if I use specific IP address in hostname as follows:
image

Though it works, it’s very tedious as I have to use different config file for different cluster nodes. I’d like to use “0.0.0.0” to avoid it. Can I?

Thanks!

The canonical address and port is used in messages and actor refs so it needs to be an address that can be used to reach the node from any other node in the cluster. 0.0.0.0 is a wildcard which means (among other things depending on context) all the interfaces of this machine, it cannot be used to reach it from the rest of the network.

Note that you can use environment variables in the config.