An SSL error is one of the most visible website faults. Browsers show a full-page warning before a visitor even reaches the site, and many people leave immediately. For a business, that warning reads as "this site is not safe", even when the cause is a simple expired certificate.
Here are the common SSL faults and how each is fixed.
"Your connection is not private"
This appears when the certificate is expired, issued for a different domain, or not trusted. Causes include:
- The certificate expired because auto-renewal failed.
- The certificate is for
example.combut the site is opened atwww.example.com, and the certificate does not cover both. - A self-signed certificate is in use.
- The certificate chain is incomplete, so some browsers do not trust it.
The fix is to install a valid certificate that covers both the bare domain and www, with the full chain, and to verify auto-renewal works.
"Not Secure" in the address bar
This usually means the site still loads over http:// or contains mixed content — parts of the page loaded over plain HTTP while the page itself is HTTPS. Mixed content appears on older sites that hard-code http:// image, script or stylesheet URLs.
Fixing it means:
- Forcing HTTPS with a redirect.
- Updating hard-coded
http://links in the database and theme files. - Checking the browser console for exactly which resources are insecure.
Certificate expired even with auto-renewal
Let's Encrypt certificates last 90 days and renew automatically — unless something blocks it. Common blockers in Kenya:
- The domain no longer points to the server, so validation fails.
- Port 80 is closed, blocking HTTP validation.
- The hosting account changed and the renewal hook did not run.
- A firewall rule blocks the ACME challenge.
The symptom is a site that worked for months and then breaks on a specific day. Checking renewal logs tells you why within minutes.
The wrong certificate on the wrong domain
On shared servers with many sites, a request can land on the wrong virtual host and serve a certificate for another domain. The fix is a correct virtual host configuration for each domain, with its own certificate and a proper ServerName.
This is common when domains are added to a server without updating the web server config, especially when the DNS was already switched.
After the fix
A proper SSL fix should confirm:
- The certificate covers the bare domain and
www. - The full chain is installed.
- HTTPS is forced with a permanent redirect.
- No mixed-content warnings remain.
- Renewal works automatically.
Test with an online SSL checker and in a fresh browser, not only in one you already use, because cached exceptions hide the problem.
What it costs
In Kenya in 2026, SSL installation and error repair typically runs KES 2,000 to 8,000. A free Let's Encrypt certificate is often enough; paid certificates add warranty and support rather than better encryption. If the error came from a misconfigured server, expect the work to include the virtual host cleanup, not just the certificate.
Do not accept "just click proceed" as a fix. The warning is the signal that visitors are being turned away.
Need this done for you?
MUKI handles website repair, SSL, business email, POS installation, biometric attendance and property software onboarding across Nairobi, Kiambu, Ruiru and Thika.
Related service: Website repair, SSL and business email →