SSL Certificate Not Trusted means the browser cannot verify the identity of a website. The secure HTTPS connection is blocked because the certificate cannot be validated.
This usually happens when the certificate chain is incomplete, the certificate is self-signed, expired, or installed incorrectly. Most SSL trust errors occur because the server does not provide the full certificate chain.
Quick Fix
- Check if the SSL certificate is expired.
- Confirm it was issued by a trusted Certificate Authority.
- Install the full certificate chain (including intermediates).
- Ensure the certificate matches the domain.
- Verify system date and time.
- Clear browser SSL cache.
What “SSL Certificate Not Trusted” Actually Means
When a browser connects to an HTTPS website, it validates the SSL certificate before establishing encryption. The browser checks:
- Who issued the certificate
- Whether that issuer is trusted
- Whether the certificate is still valid
- Whether it matches the requested domain
If any of these checks fail, the browser cannot trust the certificate. The connection is then blocked and the browser displays an SSL warning.
Why SSL Certificate Not Trusted Happens
Self-Signed Certificate
Self-signed certificates are not issued by trusted authorities. Browsers cannot verify them automatically. They are acceptable for internal testing but not for public websites.
Missing Intermediate Certificates
SSL certificates rely on a trust chain. If the server sends only the main certificate but not the intermediate certificates, the browser cannot verify the authority. This is the most common cause.
Expired Certificate
Every certificate has a strict expiration date. Once expired, the browser rejects it immediately.
Domain Name Mismatch
The certificate must match the exact domain. For example, if a certificate is issued for example.com but the user visits www.example.com, the mismatch breaks validation.
Security Software Interception
Some antivirus tools intercept HTTPS traffic and inject their own certificates. If the browser does not trust those certificates, the error appears.
How to Fix SSL Certificate Not Trusted (Server Side)
Step 1 — Inspect the Certificate
Open the website in Chrome, click the padlock icon, and view the certificate information. Verify the expiration date, issuer name, and domain coverage.
Step 2 — Install the Complete Certificate Chain
Servers must provide the entire certificate chain. This usually includes the server certificate, intermediate certificate(s), and the CA bundle. If intermediate certificates are missing, trust cannot be established.
Step 3 — Replace Self-Signed Certificates
If the certificate is self-signed, replace it with one issued by a trusted Certificate Authority (CA). Public websites should always use trusted certificates.
Step 4 — Verify Domain Coverage
The certificate must cover all used hostnames (e.g., example.com, www.example.com, and subdomains if necessary). Wildcard or multi-domain certificates may be required. If a hostname is missing, Chrome reports it as a name mismatch; see our guide to fixing ERR_CERT_COMMON_NAME_INVALID.
Step 5 — Restart Web Server
After installing the certificate, restart Apache or Nginx and clear your CDN cache. Old certificates may remain cached until services reload.
Fixing the Error as a Visitor
If you are not the site owner, the problem usually cannot be fixed locally. However, you can try:
- Checking your system date and time
- Clearing your browser cache
- Testing another network
- Disabling antivirus HTTPS scanning temporarily
If the warning persists, the website owner must correct the SSL configuration.
Advanced Troubleshooting
Check Certificate Chain Order
The order of certificates in the chain matters. Incorrect ordering can break validation.
Verify SNI Configuration
Servers hosting multiple domains use Server Name Indication (SNI). Incorrect configuration may deliver the wrong certificate.
Test Without CDN
If a CDN is used, temporarily bypass it to test the origin server directly. Behind Cloudflare in Full (strict) mode, an untrusted origin certificate shows up as Cloudflare Error 526 Invalid SSL Certificate rather than a browser warning.
Check Operating System Trust Store
Very old operating systems may lack updated trusted root certificates.
Does This Error Affect SEO?
Yes. Users will see security warnings, trust decreases rapidly, and search engines prefer fully secure websites. SSL errors heavily damage credibility, user experience, and search rankings.
Prevention Best Practices
- Enable automatic SSL renewal.
- Monitor certificate expiration.
- Install full certificate chains.
- Test HTTPS after server migrations.
- Avoid self-signed certificates on public sites.
When to Contact Support
Contact your hosting provider if the certificate appears valid but the browser still rejects it, if you cannot access server configuration, or if CDN SSL configuration conflicts with the origin server. Provide certificate details and error screenshots.
FAQ
Is SSL Certificate Not Trusted dangerous?
It indicates the browser cannot verify the identity of the website, which means the connection might not be private or secure.
Can antivirus cause SSL trust errors?
Yes. Some antivirus programs intercept HTTPS traffic and replace the certificate with their own, which the browser may not trust.
Does reinstalling SSL fix the problem?
If the issue is caused by missing intermediate certificates or incorrect installation, reinstalling the full chain usually resolves it.
Why does the error appear on some devices only?
Different devices and operating systems maintain different trusted certificate stores. An older device might lack the root certificate needed to verify your site.
How long does fixing the issue take?
Once the root cause is identified, the fix (like installing missing intermediates or renewing the certificate) usually takes less than 30 minutes.
Final Thoughts
SSL Certificate Not Trusted is a certificate validation problem. The most common causes are missing intermediate certificates, self-signed SSL, or expired certificates. Correct installation and ensuring a complete trust chain resolves the issue in most cases.
Related SSL Errors
- NET::ERR_CERT_AUTHORITY_INVALID — Causes and Fix
- Mixed Content Error — How to Fix HTTPS Issues
- SSL Handshake Failed — Causes and Solutions
- ERR_SSL_PROTOCOL_ERROR — Step-by-Step Fix
- Too Many Redirects After SSL — Fix Redirect Loop
- Your Connection Is Not Private
Hi, I’m Alex — the person behind ErrorRescue.
I’ve been working with websites, servers, and hosting for over 8 years. Most of my experience comes from troubleshooting real problems on WordPress sites, VPS and shared hosting environments, and Cloudflare setups. I’ve dealt with everything from SSL certificate failures and DNS misconfigurations to 504 timeouts, memory exhaustion errors, and Cloudflare 5xx issues.
I started ErrorRescue because I got tired of seeing generic, outdated, or incomplete error guides. My goal is to write clear, practical fixes based on what actually works in production — not just theory. Every guide here is tested against common server setups (Apache, NGINX, Cloudflare, and popular WordPress stacks).
When I’m not fixing sites, I’m usually reviewing new hosting configurations or updating existing guides so they stay accurate.