A certificate chain error means that the browser or a visitor cannot fully verify your website’s SSL certificate. This is almost always because the so-called intermediate certificates are missing or incorrectly installed on the server. The result: visitors see a warning that the connection is not secure, while the certificate itself is actually valid. In this article you’ll read what a certificate chain exactly is, how to recognize the error, and how to fix it.
What is a certificate chain?
An SSL certificate is never issued on its own. It is part of a chain consisting of three parts: the certificate for your own domain, one or more intermediate certificates from the certificate authority, and the root certificate that is trusted by default by browsers. A browser checks this entire chain from bottom to top. If a link is missing, the browser cannot confirm that your certificate ultimately leads back to a trusted root, and a warning appears.
How to recognize a chain error?
Chain errors manifest themselves in different ways, depending on browser and device:
- The message ‘This connection is not private’ or ‘Untrusted certificate’ in the browser, while an SSL checker shows the certificate itself as valid.
- The certificate works fine on desktop, but gives error messages on mobile devices or older operating systems.
- Apps, API connections, or payment providers that refuse connection while the website itself looks normal.
- An online SSL checker explicitly reports ‘incomplete certificate chain’ or ‘missing intermediate certificate’.
This last difference is important: browsers sometimes automatically fill in missing intermediates through caching, so you don’t notice the problem yourself, but other visitors or systems do.
How to fix the error
The solution depends on how you installed the certificate, but the core is always the same: ensure that the complete chain is present on the server.
Check the chain
Run a check with an SSL checker and specifically look whether all intermediates are found, not just the domain certificate.
Download the correct bundle file
When requesting a certificate, the certificate authority usually provides a separate file with intermediate certificates (CA bundle). Make sure you keep this file alongside your domain certificate.
Install certificate and chain together
When installing the certificate, upload both the domain certificate and the CA bundle. In Plesk you can find this under SSL/TLS Certificates for the website, where there is a field for the ‘CA certificate’ alongside the certificate.
Restart the web server
After adjusting the certificate configuration, the web server needs to load the new settings. This usually happens automatically upon saving, but always verify this with a re-test.
Test again
Run the SSL check again and verify that the message about an incomplete chain has disappeared.
If you use Let’s Encrypt via automatic installation, the chain is usually delivered correctly automatically. Chain errors occur more often with manually installed paid certificates where the CA bundle was accidentally skipped.
Preventing chain errors
The best way to prevent chain problems is to automate certificate management as much as possible. Use an automatically issued and renewed certificate wherever possible, so you never have to manually combine files. Additionally, periodically check, for example at every renewal, whether the chain is still complete, especially after a server move or migration to a different hosting environment.
If you’re considering switching to a different provider, make sure the certificate and its associated chain are transferred correctly. You can read more about this at switching to Tandata. For the underlying domain settings, such as linking your domain to the correct server, you can visit domain names.
Frequently Asked Questions
Why does my certificate work in Chrome but not in an app?
Chrome and other browsers often cache intermediate certificates they have seen before, so an incomplete chain goes unnoticed. Apps and standalone systems don’t do this and therefore do get an error message.
Do I need to reinstall the chain with every renewal?
With manual installation, yes, because certificate authorities sometimes change the intermediates. With automated certificates, this usually happens without you having to do anything.
Can a chain error affect email?
Yes, if you use SSL for SMTP, IMAP, or POP3 and reuse the same certificate, an incomplete chain can also lead to warnings or connection problems in email clients. You can find more explanation about this at business email.
Conclusion
A certificate chain error arises from a missing or incorrectly installed intermediate certificate. By installing the complete chain together with your domain certificate and testing regularly with an independent SSL checker, you prevent warnings for visitors and disruptions in connections with other systems.
Was dit artikel nuttig?