Cant link Jira Tickets in Confluence

[zalim786]

hey guys,

so ever since we rolled back our Confluence from latest version to 6.10.0, we cant link

our Jira Tickets to confluence.
In Application links, its showing me network error.

The remote certificate can't be trusted

Jira - nox Nachtexpress may be using a self-signed SSL certificate or a certificate that was issued by a certificate authority that isn't known locally.

On the Jira side, its connected to confluence and not showing any errors.

In Jira System Information, I can see Java.Home is c:\\program files\java\jre

and in Confluence its c:\\program files\java\jdk

Java_Home in System Variables on windows is also c:\\program files\java\jdk

The server.xml we are using is also the correct one.

We are running both Jira and Confluence as service.

Do we have to put some startup value in Confluence service?

[Srinatha T · Accepted solution]

Hi @zalim786 ,

Welcome to Atlassian community. 

This error is typically caused when an installed SSL certificate from the remote application, which in this case is Confluence, isn't imported into the Java truststore Jira uses. To remedy this, there are some streamlined steps focused on importing the Confluence SSL certificate into Jira's JVM that can be found here:

• How-to-import-a-public-ssl-certificate-into-a-jvm 

I hope the above info helps. Have a good weekend. !

Thanks,

Srinath T

[zalim786]

this error did not exit before we upgraded confluence and rolled back, we didnt do anything with our Truststore, we didnt addes or taken out any SSL certificates.

The link you provided is not working.

regards

Zalim

[Bastian Stehmann]

Hi @zalim786 ,

to follow up to @Srinatha T answer, if you are using the Java that is installed with Confluence and/or Jira and you add the certificate in that trust store, the certificate will be lost when upgrading the application, because the Java installation will be overwritten.

So if you upgrade, you have probably add the certificate again after the upgrade.

[zalim786]

Thats correct, since our Confluence is running as a service, when we rolled back we created new service for Confluence, and we made a very rookie mistake, we forgot all about jvm file in Confluence Jre folder. We put that back in and it works.

Thanks all of you for the answers.

Regards

[Fabio Racobaldo _Herzum_]

Hi @zalim786 ,

please could you check the error in the atlassian-confluence.log file in order to have more information about your issue?

This troubleshooting article could help you https://confluence.atlassian.com/applinks/ssl-and-application-link-troubleshooting-guide-790632063.html

Hope this helps,

Fabio