Confluence offline editor
If this port is already in use by another application on your server you can use the the synchrony.port system property to change it to an available port. If you run your own standalone Synchrony cluster, manually restart Synchrony on each node. If Synchrony is managed by Confluence, go to > General Configuration > Collaborative editing and choose Restart Synchrony. You can find the Confluence application logs at /logs/atlassian-confluence.log and Synchrony specific logs at /logs/atlassian-synchrony.log. See our proxy troubleshooting tips later in this page or head to Administering Collaborative Editing to find out more about possible proxy and SSL configurations. The most common issue is a misconfigured reverse proxy. If you see an error when you edit a page, but Synchrony is running, something is preventing your browser from connecting to Synchrony.
Confluence offline editor how to#
See How to check the status of Synchrony for Confluence Data Center for more info. You may want to use a third party monitoring tool to help you monitor your Synchrony cluster. Note: if you're running Confluence Data Center, this page will only be able to tell you if the current Confluence node is connected to your Synchrony cluster. To check if Synchrony is running, g o to > General Configuration > Collaborative editing. This page will help you troubleshoot problems with Synchrony in your instance. Under normal circumstances it should not need to be managed manually by an administrator. Collaborative editing is powered by Synchrony which synchronizes data in real time.