[Bug] [Android] TLS connection could not be established: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.

[drogerie21]

Describe the bug
We are getting an SSLHandshakeException on Android with our new certificate on the server. We checked the SSL-Certificate, everything looks fine, no errors. This only happens on Android with the advanced http plugin. It works in chrome on Android and it works on iOS in our app where we also use the advanced-http-plugin.
Anyone experiencing the same problem?

This is the exact error:

{"status":-2,"error":"TLS connection could not be established: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found."}

System info

• affected HTTP plugin version: 3.3.1
• affected platform(s) and version(s): Android 13 and below
• affected device(s): Google Pixel 4
• cordova version: 11.0.0
• cordova platform version(s): 11.0.0 and 12.0.0 (tried both)

Are you using ionic-native-wrapper?
No

Minimum viable code to reproduce
we do nothing fancy, only use the sendRequest method with the url and some custom headers

[FliiFe]

Same issue here. Not using SSL pinning as I'm making request to an API I do not own. The only "workaround" is to set the server trust mode to nocheck, which looks super dangerous to me.

[drogerie21]

Problem was partly solved. we found a glitch in the cert-chain, that was not obvious. But the weird thing was: That was accepted by every other platform (ios with the advanced-http-plugin, chrome, edge, safari on desktop and even on chrome on android it worked). Only our android app refused the certificate.

[EderWillian]

I'm facing a similar issue

TLS Connection could not be established: javax.net.ssl.sslhandshakeexception: read error: SSL=0X7D173F1F08: Failure in ssl library, usually a protocol error.

I'm disturbing as I'm using server trust mode 'nocheck'.

[TiBz0u]

Hi @drogerie21 , are you on Capacitor?
We encounter the same issue from going from Cordova to Capacitor. The solution was to add intermediate CA into the "certificates" folder but I'm still wondering why this difference.
After analysis with the infrastructure, we added the wrong certificate imported. So everything is fixed now.

@drogerie21
If everything is fixed, maybe we can close this ticket?

Kr.

[Tanish2001]

@TiBz0u hi, I also migrated from cordova to capacitor and now i am also facing this issue, can u tell me how did u solved this issue?