It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Get Confluence working on a subdomain Edited

Software properties:

  • OS: Ubuntu 16.04 (with PLESK installed)
  • Webserver: Apache 2.4.18
  • Confluence 6.3.1


Dear all,

I simply try to get Confluence working on a subdomain like sub.domain.tld.

To do so, I read the documentation and the community forums.

After doing so, I felt ready to start.

What I did was to

  1. Create an A-name entry for the sub-domain in the DNS
  2. Add the subdomain to /etc/hosts
  3. Install Confluence
  4. Create a config file under /etc/apache2/confluence with the entries, where XXX.XXX.XXX.XXX is my IP-adress:
<VirtualHost XXX.XXX.XXX.XXX:80>
    ServerName sub.domain.tld
	ProxyRequests Off
	# Auth changes in 2.4
		Require all granted

	ProxyPass /synchrony http://<internal_domain>:8091/synchrony

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

	ProxyPass / h ttp://domain.tld:8090/
	ProxyPassReverse / h ttp://domain.tld:8090/

	<Location />
		Require all granted
  • Enable the new site
  • Change server.xml according to this documentation (add proxy name, proxy port and scheme)
  • Restart Confluence 
  • Restart Apache2

Unfortunately, this does not help me.

When entering sub.domain.tld in a browser, I am redirected to the PLESK "standard" webpage. Only entering the port 8090 will allow me to enter the confluence webpage.

Any ideas from your side?

Thank you in advance,

best regards,



2 answers

1 accepted

0 votes
Answer accepted

@Nic Brough [Adaptavist]:

Thank you for your support. This was - unfortunately - only a problem in this post.

The "real" lines are

ProxyPass / http://domain.tld:8090/

ProxyPassReverse / http://domain.tld:8090/

Any other idea on what might be wrong?

Thank you in advance.

Hmm.  It looks good to me, so I don't think it's your config.

Two other thoughts -

1) Can you try "sudo netstat - plant" to check that it really is apache listening on port 80?

2) In your apache config, how is Plesk configured?

@Nic Brough [Adaptavist]

Your other thoughts were right.

Due to the Plesk integration, the vhost configuration nedded to start with

<VirtualHost XXX.XXX.XXX.XXX:7080 >
ServerName "sub.domain.tld:80"


After applying these changes, it worked.

Thank you for yur support.

Ah, so Apache was serving up Plesk first on port 80 and then ignoring Confluence because it was listed lower?

You're right.

Solved it finally thanks to your ideas.

@Philip Deubner Is <VirtualHost XXX.XXX.XXX.XXX:7080> a Standard-Port when using Plesk? Or do I have to find out the individual one for my setup?

@Nicolas Rehner: 7080 seems to be a Plesk standard port.

So from my assumption, this should also work at your place.

0 votes

Your proxypass and proxypassreverse lines are wrong.

The first one for synchrony is ok, but the other two are html url links and have too many entries.  They should be as simple as the synchrony one, and only one url.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published Thursday in Confluence

Confluence CVEs and common questions

Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...

257 views 0 12
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you