In this article · 9 sections
- 1. "Not secure" in the address bar
- 2. Certificate expired
- 3. Certificate name mismatch
- 4. Mixed content
- 5. Too many redirects (redirect loop)
- 6. Old browser or device errors
- After fixing
- Frequently Asked Questions
- Is free SSL good enough for business websites?
- Does HTTPS affect SEO?
- How often should I check SSL?
- Need SSL fixed?
An SSL certificate encrypts the connection between visitors and your website and enables HTTPS. When something is wrong, browsers show warnings like "Not secure" or a full-page error. Most visitors leave immediately. Here are the common problems and their fixes. (For why HTTPS matters, see our SSL guide.)
1. "Not secure" in the address bar
Cause: the page is loading over HTTP instead of HTTPS, or no certificate is installed.
Fix: install a certificate (most hosts offer free SSL) and redirect all HTTP traffic to HTTPS with a 301 redirect in .htaccess or your hosting panel.
2. Certificate expired
Cause: free certificates usually last about 90 days and renew automatically. Renewal can fail if DNS changed, the domain moved, or a firewall blocks validation.
Fix: reissue/renew from your hosting panel's SSL section; check DNS points to the correct server.
3. Certificate name mismatch
Cause: the certificate covers example.com but not www.example.com (or vice versa), or a subdomain.
Fix: issue a certificate covering both versions and redirect one to the other consistently.
4. Mixed content
Cause: the page loads over HTTPS but includes images, scripts or stylesheets via http://. Browsers block insecure scripts and may show a broken padlock.
Fix: update hard-coded URLs to https:// or relative paths — in templates, database content (blog posts often contain old image URLs) and settings. The browser console lists every mixed content resource.
5. Too many redirects (redirect loop)
Cause: HTTPS redirect rules conflict with a CDN or proxy (for example, the CDN connects to your server over HTTP while your server keeps redirecting to HTTPS).
Fix: make redirect rules aware of proxy headers (such as X-Forwarded-Proto), or set the CDN to full/strict SSL mode.
6. Old browser or device errors
Very old devices may not support modern certificates. Usually nothing to fix on your side; ensure your server uses standard certificate chains.
After fixing
- Update canonical tags, sitemap and internal links to HTTPS.
- Check Search Console's HTTPS report.
- Test forms and payment pages.
Frequently Asked Questions
Is free SSL good enough for business websites?
Yes, for encryption. Paid certificates add organisation validation and warranties, which some businesses prefer.
Does HTTPS affect SEO?
HTTPS is a lightweight ranking signal, and browser warnings on HTTP pages hurt trust and conversions.
How often should I check SSL?
Monitor automatically or check monthly; renewal failures are common after DNS or hosting changes.
Need SSL fixed?
Joboo Web fixes SSL, redirects and mixed content issues. See hosting and support or contact us.