nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

unable to create page after upgrade to 6.0.1 with apache 2.2 as proxy

Andreas Nitsche

Hi,

after I upgraded to latest 6.0.1 I'm not able to create pages anymore. The loading symbol does not disapear and after some time I see the message:

Loading the editor's taking longer than usual. Give it a few moments, then refresh your page if it still doesn't load. Speak to your Confluence admin if that doesn't fix it.

Refreshing the page was not helpful and I had a look at the catalina log and the atlassian-confluence.log, both do not show an error while loading a "add page".

Do you have any ideas what to try to solve this problem?

Cheers
Andi

Accepted answers

All comments

Panos

The problem comes the new collaborative script which surprise surprise is running at your port 8091 by default. So, open the port in the firewall and go to Admin -> Left panel down is the Collaborative Editing -> restart the synchrony.

Panos

Oh! And there is a new file called atlassian-synchrony in the log folder of your app data to help you debug.

Andreas Nitsche

I do have an apache in front of my confluence to do the SSL handshake for me. Looks like there is the problem because the OPTION request to port 8091 is also called via https. Is there already a solution documented?

I would start to proxy this service through apache as well. Shrink the listen for port 8091 to 127.0.0.1, setup the proxy on port 8091 for the external ip including ssl and test again. I will try that later or tomorrow.

Cheers
Andi

Panos

ah so i am not the only one with problem when ssl

Panos

https://confluence.atlassian.com/doc/administering-collaborative-editing-858772086.html scroll down to Change your Synchrony configuration

Andreas Nitsche

Just an update on how far I am at the moment.

The idea to configure synchrony to localhost was more difficult than I thought at the beginning because the documentation for synchrony.bind and synchrony.port are well hidden. I checked this site to see how I can configure synchrony for data center even if I do not have one: https://confluence.atlassian.com/doc/configuring-synchrony-for-data-center-858772125.html

Once the two options

JAVA_OPTS="$JAVA_OPTS -Dsynchrony.bind=127.0.0.1"
JAVA_OPTS="$JAVA_OPTS -Dsynchrony.port=8091"

are set, synchrony starts at localhost:8091 as expected. After that I configured apache to listen on the external ip on port 8091. Make to to not only use "Listen 8091" but use "Listen x.y.z.a:8091" and if you've enabled IPv6 according "Listen a:b:c::x:8091"

At the moment my collaboration service is NOT working yet, even if the service can be accessed through Apache with SSL. This is because a websocket is used for synchrony and my apache 2.2.15 of the CentOS 6 box I run confluence, doesn't support mod_proxy_wstunnel out of the box. This will be my next try to get this working via SSL.

Sooner or later I will setup a CentOS 7 box with apache 2.4.x which brings already the module mod_proxy_wstunnel with it.

Cheers and good night
Andi

Andreas Nitsche

Hey,

I made some changes to my configuration and it would be great if somebody with an apache 2.2 can verify that.

EDIT: build part of the module was missing in the explanation

Build mod_proxy_wstunnel for your apache version

# Check apache version (on my centos 6 box it's 2.2.15)
rpm -qa | grep httpd

# I would recommend to do all the build stuff in the next steps as an 
unprivileged user to not install or break anything when doing this as 
root.
# ensure these packages are installed, otherwise commands below will fail:
# - svn
# - libtool

# Checkout apache source
svn checkout http://svn.apache.org/repos/asf/httpd/httpd/tags/2.2.15/ httpd-2.2.15

# Get patch and apply it
wget https://gist.github.com/vitkin/6661683/raw/873dd8b4de4ad1ff69757ffe48fc574374aedc57/apache-2.2-wstunnel.patch
cd httpd-2.2.15
patch -p1 -i ../apache-2.2-wstunnel.patch

# Build Apache
svn co http://svn.apache.org/repos/asf/apr/apr/branches/1.4.x srclib/apr
svn co http://svn.apache.org/repos/asf/apr/apr-util/branches/1.3.x srclib/apr-util
./buildconf
./configure --enable-proxy=shared --enable-proxy_wstunnel=shared
make

# Copy the module to apache installation
sudo cp modules/proxy/.libs/mod_proxy_wstunnel.so /etc/httpd/modules

# Create module load file
cd /etc/httpd/conf.d
echo "LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so" &gt; mod_proxy_wstunnel.conf

Default proxy for the confluence application.

&lt;VirtualHost &lt;IPv4&gt;:443 &lt;IPv6&gt;:443&gt;
	...

	ProxyRequests Off
    ProxyVia Off
    SSLProxyEngine On

    ProxyPass / http://127.0.0.1:8080/
    ProxyPassReverse / http://127.0.0.1:8080/

	...
&lt;/VirtualHost&gt;

Connector in server.xml

&lt;Connector port="8080"
        maxHttpHeaderSize="8192"
        maxThreads="200"
        minSpareThreads="10"
        maxSpareThreads="75"
        enableLookups="false"
        redirectPort="8443"
        acceptCount="100"
        connectionTimeout="20000"
        debug="0"
        URIEncoding="UTF-8"
        proxyName="confluence.example.com"
        proxyPort="443"
        secure="true"
        scheme="https" /&gt;

Ensure to change the proxyName.

Add an additional VirtualHost for the synchrony service

&lt;VirtualHost &lt;IPv4&gt;:8091 &lt;IPv6&gt;:8091&gt;
	...
	SSLEngine on
	&lt;rest of ssl configuration&gt;
	...

    ProxyRequests Off
    ProxyVia Off
    SSLProxyEngine On

    ProxyPassMatch "^/synchrony/(.*/websocket.*$)" ws://127.0.0.1:8091/synchrony/$1
    ProxyPass /synchrony http://127.0.0.1:8091/synchrony

	...

&lt;/VirtualHost&gt;

Ensure only the external IPv4 and IPv6 addresses of your server are used here because confluence itself needs to be able to open the port 8091 on 127.0.0.1. The ProxyPassMatch statement is the trick. As long as confluence only calls websockets when there's a websocket in the url this will work.

Change synchrony.bind ip for your confluence instance

JAVA_OPTS="$JAVA_OPTS -Dsynchrony.bind=127.0.0.1"

Disable synchrony.proxy

The service is enabled by default, you can find this configuration statement in <confluence-home>/confluence.cfg.xml.

&lt;property name="synchrony.proxy.enabled"&gt;false&lt;/property&gt;

Restart Services

Depends on how you installed confluence, hopefully you know how to stop and start the application.

For apache you should do:

apachectl -S
service httpd restart

Would be great if somebody could check this explanation and reply if it's working this way for your setup as well.

Cheers
Andi

unknown

thanks Panos, this was the solution to my problem. but in my case i've temporary turned off collaborative editing feature and i will check firewall / router problem later wink with our network admin.

Andreas Müller6

Hi,

I changed from Cloud to Server 6.0.1 yesterday, imported everything from the Cloud instance, have it up and running now BUT editor doesn't work. Same message as you have. I can't create Pages and also can not edit pages.

Tried direct connection without SSL, no go.
Running NginX with SSL as proxy now, still, no go.

Panos

And thats the reason I switched back to lovely 5.10 cheeky Anyway, look the inspection console to identify the error (could be different than ours?) which will give you clues of what is going on. Further more in the application folder/logs there is a new log file, something with synchrony.log. Take a look there also

Andreas Müller6

As a workaround I turned off 'collaborative editing'. Let's see if future versions will get a fix for that smile

Rachel Robins

Hi everyone,

Sorry to hear you've had problems getting collaborative editing up and running with your reverse proxy. It's important to know your reverse proxy must support websockets. This means Apache 2.2 won't work, you need Apache 2.4.

The following docs have some example configs that you can use as a basis for your own config. Note that the order of directives and blocks is important in the examples.

Proxying Atlassian server applications with Apache HTTP Server (mod_proxy_http) (be sure to expand the Confluence example in Part B, step 2)
Using Apache with mod_proxy (note the info on required modules that you may need to enable)

Vojtech Galda

I don't agree with you. Is possible use proxy_wstunnel_module module with 2.2. @Andreas Nitsche wrote down how to get this module, see below

Roman Samorodov

Hi I just changed one system property and it worked for me.

In file <Confluence home>\confluence.cfg.xml I changed synchrony.proxy.enabled property to false.

Documentation

Siddheshwar mhetre_l4zeyg

@Panos Karampis, how do you downgrade the Conflunece to 5.10?

Panos

For you, (hopefully all of you) that still have problems upgrade to 6.0.2. According to their release notes there are some bug fixes regarding synchrony.

Mick Carroll

Thanks! Worked for me. I just turned off Collaborative Editing (we dont use it)

Hal9000

I am running Apache 2.4, but all I needed to make it work was set synchrony.proxy.enabled property to false.

Jason Hihn_vsd9pb

I am using NGINX, and I am also interested in the setting to make this work on NGINX.

小白

set synchrony.proxy.enabled property to false work for me.

my confluence version is 6.6.1

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

confluence-administration