The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can't check your base URL - reverse proxy

pavel.svec@i.cz
August 4, 2017

I managed to run Confluence 6.3.1 on Debian 9. Shortly after installation we decided to run Confluence on https with reverse proxy on apache.

I redirected port 80 to 443 and then to confluence default 8090. But I get 'Can't check your base URL'  problem during each logon to Confluence web-app even though I configured all parts according the atlassian doc.

Here is the (important) part of apache site file.

<VirtualHost <my_ip>:443>

ServerName <my_domain>

ProxyPass / http://localhost:8090/

ProxyPassReverse / http://localhost:8090/

</VirtualHost>

<VirtualHost <my_ip>:80>
ServerName <my_domain>
Redirect Permanent / https://<my_domain>/
</VirtualHost>

Here is the (important) part of tomcat server.xml. 

<Connector port="8090" connectionTimeout="20000" redirectPort="8443"
proxyName="localhost"
proxyPort="443"
secure="true"
scheme="https"
/>

 Here is the URL base from Confluence admin console.

https://<my_domain>

I believe there's nothing wrong with this configuration. Am I right?

Thx ahead for any contribution.

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 4, 2017

The proxyName in the server.xml should be the domain you want to access Confluence on, not localhost (unless you only every want to proxy from the server!)

For example

<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"
                proxyName="my_domain" proxyPort="443" scheme="https" />

pavel.svec@i.cz
August 7, 2017

1. It's made on purpose. -> by design => proxyName="localhost"

2. Could it help a module mod_remoteip (x-forwarded)?

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 7, 2017

No, your proxyName is incorrect, you need to use the right server name.  A module won't help you get around an incorrect setting.

pavel.svec@i.cz
August 7, 2017

Of course., u were right! Thx.

TAGS
AUG Leaders

Atlassian Community Events