Confluence Collaborative Editing does not work with SSL and Apache 2.4.9 or earlier

Still need help?

The Atlassian Community is here for you.

Ask the community

Atlassian applications allow the use of reverse-proxies, however Atlassian Support does not provide assistance for configuring them. Consequently, Atlassian can not guarantee providing any support for them.

If assistance with configuration is required, please raise a question on Atlassian Answers.


This Knowledge Base article was written specifically for the Atlassian Server platform. Due to the Restricted functions in Atlassian Cloud apps, the contents of this article cannot be applied to Atlassian Cloud applications.


Confluence 6+ is configured with Apache 2.4 using SSL and Websockets as described in this guide: Securing your Atlassian applications with Apache using SSL

However, when trying to use collaborative editing, you get an error in the browser and the editor does not load. 



  • Confluence 6 or higher
  • Apache 2.4.9 or earlier (Not Apache 2.2, as it does not support Websockets at all)
    • If you are on Apache 2.2, please upgrade to the latest version of 2.4 and check if the issue persists
  • SSL configured in Apache and/or Tomcat level
  • The appropriate modules are loaded, specifically

Diagnostic Steps


The following bug breaks the SSL handshake because it sends plain-text requests to the Websockets URL, as opposed to SSL requests:  Plain-text request is sent to WSS URL (which should be over SSL) in mod_proxy_wstunnel


Workarounds are ways to temporally circumvent a problem, although it still exists in the application.


Upgrade to Apache 2.4.10 or higher. For some operating systems there is a fix available that has been tested using Apache version 2.4.6-45.

Last modified on Jan 30, 2017

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.