SSL Certificate Chain Errors: Causes and Fixes
Certificate chain errors are some of the trickiest SSL problems to debug because your site may work fine in most browsers but fail for some users, mobile apps, or API clients. Understanding certificate chains is essential for anyone managing TLS certificates.
What is a Certificate Chain?
A certificate chain (also called a trust chain) is a series of certificates linking your domain certificate to a Root CA that browsers inherently trust:
Common Chain Errors
UNABLE_TO_GET_ISSUER_CERT_LOCALLYMissing intermediate certificate in the chainCERT_UNTRUSTEDSelf-signed cert or intermediate not in browser trust storeUNABLE_TO_VERIFY_LEAF_SIGNATUREChain breaks — intermediate cannot be verified against rootCERTIFICATE_VERIFY_FAILEDGeneral chain verification failureERR_CERT_AUTHORITY_INVALIDChrome: issuer not recognized as trusted CADiagnose Your Chain
You should see a chain like:
If you only see one "s:/i:" pair, your intermediate certificate is missing from the server configuration.
Fix: Build the Full Chain
Where to get the intermediate certificate: download from your CA's documentation page. For Let's Encrypt, use the ISRG Root X1 chain. For DigiCert, use their intermediate repository.
Configure Your Web Server
Why Mobile Clients Are More Sensitive
Desktop browsers use a technique called "AIA Fetching" (Authority Information Access) to automatically download missing intermediate certificates. Mobile apps, IoT devices, and server-to-server API clients often do not — they will fail with a chain error even when the same site works in Chrome. Always configure the complete chain on the server side.
Check your chain now
Use the CertNotify SSL Checker to verify your certificate chain is complete and properly ordered. Takes 5 seconds.