Skip to content

"Trust anchor for certification path not found"

Key idea:

Android throws this (java.security.cert.CertPathValidatorException) when the server certificate is signed by a CA missing from the Android system truststore. Three causes: (1) self-signed or private CA, (2) incomplete chain — server doesn't send the intermediate, (3) old Android < 7 doesn't know newer CAs (Let's Encrypt R3 since 2021). Fix: install the full chain on the server or add the CA to network_security_config.xml.

Below: details, example, related, FAQ.

Check your site's SSL →

Details

  • Chain check: openssl s_client -connect host:443 -showcerts — should show 2+ certs
  • Android 7+ supports Let's Encrypt. Android < 7 — needs ISRG Root X1 cross-signed
  • network_security_config.xml — per-app trust config (API 24+)
  • Does not work with Google Play — apps use certificate pinning
  • Alternative: apps using OkHttp with a custom TrustManager

Example

<!-- res/xml/network_security_config.xml -->
<network-security-config>
  <base-config>
    <trust-anchors>
      <certificates src="system"/>
      <certificates src="@raw/my_ca"/>  <!-- res/raw/my_ca.pem -->
    </trust-anchors>
  </base-config>
</network-security-config>

<!-- AndroidManifest.xml -->
<application android:networkSecurityConfig="@xml/network_security_config" ...>

Related

TL;DR: Resolving the 'Trust Anchor for Certification Path Not Found' Error on Android

The 'Trust anchor for certification path not found' error on Android devices typically indicates an issue with SSL certificate validation. To resolve this, ensure your device's date and time are correct, clear the browser cache, and check if the website's SSL certificate is properly installed and trusted. If the issue persists, consider updating the Android system or the web browser in use.

Understanding the 'Trust Anchor' Concept in SSL Certificates

The term 'trust anchor' refers to a known and trusted certificate authority (CA) that issues digital certificates for secure communications. In the context of SSL/TLS, a trust anchor is the root certificate that forms the basis of a certificate chain. For Android devices, the system maintains a list of trusted root certificates, and if the server's certificate does not chain back to a trusted anchor, users may encounter the 'Trust anchor for certification path not found' error.

To troubleshoot this, it is essential to verify the SSL certificate of the website. You can use the following command in your terminal to check the certificate chain:

echo | openssl s_client -connect example.com:443 -showcerts

Replace example.com with the actual domain. This command will display the server's certificate along with any intermediate certificates. Ensure that the chain links back to a trusted root CA recognized by Android.

For Android, the trusted root certificates are stored in the system's certificate store. If a website's SSL certificate is issued by an unrecognized CA or if the intermediate certificate is missing, users may see the aforementioned error. It's vital to ensure that your server sends the complete certificate chain, including all intermediate certificates.

Common Causes of the Error

  • Incorrect Date/Time: If your Android device's date and time settings are incorrect, SSL validation may fail.
  • Expired Certificates: Ensure that the SSL certificates are not expired.
  • Incomplete Certificate Chain: The server may not be providing the complete certificate chain, leading to trust issues.
  • Untrusted CA: The certificate may be issued by a CA that is not included in Android’s trusted root store.

Practical Steps to Fix the 'Trust Anchor for Certification Path Not Found' Error

To effectively resolve the 'Trust anchor for certification path not found' error on Android devices, follow these systematic troubleshooting steps:

  1. Check Date and Time Settings: Ensure that your device's date and time are set correctly. Go to Settings > Date & Time and enable Automatic date & time.
  2. Clear Browser Cache: Open your browser, navigate to settings, and clear the cache and cookies. This can resolve issues stemming from outdated cached data.
  3. Update Android OS: Go to Settings > System > System update to check for any available updates. Keeping your OS updated ensures you have the latest root certificates.
  4. Update Your Browser: Ensure that your web browser is updated to the latest version. Browsers may have their own trusted certificate stores.
  5. Verify SSL Certificate: Use the openssl command provided earlier to check the SSL certificate chain.
  6. Install Missing Certificates: If you find that the root CA is missing on your device, consider installing it manually. Download the root certificate from the CA's website and install it on your Android device:
Settings > Security > Install from storage

Follow the prompts to install the downloaded certificate. Ensure that you trust the source of the certificate before installation.

Example of Checking SSL Certificate Chain

Using the command:

echo | openssl s_client -connect yourwebsite.com:443 -showcerts

This command will return the certificate details. Look for lines starting with -----BEGIN CERTIFICATE----- and -----END CERTIFICATE-----. Ensure that the entire chain is present and that no errors are reported.

By following these steps, you can systematically troubleshoot and resolve the 'Trust anchor for certification path not found' error, ensuring a secure browsing experience on Android devices.

CertificateExpiry, issuer, domains (SAN)
ChainIntermediate and root CA validation
TLS ProtocolTLS version and cipher suite
VulnerabilitiesHeartbleed, POODLE, weak ciphers

Why teams trust us

TLS 1.3
supported
Full
CA chain check
<2s
result
30/14/7
days-to-expiry alerts

How it works

1

Enter domain

2

TLS chain verified

3

Expiry date & vulnerabilities

What Does the SSL Check Cover?

SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.

Certificate Details

Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).

Chain of Trust

Full chain verification: from leaf certificate through intermediates to root CA.

TLS Analysis

Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.

Expiry Alerts

Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.

DV vs OV vs EV Certificates

DV (Domain Validation)
  • Confirms domain ownership only
  • Issued in minutes automatically
  • Free via Let's Encrypt
  • Suitable for most websites
  • Most common certificate type
OV / EV
  • Organization (OV) or Extended Validation (EV)
  • Issued in 1-5 business days
  • Costs $50 to $500/year
  • For finance, e-commerce, government sites
  • Increases user trust

Who uses this

DevOps

SSL certificate monitoring

Security

TLS config audit

SEO

HTTPS as ranking factor

E-commerce

customer trust

Common Mistakes

Expired certificateBrowsers block sites with expired SSL. Set up auto-renewal or monitoring.
Incomplete certificate chainWithout intermediate CA, some browsers and bots cannot verify the certificate.
Mixed content on HTTPS siteHTTP resources on an HTTPS page — the browser lock icon disappears, reducing trust.
Using TLS 1.0/1.1Legacy TLS versions have known vulnerabilities. Use TLS 1.2+ or 1.3.
Domain mismatch in certificateThe certificate must cover all site domains, including www and subdomains.

Best Practices

Set up auto-renewalLet's Encrypt + certbot with cron — certificate renews automatically every 60-90 days.
Enable HSTSStrict-Transport-Security header forces browsers to always use HTTPS.
Use TLS 1.3TLS 1.3 is faster (1-RTT handshake) and safer — legacy ciphers removed.
Monitor expiration datesCreate a monitor on Enterno.io — get notified well before expiration.
Verify chain after renewalAfter certificate renewal, confirm that intermediate certificates are installed.

Get more with a free account

SSL certificate monitoring, check history and alerts 30 days before expiry.

Sign up free

Learn more

Sources

Frequently Asked Questions

Quick way to check the chain?

curl -v https://host 2>&1 | grep -i "issuer\|depth\|ssl". Or enterno.io/ssl — shows intermediate + leaf.

LE on Android < 7?

ISRG Root X1 cross-signed via DST Root CA X3. Expired 30 Sep 2021, LE resumed cross-sign — works until 2025+.

App-level vs system-level?

network_security_config — per-app (API 24+). Device-wide — needs rooted device + push CA to /system/etc/security/cacerts/.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.