Remote OpenSearch connection-result CONNECTION_ERROR

Lasse Meyer

I have a Bitbucket Data Center on a Linux VM in Azure and a remote OpenSearch on a Linux VM in Azure, both are in the same network.
OpenSearch is configured like in: Debian - OpenSearch Documentation
And Bitbucket Data Center is configured like in: Install and configure a remote OpenSearch server | Bitbucket Data Center 8.18 | Atlassian Documentation

When i´m using this on my bitbucket data center vm: "curl -X GET https://IP:9200 -u 'user:pw' --insecure" (with my own credentials, which i setuped), i get the right answer from the opensearch server.
But in Bitbucket i still have connection-result: CONNECTION_ERROR

This is the only thing i can find in the atlassian-bitbucket.log and i doesnt get it:

---

2024-02-21 14:21:05,499 DEBUG [I/O dispatcher 15] c.a.b.i.s.c.s.t.DefaultSearchConnectionTester Testing connection with search server failed due to exception:
java.util.concurrent.CompletionException: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

---

And i dont know why.
Does anyone know or have some ideas?

Aman Shrivastava_2l9dw2

Hi Lasse,

The below error indicates that a target application(in this case OpenSearch) is running with an SSL/TLS configuration but it can't be trusted by Bitbucket. This is most likely due to the peer application's certificate being self-issued (i.e., not signed by a CA) or a certificate chain does not exist within the Java trust store that Bitbucket is using.

java.util.concurrent.CompletionException: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

I would suggest you review the Unable to connect to SSL services due to "PKIX Path Building Failed" error KB that covers all the possible causes and the fix for this error. In case of any problem, please raise a ticket with Atlassian support.

Regards,
Aman