Application Connections with SSL


We are running JIRA 6.2.7 and FishEye 4.0.4 on a Server 2008 R2 host and Bamboo 5.9.7 on a Server 2012 R2 host. Tomcat is used as the backends. I am trying to link the applications with SSL installed. Currently, I just have a cert in JIRA, which I have exported and imported into Bamboo and FishEye's keystore and trusted certs. However, I am getting the error that: "Application 'Jira' seems to be offline. Click here to Relocate." It's very similar to this person's post:

They solved it by switching to an Apache reverse proxy, which I'd rather not have to deal with if possible.

I've tried to troublshoot with this:

Haven't been successful so far. JIRA is definitely reachable over HTTPS, but I've had to roll back to HTTP until we can get the links working. If anyone has managed to get this configuration to work and has some instructions to do this, I would appreciate the assistance. 


1 answer

Each application link has both a display URL and an application URL. It is important that the display URL is exactly the same as the base URL of that application but you can have a different Application URL.


JIRA running on
Confluence running on

External URLS: and

When creating an application link, use as the application url and as the display URL. 

So if the wilcard cert is used for *, will a cert error be thrown if https://servername is used for the URL rather than

I see I missed an important part in my message:

The application url should be: in my example above. So no HTTPS and therefore no need for the application links to trust each others certificates.

So even if JIRA is set to redirect HTTP to HTTPS in the config, the backend application links do not need to use HTTPS? But wouldn't that also mean that traffic between the apps is in the clear?

Sorry for the delay, but I'm only able to post twice in 24 hours, which is a bit limiting.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

395 views 6 0
Join discussion

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