JIRA, Confluence Server and friendly base URLs
Asked by Michael Woffenden:

We've setup JIRA Service Desk (server) and Confluence (server) on the same Windows machine.

And we've setup the initial base URLs as follows:

* support.ourdomain.com - for service desk
* support.ourdomain.com:8090 - for confluence

Both apps are running, but we would like to setup confluence like this:

* kb.ourdomain.com

Not knowing our way around Apache, how would we get our desired result working?


Answers:
author: Hassan Aftab
body: Hi Michael

You have two options now, each with its own constraints.

**Option 1**

If you have two IP address, then you can configure each hostname to resolve to different IP address and configure *address*parameter in tomcat configurations. For Confluence, you can use the following connector,
> `<Connector port=80`  
> `address="kb.ourdomain.com"`  
> `...`
>
> `...`
>
> `. />`

Similarly for JIRA, tomcat can also be set to respond to port 80 on *address="support.ourdomain.com"*, which eventually resolves to a different IP address.

**Option 2**

The second option would be to use HTTP (port 80) for JIRA and HTTPS (port 443) for confluence.
> http://support.ourdomain.com --\> Goes to JIRA  
>
> https://kb.ourdomain.com --\> Goes to Confluence

For this Confluence will need to be configured to accept only HTTPS connections, by removing the HTTP connector in tomcat configuration of JIRA.

[Confluence over SSL](https://confluence.atlassian.com/doc/running-confluence-over-ssl-or-https-161203.html)

**Notes**

Proxies are the default choice for such configurations, since two applications can't listen on the same IP/port on a single machine.

I would suggest you to have a look at our guide to understand how this works.

[Atlassian applications with Apache Httpd](https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html?)

It will allow you to route requests on hostnames like,
> support.ourdomain.com --\> Goes to JIRA  
>
> kb.ourdomain.com --\> Goes to Confluence

as well, as context paths,
> support.ourdomain.com/jira --\> Goes to JIRA  
>
> support.ourdomain.com/confluence --\> Goes to Confluence

Thanks,

Hassan Aftab

comments: author: Michael Woffenden
body: Thanks [@Hassan Aftab](/t5/user/viewprofilepage/user-id/1167138)I will give these options a try. Looks like the proxies is the cleanest, would you say?

Also the last link does not work. Is this the right link?

* [Using Apache with mod_proxy - Atlassian Documentation](https://confluence.atlassian.com/doc/using-apache-with-mod_proxy-173669.html "Using Apache with mod_proxy - Atlassian Documentation")


author: Hassan Aftab
body: Hi Michael

I apologise for the previous link.

The link that you have shared is correct.

Proxies are indeed the nicest way of doing this and provides more flexibility like SSL and context paths.

You can also consider Nginx or IIS for integrating with Atlassian applications. Please find below links to configure Nginx.

* [JIRA with Nginx](https://confluence.atlassian.com/jirakb/integrating-jira-with-nginx-426115340.html)
* [Confluence with Nginx](https://confluence.atlassian.com/confkb/how-to-use-nginx-to-proxy-requests-for-confluence-313459790.html)

Similarly, you can also find guides to configure IIS.

Thanks,

Hassan Aftab


author: Michael Woffenden
body: Very helpful [@Hassan Aftab](/t5/user/viewprofilepage/user-id/1167138)- But can you clarify something in your first reply? Does the "Notes" section (which mentions proxies) pertain to both Options 1 and 2, or just to Option 2?


author: Hassan Aftab
body: HI Michael

Notes are actually the third option.

Options 1 \& 2 have nothing to do with proxies.

Cheers, Hassan


author: Michael Woffenden
body: Hi [@Hassan Aftab](/t5/user/viewprofilepage/user-id/1167138)- Got this working using option 1. Thanks!