URGENT: Issue with Collaborative editing with Confluence DC on HTTPS

[Yohaan Sunny]

Hi,

I have deployed Confluence DC on AWS. After the deployment I had added an HTTPS listener on the LB with our certificate (uploaded using IAM) and pointed our DNS to this LB endpoint. All is well and I can access the site on HTTPS.

However, I now have an issue with collaborative editing. Since Synchrony runs on HTTP and the website is on HTTPS, when I try to create/edit a page, the page does not get loaded.

Checking the network traffic, I see it is because the browser has detected an issue in calling the synchrony-heartbeat endpoint which is HTTP and not HTTPS.

The error is "mixed-content" and found this article on Atlassian knowledge base for this but it doesn't really tell me what I need to do to fix this.

If I ignore this in the browser, then the session comes out of HTTPS to HTTP.

This issue is delaying our migration plans from Confluence to Confluence Data Center.

Has anyone here configured Confluence DC and Synchrony on HTTPS? Please help!!

[Yohaan Sunny · Accepted solution]

Issue resolved.

Redeployed the template with the Certificate (uploaded via IAM) value in place and added the CATALINA option -Dsynchrony.service.url=<mydns.com>/synchrony/v1