Configuring collaborative editing with nginx

[Dmitry Krasichkov]

Hello. I'm having difficulties with configuring collaborative editing. Our server uses nginx and as a starting point I used instructions from this page

(How to use nginx to proxy requests for confluence)

Since we want to launch conluence on seperate url, system itself is deployed in root with synchrony at /synchrony and configuration looks something like this

server {
    listen 80;
    server_name wiki.site_url.ru;
     access_log off;
     location /synchrony {
         proxy_set_header Host $host;
         proxy_set_header X-Forwarded-Host $host;
         proxy_set_header X-Forwarded-Server $host;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_pass http://127.0.0.1:8091;
         proxy_http_version 1.1;
         proxy_set_header Upgrade $http_upgrade;
         proxy_set_header Connection "upgrade";
     }

    location / {
         proxy_set_header Host $host;
         proxy_set_header X-Forwarded-Host $host;
         proxy_set_header X-Forwarded-Server $host;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_pass http://127.0.0.1:8090;
     }

}

Base url is configured to wiki.site_url.ru and seems to be working as intended.

When Confluence is started with collaborative editing enabled, I can see that server is processing request at ports 8090 and 8091 and in collaborative editing tab in configuration I can see, that everything seems to be in order and editing mode is started, but if I try to access the page being edited I either get message "This page is taking longer to load than usual" and unable to edit it, or a message about inablity to start websocket which results in editing page seperatly and merging later.

Thanks in advance.

[AnnWorley · Accepted solution]

Hi Dmitry,

I understand you are seeing WebSocket errors when editing pages in Confluence. I am curious what version of Confluence you are running.

In earlier versions of Confluence, like 6.0, a WebSocket connection had to be possible for collaborative editing and XHR fallback was set via a system option as described in Websocket issues. in later versions we added the XHR fallback to Confluence by default, so I am not sure why you would see a WebSocket error.

Thanks,

Ann

[Dmitry Krasichkov]

Thank you for your reply. We are using Confluence 6.7.1. After the update, problem resolved itself. Thank you.