ERR_SSL_UNRECOGNIZED_NAME_ALERT is a common SSL error that blocks visitors from reaching your HTTPS site. It usually appears right after you install an SSL certificate, or after you change DNS or hosting settings. The error means the server didn’t recognize the hostname the browser asked for during the TLS handshake. In most cases, the fix is a matter of aligning your domain, DNS records, and SSL certificate on the same server.
What Causes ERR_SSL_UNRECOGNIZED_NAME_ALERT?
The browser sends the domain name it wants during the handshake, a feature called Server Name Indication (SNI). If the server can’t match that name to a site and certificate, it rejects the connection. Common causes include:
- No SSL certificate for the domain: The certificate is missing, or it covers a different domain or subdomain.
- DNS pointing to the wrong server: Your A or CNAME records send traffic to an IP address where the domain isn’t configured.
- Missing virtual host entry: The web server doesn’t know which site to serve for that domain.
- Hosting security features: Some hosts enable add-ons, such as SiteLock, that interfere with HTTPS traffic.
Step 1: Check Your SSL Setup
Start by testing your site on SSL Labs. It reports critical certificate and configuration problems. If it shows errors, your hosting provider or SSL provider can usually resolve them quickly. Also confirm that your certificate covers both the root domain and the www version if you use both.
Step 2: Install a Free SSL Certificate
If your site doesn’t have a valid certificate yet, install one. For WordPress sites, the WP Encryption plugin can generate and install a free certificate from your dashboard. Once installed, make sure the certificate covers the exact domain you’re visiting.
Step 3: Disable Hosting Security Add-Ons
Some hosting control panels include security features that can interfere with SSL. If your host provides SiteLock or a similar service:
- Log in to your hosting control panel.
- Find the SiteLock feature (or the equivalent in your host’s panel).
- Disable it, then reload your site.
If the error goes away, contact your host to find out whether the feature can be configured for HTTPS or should stay off.
Step 4: Correct Your DNS Records
If the error continues, your DNS records may point to the wrong place. In cPanel, open Advanced DNS Editor or Zone Editor and scroll to the A and CNAME records at the bottom of the page.
- A record: Point the domain to your server’s IP address. Use the same IP as your other DNS records, such as autoconfig, whm, or autodiscover, or the IP your hosting provider gave you.
- CNAME record for www: Point the
wwwname to your non-www domain.
Make sure you don’t have duplicate or conflicting records for the same name. If you’re unsure which IP address is correct, ask your hosting provider before you change it.
Step 5: Wait for DNS to Update
After you save DNS changes, allow time for them to propagate. This often takes a few minutes but can take up to 24 to 48 hours. You can check progress with a tool such as whatsmydns.net. Once your domain resolves to the correct server, reload your HTTPS site and confirm the padlock appears.
When to Get Further Help
If the error persists after these steps, contact your hosting support and give them the exact domain, the error text, and what you changed. Ask them to confirm that:
- The domain is added to the correct site or virtual host on the server.
- The SSL certificate is installed for that domain and is valid.
- No security add-on is blocking HTTPS.
Frequently Asked Questions
Is this error caused by a virus or hack?
Usually not. It’s almost always a configuration mismatch between your domain, DNS, and SSL certificate.
Why did the error appear right after I installed SSL?
The certificate may not match the domain, or the server may not be serving that domain over HTTPS yet. Recheck the certificate and DNS records.
Will changing DNS cause downtime?
It can, briefly, if the records point to the wrong server during propagation. Make changes during a low-traffic period when possible.
