nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to link from jira to confluence after changing the certificate?

Alexander Schichow

So, here's the situation. The certificate we used on our jira/confluence machines has expired, so we got ourselfs a new one and i simply exchanged the old certificate with the new one. The root CA remained the same as well as the intermediate CA. The used certificate is a wildcard. So basically the same certificate is installed and trusted on both machines. However, when trying to link the two over application links, both machines tell me that the certificate used on the other machine can't be trusted since it's not installed locally.

Both machines are running behind a nginx reverse proxy and according to tomcat's documentation there is no need for a .jks in that case.

Now my question is, am I missing something?

Thanks for your replies.

Accepted answers

Alexander Schichow

figured it out. Apparently Jira as well as Confluence insist on having the certificate stored in the .jks even with a reverse proxy.

after I added our wildcard to the corresponding .jks' the link was back

All comments

Petr Vaníček

Hi,

when you try ping from jira server to confluence server by domain name (so for example run "ping jira.demain.tld" from confluence). Are you getting public IP or internal one? If internal one then you need change it in your local DNS or in hosts file.

If this is not your problem then let me know and I will try find some another reason for it.

Alexander Schichow

Hi Petr, thank you for your reply.

Am I assuming correctly that you mean the loopback when you say internal IP?

If so, then my answer is, yes I'm getting the public IP when i ping either of the machines.

If you actually mean the IP we used for those machines, the answer however, is that our machines are not publicly accessible and therefore only have internal IPs.

Also, like I mentioned before the application links used to work on both sides until I had to exchange the certificate.

Petr Vaníček

Did you reload/restart proxy?

Alexander Schichow

Yes, i did. Accessing the sites works fine as well.

Alexander Schichow

figured it out. Apparently Jira as well as Confluence insist on having the certificate stored in the .jks even with a reverse proxy.

after I added our wildcard to the corresponding .jks' the link was back

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira

application-link

proxy

ssl