Jira can't connect to Confluence due to not known SSL CA, but previously added to trusted CA in keys

[VIPPERDEV]

I installed JIRA and Confluence on two VPS platforms. On the first one, where JIRA is installed, I also added Apache for proxy and created self-signed SSL on that platform for all my subdomains - *.mydomain.com. I also added that certificate to the trusted certificates in keystore on each platform. Everything is working well despite the fact that JIRA cannot connect to Confluence in Application Links. However Confluence can connect to JIRA. The error is "The remote certificate can't be trusted". I'm searching Atlassian documentation and other people cases but everywhere is written to add the certificate to keystore on both platform - and I already done it.

[Shannon S]

Hi Wojciech,

Something still seems wrong with the certificate. One thing I'd check is that the certificate is from a trusted provider, but there are a few more things you can do.

• Application links using SSL with reverse proxy - a customer here had a similar error and explained everything he did to fix it. You could compare this to your steps and make sure that nothing is being missed.
• SSL and Application Link Troubleshooting - basic set of instructions to start troubleshooting on your instance. It will help here if you can tail your Jira logs to see what error messages are showing besides "the remote certificate can't be trusted." This will give you a better idea of the issue at hand.
• Unable to connect to SSL services due to PKIX path building failed - this is the most common error I see in the logs, and this particular article I have had most success with. Be sure to try each troubleshooting step and even backtrack your steps if you need to.

Let us know how it goes, and if you have any issues, please send us what errors you see from your Jira logs.

Regards,

Shannon