cannot create new content in confluence after adding reverse proxy Edited

[Klaus Pedersen]

Hi,

I just added a reverse proxy in my JIRA-software+confluence setup and after some learning I managed to get it all working, I thought..

This morning I logged into confluence and clicked "Create" and i just got a spinning disk..

Looked in the log analyzer, and found this one: After upgrading Confluence, you are unable to create new pages or spaces Describes my problem pretty well.

It suggested 3 things to check:

proxyport, proxyname and scheme..

All are set as they should.. 443, confluence.domain,tld and https..

any suggestions of where to look for clues?

Confluence is running version 7.0.1

Apache2 vhost is configured like this:

<VirtualHost *:443>

ServerName confluence.domain.tld
ProxyRequests Off
ProxyPreserveHost On

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

SSLEngine On
SSLCertificateFile /var/www/SSL/wildcard_domain_tld.crt
SSLCertificateKeyFile /var/www/SSL/wildcard_domain_tld.key
SSLCertificateChainFile /var/www/SSL/wildcard_domain_tld_ca.crt

<Proxy *>
Require all granted
</Proxy>

ProxyPass /synchrony http://confluence-internal.domain.tld:8091/synchrony

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

ProxyPass / http://confluence-internal.domain.tld:8090
ProxyPassReverse / http://confluence-internal.domain.tld:8090

<Location />
Require all granted
</Location>
</VirtualHost>

The server.xml files proxy-part is like this:

<Connector port="8090" connectionTimeout="20000" redirectPort="8443"
maxThreads="48" minSpareThreads="10"
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol"
scheme="https" secure="true" proxyName="confluence.domain.tld" proxyPort="443"/>

All help is appreciated :)

[Shannon Spaniol · Accepted solution]

Hi Klaus,

Welcome to Atlassian Community. It's nice to have you join us.

Do you happen to see any errors in your atlassian-confluence.log file? See Working with Confluence logs for more details.

I would recommend reviewing your proxy setup against the following:

• Administering Collaborative Editing > Proxy and SSL considerations
• Troubleshooting Collaborative Editing > Reverse proxy issues 
• Possible Confluence and Synchrony Configurations > With a reverse proxy 

Let me know if you have any trouble or questions with that.

Regards,

Shannon

[Klaus Pedersen]

Hi,

I actually managed to figure it out the other day :) just didn't have the time to post the reply yet.. So here it is. :)

After looking through the guides i noticed that during the different guides you proxy the socket-server connection but it wasn't mentioned to actually open the port in the firewall on the confluence server.. after some testing (Don't use firefox with disabled cache for testing), I got everything to work.

The problem was that i didn't get any use full errors in the logs other than to check the proxy settings "https", "port" and the domain..

So all I needed was, more or less:

# sudo firewall-cmd --zone=public --permanent --add-port=8091/tcp

on the confluence server :P

Thanks for the reply :)

Regards,

Klaus

[Shannon Spaniol]

Hi Klaus,

Thank you for sharing your fix! Glad to hear you were able to solve it.

Take care, and have a pleasant rest of your week.

Regards,

Shannon