Interface IP is incorrect and not found while starting Hazelcast in a dockerized environment for Confluence Data Center

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Data Center Only - This article only applies to Atlassian products on the data center platform.


While starting up Confluence Synchrony (collaborative editing) in a dockerized environment, you get the following error in the atlassian-synchrony.log:

ERROR [main] [com.hazelcast.instance.AddressPicker] [LOCAL] [confluence-<name>-Synchrony] [3.11.4] Hazelcast CANNOT start on this node. No matching network interface found.

When you view the <Confluence local home>/confluence.cfg.xml file, the network interface is set correctly under the _<confluence.cluster.interface>_ property, however the IP address of the interface is incorrect.


Confluence Data Center 7.1.1



The Hazelcast service cannot find the IP or interface when starting and fails to start the synchrony service.


Docker uses 'Virtual Networks', networks that are independent and outside the scope of the host machine network interface unless setup otherwise. Virtual networks by default use the bridged driver.


If you plan on using the host machines network interface, switch the virtual network on docker to use the host driver.

Last modified on Jan 17, 2020

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.