Running a group of servers in a cluster is considerably more complicated than a single server, particularly when first configuring the cluster. This is because configuration changes are being distributed to all servers in the cluster.
By default each secondary server's IP filtering rules only permit connections from localhost. A rule must be added to permit the primary server to contact them. This requires connecting locally to each secondary server, and opening the Admin Site configuration (in Sites panel by selecting "Show system users/folders/sites" in the Options menu at the bottom left of the window). Add an IP Filter rule that allows the primary server to connect to the secondary.
There are two simple things that can be tried to resolve any problems. If a secondary is out of date and cannot be synchronized, the right mouse button click menu item"Force configuration update" can be used to force a secondary server to have its configuration overwritten using the configuration of the primary. An alternative approach is to simply remove the server from the cluster and re-add it.
If problems are experienced that cannot be resolved by the above, it will be necessary to look at the log files that are produced in the Monitoring panel. If possible, ensure that logging is set to the Debug level, as shown below:
Ensure that all log files from every server in the cluster are sent to us. Please ensure that they are zipped and that it is clear which machine each group of logs comes from. A simple way to do this is to copy each group of files to a directory that has the name of the server, and zip up all these directories into the one zip file.