Fixing SSL Certificate Errors
SSL certificate errors can prevent visitors from accessing your website and damage trust. This guide covers the most common SSL issues on GoSiteMe and how to resolve them quickly.
Common SSL Errors
| Error | What It Means |
|---|---|
| NET::ERR_CERT_DATE_INVALID | The SSL certificate has expired. |
| ERR_CERT_COMMON_NAME_INVALID | The certificate doesn't match the domain name. |
| ERR_CERT_AUTHORITY_INVALID | The certificate was issued by an untrusted authority. |
| Mixed Content Warning | The page loads some resources over HTTP instead of HTTPS. |
| ERR_SSL_PROTOCOL_ERROR | SSL/TLS handshake failed—usually a server configuration issue. |
Fix: Expired Certificate
GoSiteMe's free Let's Encrypt certificates renew automatically. If renewal failed:
- Go to Dashboard → Hosting → SSL/TLS.
- Click Renew Certificate.
- If renewal fails, check that your domain's DNS A record points to GoSiteMe's servers (listed in the DNS panel).
- Ensure no firewall rules are blocking the Let's Encrypt validation servers.
- Try again after DNS propagation (up to 24 hours for recent DNS changes).
Fix: Domain Name Mismatch
This occurs when your SSL certificate covers example.com but you are visiting www.example.com (or vice versa).
- Navigate to SSL/TLS and check which domains the certificate covers.
- Click Reissue Certificate and ensure both
example.comandwww.example.comare included. - Alternatively, set up a redirect so one version always redirects to the other.
Fix: Mixed Content
Mixed content happens when your HTTPS page loads images, scripts, or stylesheets over HTTP.
- Open your browser's Developer Tools (F12) and check the Console for mixed content warnings.
- Update the offending URLs from
http://tohttps://. - For WordPress sites, use the Better Search Replace plugin to find and replace
http://yourdomain.comwithhttps://yourdomain.comacross the database. - Enable Automatic HTTPS Rewriting under SSL/TLS → Edge Certificates to fix mixed content at the CDN level.
Fix: SSL Protocol Error
- Clear your browser cache and cookies.
- Try an incognito/private window.
- Verify the correct TLS versions are enabled: Go to SSL/TLS → Settings and ensure TLS 1.2 and 1.3 are active.
- If using Cloudflare or another proxy, ensure SSL mode is set to "Full (Strict)".
Still Need Help?
If the issue persists, run Security → SSL Diagnostic in your dashboard, which checks certificate validity, chain completeness, and protocol compatibility. Share the diagnostic report with GoSiteMe support for fast resolution.