Fix SSL Certificate Error

The Problem

Visitors see a security warning — "certificate not trusted", "name mismatch", "certificate expired", or similar — even though you think SSL is set up, and you need to know exactly what's wrong and get it fixed.

About this problem

SSL errors come in several distinct flavours that all look similarly alarming to a visitor but have different causes: a name mismatch means the certificate doesn't cover the exact domain/subdomain being visited, an incomplete chain means intermediate certificates are missing, and an untrusted certificate often means it's self-signed or from an unrecognised authority. Diagnosing which one you actually have is the first step, since the fix is different for each.

This often shows up right after a server migration, a change in how a site is proxied (adding Cloudflare, for example), or when a certificate was issued for the wrong domain variant (www versus non-www).

What's Included

• Identifying the exact type of SSL error occurring
• Checking certificate coverage (domain names, chain completeness) against what's actually being served
• Correcting the certificate installation or reissuing it to cover the right domain(s)
• Verifying the error is resolved from a fresh browser session, not just a cached one

What's NOT Included

• Certificate authority account/billing issues for paid certificates
• Fixing errors caused by a visitor's own outdated device/browser (flagged if that's the actual cause)
• Ongoing certificate monitoring (see server monitoring/alerts service)

How It Works

1. Reproduce the exact error and identify its specific type (name mismatch, chain incomplete, untrusted/self-signed, expired).
2. Check what domains/subdomains the current certificate actually covers against what's being requested.
3. Check the certificate chain is complete, including any required intermediate certificates.
4. Reissue or reinstall the certificate correctly to resolve the specific identified issue.
5. Test from a fresh, uncached browser session (or an SSL checker tool) to confirm the error is genuinely gone.

In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.

Frequently Asked Questions

What does 'your connection is not private' mean?

It's a browser's way of flagging an SSL certificate problem — commonly a name mismatch, an untrusted/self-signed certificate, or an expired one — the exact cause determines the fix.

Why does my SSL error only show on some browsers or devices?

Different browsers cache certificates differently and some older devices don't trust newer certificate authorities, which can make an error appear inconsistent across devices.

Can adding Cloudflare cause SSL certificate errors?

Yes, if the SSL mode in Cloudflare doesn't match how your origin server is actually configured, it can produce certificate or redirect errors — this is checked specifically when Cloudflare's involved.

What is a 'certificate name mismatch' error?

It means the certificate being served doesn't cover the exact hostname being visited (for example, it covers yourdomain.com but not www.yourdomain.com), and needs reissuing to include both.

Will visitors lose trust in my site because of an SSL error?

Very likely — most visitors leave immediately when they see a security warning, which makes this worth fixing quickly rather than leaving it.

Can an SSL error affect my search engine rankings?

Indirectly yes, since a flagged "not secure" site can see increased bounce rates, and Google has in the past taken direct action against sites with serious certificate problems.