Forums

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

Using Apache for JIRA server and Confluence server running on same VM but different ports

Navrattan Jain August 24, 2020

Hi everyone,

I have installed JIRA server and Confluence server on Linux VM. They are installed on port 8100 and 8300. Further i have installed apache for reverse proxy. My Jira uses url jira.example.com and confluence uses url confluence.example.com:8300. Problem is i am not able to configure apache for confluence in the same way i did for jira server. My confluence url confluence.example.com directs to apache default page. i followed the following document:

https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html

Please if someone can help that would be great.

1 answer

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 Leaders.
August 25, 2020

What have you got for the proxy and reverse proxy lines in the Apache site file(s)? (it would be good to see both pairs - Jira and Confluence)

What changes have you made to the server.xml for the two systems?

Navrattan Jain August 25, 2020

Thanks for replying @Nic Brough -Adaptavist-. Please help. Here i have shared the changes i made to respective files:

For Confluence:

Server.xml i added the bold one

<!--

         ==============================================================================================================

         DEFAULT - Direct connector with no proxy, for unproxied HTTP access to Confluence.

 

         If using a http/https proxy, comment out this connector.

         ==============================================================================================================

        -->

        <Connector port="8300" connectionTimeout="20000" redirectPort="8443"

                   maxThreads="48" minSpareThreads="10"

                   enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"

                   protocol="org.apache.coyote.http11.Http11NioProtocol"/>

scheme="http" proxyName="confluence.example.com" proxyPort="80"/>

 

For JIRA:

Server.xml file i added the bold one

<!--

         ==============================================================================================================

         DEFAULT - Direct connector with no proxy for unproxied access to Jira.

 

         If using a http/https proxy, comment out this connector.

         ==============================================================================================================

        -->

 

        <!-- Relaxing chars because of JRASERVER-67974 -->

        <Connector port="8100" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"

                   maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"

                   maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"

                   acceptCount="100" disableUploadTimeout="true" bindOnInit="false"/>

                   proxyName="jira.example.com"

                        proxyPort="80"

                        scheme="http"/>

 

Apache2.conf file i added the bold one

# Include generic snippets of statements

IncludeOptional conf-enabled/*.conf

 

# Include the virtual host configurations:

IncludeOptional sites-enabled/*.conf

<VirtualHost *:80>

  ServerName jira.example.com

 

  ProxyRequests Off

  ProxyVia Off

  ProxyPreserveHost On

  <Proxy *>

   Require all granted

   </Proxy>

 

   ProxyPass / http://jira.example.com:8100/

   ProxyPassReverse / http://jira.example.com:8100/

   </VirtualHost>

 

<VirtualHost *:80>

  ServerName confluence.example.com

  ProxyRequests Off

  ProxyVia Off

  ProxyPreserveHost On

  <Proxy *>

   Require all granted

   </Proxy>

 

   ProxyPass / http://confluence.example.com:8300/

   ProxyPassReverse / http://confluence.example.com:8300/

   </VirtualHost>

 

I also tried modifying connector settings in server.xml file under apache http comments but it didn't work.

 

Thanks and Regards

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 Leaders.
August 25, 2020

What have you got as the context entries for the two services?

Navrattan Jain August 25, 2020

@Nic Brough -Adaptavist- i haven't added or modified context entries. Because i want Jira to be accessed as jira.example.com and confluence as confluence.example.com instead of example.com/jira and vice versa. Thats what i thought not sure though.

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 Leaders.
August 25, 2020

The config you have given me here seems to say everything should be working, so I am a bit stuck.

My best guess is that the next place to look is at the detail of the proxy, as that is not referring back to Confluence like it is to Jira.  I would want to check that both services are available on the addresses the proxies talk to, but I doubt that is wrong.

Navrattan Jain August 25, 2020

@Nic Brough -Adaptavist- 

Like i am able to access jira.example.com but for confluence i have to go for confluence.example.com:8300 

It's driving me crazy. Thing is i need SSL certificate and easy url to access applications. Can you suggest anything else please!

 

Thanks a lot

Navrattan Jain August 25, 2020

@Nic Brough -Adaptavist- Hi, i think the problem is at domain service provider end.

I saw the A records and found following entries:

domain-example.com

subdomain- confluence.example.com at ip xx.xxx.xxx.xx

one more entry with same subdomain confluence.example.com at yy.yyy.yyy.yy

I guess it was conflicting. Can this be the issue?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events