Reverse proxy configuration for synchrony problem

[Neil Anthony Morada]

Hi All,

We jut encountered synchrony error on our confluence. Our confluence was installed in our server. After searching some troubleshooting method in confluence, I saw this link on how to check the status of our synhrony.

https://confluence.atlassian.com/confkb/how-to-check-the-status-of-synchrony-for-confluence-data-center-953651062.html

And I did some methods on it like this:

<confluence-base-url-without-context-path>/synchrony/heartbeat>

 I typed this on our browser and a  "Page Not Found" appeared.

As said in this method, If the above URL directs you to a Confluence page stating "Page Not Found": There is a misconfiguration of your reverse proxy which is directing the  /synchrony/*  traffic to your Confluence webserver instead of your Synchrony server. 

Now, can I ask how to reconfigure our reverse proxy for our synchrony problem? Thank you!

[Nic Brough -Adaptavist-]

Synchrony needs to use "websockets".  I'm not going to pretend I understand the mechanisms that describes, but I do know how to make it work through a proxy.  I tend to only work with Apache2  (and you need to be on 2.4 or above for this to work)

This system has offloaded the SSL to Apache, and the Apache is serving up a site made of several services, so it's got somewhere.com as the main page, and somewhere.com/jira for their Jira, somewhere.com/docs as their Confluence and so-on.

Their Apache2 is running on their web-server, and Confluence internally on the server 192.168.1.144:8090

So...

    # Confluence proxy pass

    ProxyPass /docs http://192.168.1.144:8090/docs
    ProxyPassReverse /docs http://192.168.1.144:8090/docs

    # Synchrony as it's got a few funnies

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

I'm not sure how to translate that to nginx or a load balancer off the top of my head, but hopefully it might give you some pointer!

[Neil Anthony Morada]

Hi @Nic Brough -Adaptavist- 

Thank you for this information. I will try to work on this.