SSL Certificate Chain Errors: Why Some Devices Trust Your Site and Others Do Not
Understand root, intermediate and server certificates, then fix incomplete-chain errors without guesswork.

Your server certificate is rarely signed directly by a root certificate. It is signed by an intermediate CA, which links it to a root already trusted by the browser or operating system. If the server fails to send that intermediate, newer desktops may appear fine while older phones, API clients or embedded devices fail.
Typical symptoms
- “Unable to get local issuer certificate” in command-line clients.
- A mobile app fails while Chrome succeeds.
- Monitoring reports an incomplete chain or extra download.
The correct installation
Install the leaf certificate with the CA-provided intermediate bundle in the documented order. Do not include the root certificate unless your server platform specifically requires it. Restart or reload the web service, then test the public endpoint rather than only inspecting local files.
Diagnose methodically
Use Enet's SSL checker and compare the presented chain with your CA download. If you are creating a new request, generate it with the CSR generator, then confirm the issued certificate matches it using the CSR matcher. Managed installation is available with every certificate purchased through Enet SSL.
Share this article
Was this article helpful?
Your vote helps us write better guides.
