Confluence 6.9.0 Problems with Collaborative Editing
Asked by Tim Buecher:

Dear Community,

I'm having problems with my Confluence 6.9.0 Server Installation on CentOS 7.

There's an Apache 2.4 used as a reverse Proxy and DNS Termination Point.

When I activate Collaborative Editing and try to edit a page, I'm always facing "

The editor didn't load this time error when trying to edit a page" Error. I tried everything on <https://confluence.atlassian.com/confkb/confluence-throws-the-editor-didn-t-load-this-time-error-when-trying-to-edit-a-page-840796639.html>, but I'm not getting anywhere. When I'm trying the port, it's available - when I tested the firewall, the request went through. So nothing should be blocking WebSocket Connections ....

Also for completion, I wanted to paste my Apache 2.4 config ...

\<VirtualHost \*:443\>  
SSLEngine on  
SSLCertificateFile /etc/pki/tls/certs/confluence-domain.crt  
SSLCertificateKeyFile /etc/pki/tls/private/confluence-domain.key

LogLevel alert rewrite:trace6  
ErrorLog logs/confluence-domain-error_log  
CustomLog logs/confluence-domain-access_log common  
ServerName confluence-domain  
ProxyRequests Off  
ProxyPreserveHost On

<br />

RewriteEngine On  
RewriteCond %{REQUEST_URI} !\^/synchrony  
RewriteRule \^/(.\*) http://confluence-server:8090/$1 \[P\]

\<Proxy \*\>  
Require all granted  
\</Proxy\>

ProxyPass /synchrony http://confluence-server:8091/sychrony

\<Location /synchrony\>  
Require all granted  
RewriteEngine on  
RewriteCond %{HTTP:UPGRADE} \^WebSocket$ \[NC\]  
RewriteCond %{HTTP:CONNECTION} Upgrade$ \[NC\]  
RewriteRule .\* ws://confluence-server:8091%{REQUEST_URI} \[P\]  
\</Location\>

ProxyPass / http://confluence-server:8090/  
ProxyPassReverse / http://confluence-server:8090/


Answers:
author: AnnWorley
body: I compared your Apache configuration side by side with the documentation ([Securing your Atlassian applications with Apache using SSL](https://confluence.atlassian.com/kb/securing-your-atlassian-applications-with-apache-using-ssl-838284349.html)) and it looks like there are a lot of differences.

![Screen Shot 2018-05-23 at 2.03.36 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/22781i67C058FA4D6D3B56/image-size/large?v=v2&px=999 "Screen Shot 2018-05-23 at 2.03.36 PM.png")

I recommend using the same directives in the same sequence for best results.

Please also make sure your connector in \<confluence_install_dir\>/conf/server.xml is set up as documented to include the proxyName, proxyPort and scheme:

    <Connector port=<default> maxThreads=<default>    minSpareThreads=<default>    connectionTimeout=<default>    enableLookups=<default>    maxHttpHeaderSize=<default>    protocol=<default>    useBodyEncodingForURI=<default>    redirectPort=<default>    acceptCount=<default>    disableUploadTimeout=<default> proxyName="<subdomain>.<domain>.com" proxyPort="443"    secure="true" scheme="https"/>

comments: author: Tim Buecher
body: I'm sorry! You were totally right. I changed my config according to the article and everything works now.


author: Kelly Albrecht
body: Consider the above answer as well but I don't think you need any of the Sychrony directives in 6.9.0.

What happens if you comment out all of this:  

```
RewriteEngine On
RewriteCond %{REQUEST_URI} !^/synchrony
RewriteRule ^/(.*) http://confluence-server:8090/$1 [P]

<Proxy *>
Require all granted
</Proxy>

ProxyPass /synchrony http://confluence-server:8091/sychrony

<Location /synchrony>
Require all granted
RewriteEngine on
RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC]
RewriteCond %{HTTP:CONNECTION} Upgrade$ [NC]
RewriteRule .* ws://confluence-server:8091%{REQUEST_URI} [P]
</Location>
```

I don't have any of that on 6.9.0 and it works great.

comments: author: Tim Buecher
body: Thanks for your input! I tried your solution, but it returned also the timeout in my instance ....


Tags: confluence-server

server