Managing Synchrony connectivity in Confluence Data Center

This insight appears when your Synchrony service experiences connection issues. Synchrony connectivity measures the connection state between Confluence and its collaborative editing service. Maintaining stable connectivity between Confluence and Synchrony is crucial for real-time collaboration and content editing.

How do connectivity issues affect performance?

When Synchrony connectivity fails:

• Users cannot edit pages collaboratively

• Changes may fail to save

• Real-time updates stop working

• Edit conflicts become more likely

• What's the recommendation?

What's the recommendation?

Follow these steps to restore proper connectivity:

Verify synchrony service status

Service status verification

• Navigate to Administration > General Configuration > Collaborative editing

• Check service status indicators

• Review recent error logs

• Verify process status on all nodes

Base uRL configuration

• Confirm correct base URL settings

• Test URL accessibility from all nodes

• Verify SSL certificate validity if applicable

• Check for any URL rewriting issues

Learn about administering collaborative editing

Check system configuration

Port configuration

• Check default port (8091) availability:

  
  

  # Linux systems
  netstat -an | grep "8091"
  lsof -i :8091
  # Windows systems
  netstat -na | findstr "8091"

  
  

• Verify no port conflicts exist

• Ensure consistent port configuration across nodes

Plugin health

• Verify Synchrony Interop Bootstrap plugin status

• Check for version compatibility

• Review plugin error logs

• Confirm plugin configuration consistency

Learn about Synchrony configuration

Review proxy configuration

Proxy setup

• Review proxy configuration for /synchrony/* endpoints

• Verify WebSocket support

• Check timeout settings

• Confirm proper SSL termination

Network configuration

• Test network connectivity between nodes

• Verify DNS resolution

• Check firewall rules

• Monitor network latency

See synchrony heartbeat fails due to timed out exception

Preventive measures

• Monitor Synchrony logs regularly

• Set up alerts for connection failures

• Document working configuration

• Test after infrastructure changes