How to Fix SSL Errors and "Not Secure" Warnings (2026)

Trace every SSL error — expired certificate, name mismatch, mixed content, incomplete chain — with fixes and auto-renewal

By CloudPicked Review Team•Last updated June 16, 2026•9 min read

How to Fix SSL Errors and "Not Secure" Warnings (2026)

What SSL errors mean
Expired certificate
Name mismatch
Mixed content
Incomplete chain
Other causes
Auto-renewal
Hosting with easy SSL
FAQ

What an SSL error is and why browsers warn

When a browser connects over HTTPS it checks the SSL/TLS certificate is valid and trusted. If something is wrong, the browser shows a warning to protect users — which scares visitors away.

HTTPS uses a certificate to verify site identity and encrypt data
Browsers warn when a certificate is expired, mismatched or untrusted
A red warning page stops users entering data and drives them away
SSL errors hurt both credibility and SEO

Expired certificate (NET::ERR_CERT_DATE_INVALID)

One thing that surprised us: the most common cause is an expired certificate. Certificates have a limited lifespan, so if you do not renew or auto-renewal fails, the site warns immediately.

Check the certificate's expiry date in your panel or browser
Reissue/renew the certificate via your panel (e.g. DirectAdmin)
Enable auto-renewal to avoid lapses, especially 90-day Let's Encrypt
Clear your browser cache after renewing to see the new certificate

Name mismatch (NET::ERR_CERT_COMMON_NAME_INVALID)

This happens when the certificate was issued for one name but the user visits another — for example issued for example.com but accessed via www.example.com, or via the IP.

💡 Key takeaway: Issue the certificate to cover both example.com and www.example.com

Issue the certificate to cover both example.com and www.example.com
Use a Wildcard certificate if you have many subdomains
Set a consistent redirect from www to non-www (or vice versa)
Don't access the site via raw IP — certificates are issued to names
Check the SAN (Subject Alternative Name) includes the name you use

Mixed content — no padlock despite having SSL

Sometimes SSL is installed but the padlock is missing or shows "partly not secure" because the page still loads some resources over HTTP — images, scripts or CSS.

Change internal resource links from http:// to https:// (or use //)
Use a plugin or search-replace to fix old links in the database
Add a forced-HTTPS redirect in .htaccess
Check the browser console for any remaining HTTP resources
Set your site's primary URL to https in the CMS settings

Incomplete certificate chain

Some browsers or phones show an error because the chain is incomplete — the intermediate certificate linking to the root CA is missing, so trust cannot be verified.

Install the intermediate (CA bundle) alongside the main certificate
Use a panel that handles the chain automatically, e.g. DirectAdmin
Test with an SSL checker to confirm the chain is complete

Other causes of SSL errors

If the above does not fix it, the issue may be on the user's device or a small overlooked setting. Run through these common remaining causes.

The user's device clock is wrong, breaking date validation
A self-signed certificate the browser does not trust
Antivirus/firewall software intercepting HTTPS connections
Old browser or CDN cache still remembering the previous certificate
Outdated TLS version the browser no longer supports

Prevent errors with SSL auto-renewal

In practice, most SSL problems come from forgetting to renew. Enabling auto-renewal is the best prevention, especially for Let's Encrypt certificates which last 90 days and need frequent renewal.

Enable auto-renew in your panel (DirectAdmin supports it)
Set an expiry reminder as a backup
Verify the new certificate is actually installed after renewal
Use a trusted issuer supported by all browsers

Choose hosting that makes SSL easy

The easiest way to avoid SSL errors is hosting that installs free SSL, auto-renews and handles the chain for you. From our testing, our recommended provider asiagb.com offers free SSL with auto-renewal through DirectAdmin, plus SSD storage, servers in Thailand/Singapore, 99% uptime and 24-hour Thai support that genuinely helps with setup.

Choose a host that provides free SSL with auto-renewal
Look for a panel that installs SSL in a few clicks, e.g. DirectAdmin
It should handle the chain and force HTTPS automatically
Support that can fix SSL errors promptly
99% uptime and servers near Thai visitors aid both speed and stability

Frequently Asked Questions

My site shows "Not Secure" even though SSL is installed

This is usually mixed content — the page still loads some images, scripts or CSS over HTTP. Change resource links to https, force a redirect to HTTPS, and check the browser console for anything remaining.

My SSL keeps expiring — how do I fix it permanently?

Enable auto-renewal in your panel, especially for 90-day Let's Encrypt certificates that renew often. Using a host that installs and auto-renews free SSL through DirectAdmin removes the problem entirely.

SSL errors only appear on mobile — why?

Usually an incomplete chain (missing intermediate). Some desktops tolerate it but mobiles are stricter. Install the full CA bundle and test with an SSL checker on both devices.

Is SSL necessary for SEO?

Yes. HTTPS is a Google ranking factor and browsers warn that non-SSL sites are not secure, driving users away. Having a valid, auto-renewing certificate matters for both ranking and credibility.