Confluence could not retrieve public key for real-time collaboration service from Synchrony
Platform Notice: Data Center Only - This article only applies to Atlassian products on the data center platform.
After setting up a Synchrony node or cluster, you are unable to successfully enable Collaborative editing.
The following appears in the atlassian-confluence
INFO ... [plugins.synchrony.config.DefaultSynchronyConfigurationManager] retrievePublicKey [Collab editing plugin] Could not retrieve public key for real-time collaboration service at confluence.example.com/synchrony/jwt-key with exception: null
- Confluence Data Center
- One or more Synchrony nodes
- You are using an AWS ELB (Elastic Load Balancer)
- You cannot successfully enable Collaborative Editing
- You see various errors in the UI on the Collaborative Editing settings page:
- You are able to reach this URL in your browser and see the public key from Synchrony:
- You are able to reach this URL in your browser and see an OK from Synchrony:
You are not successful when running this command from the Confluence node:
This is caused by blocking TCP port 8091 in the ELB Security group. This prevents Confluence nodes from reaching Synchrony nodes on 8091.
You may still be able to reach the Synchrony node directly from the Confluence node on port 8091, but communication occurs through the load balancer (see diagram on this page).
Add port 8091 to the Elastic Load Balancer security group so that Confluence and Synchrony can communicate.
Example rule addition:
You may of course restrict this to only allow communication between those particular nodes or clusters.