General SSL errors
Starting September 9, 2024, visitors that try to connect to your website using older devices - for example, Android 7.0 and earlier - have access problems or reach security warnings.
The fastest way to resolve this issue is to change your certificate to use Google Trust Services as the certificate authority. Refer to the migration guide to learn how to proceed with each certificate type.
Until Cloudflare provides an SSL certificate for your domain, the following errors may appear in various browsers for HTTPS traffic:
- Firefox:
_ssl_error_bad_cert_domain/This connection is untrusted - Chrome:
Your connection is not private - Safari:
Safari can't verify the identity of the website - Edge / Internet Explorer:
There is a problem with this website's security certificate
Even with a Cloudflare SSL certificate provisioned for your domain, older browsers display errors about untrusted SSL certificates because they do not support the Server Name Indication (SNI) protocol ↗ used by Cloudflare Universal SSL certificates.
To solve, determine if the browser supports SNI ↗. If not, upgrade your browser.
Cloudflare Universal SSL certificates only cover the apex domain (example.com) and one level of subdomains (blog.example.com). If visitors to your domain observe errors accessing a second level of subdomains in their browser (such as dev.www.example.com) but not the first level of subdomains, resolve the issue using one of the following methods below.
- Purchase an advanced certificate that covers
dev.www.example.com. - Upload a Custom SSL certificate that covers
dev.www.example.com. - Enable Total TLS.
- If you have a valid certificate for the second level subdomains at your origin web server, change the DNS record for
dev.wwwto DNS Only (grey cloud).
All active Cloudflare domains are provided a Universal SSL certificate. If you observe SSL errors and do not have a certificate of Type Universal within the Edge Certificates tab of the Cloudflare SSL/TLS app for your domain, the Universal SSL certificate has not yet provisioned.
Our SSL vendors verify each SSL certificate request before Cloudflare can issue a certificate for a domain name. This process may take anywhere from 15 minutes to 24 hours. Our SSL certificate vendors sometimes flag a domain name for additional review.
If your Cloudflare SSL certificate is not issued within 24 hours of Cloudflare domain activation:
- If your origin web server has a valid SSL certificate, temporarily pause Cloudflare, and
- Contact Support and provide a screenshot of the errors.
Temporarily pausing Cloudflare will allow the HTTPS traffic to be served properly from your origin web server while the support team investigates the issue.
If your domain is on a full setup, review your DNS records.
Cloudflare SSL/TLS certificates only apply for traffic proxied through Cloudflare. If SSL errors only occur for hostnames not proxied to Cloudflare, proxy those hostnames through Cloudflare.
If your domain is on a partial setup, confirm whether you have CAA DNS records enabled at your current hosting provider. If so, ensure you specify the Certificate Authorities that Cloudflare uses to provision certificates for your domain.
Visitors to your site observe an OCSP response error.
This error is either caused by the browser version or an issue requiring attention by one of Cloudflare’s SSL vendors. In order to properly diagnose, contact Support with the following information provided by the visitor that observes the browser error:
- The output from https://aboutmybrowser.com/ ↗ .
- The output of
https://<YOUR_DOMAIN>/cdn-cgi/tracefrom the visitor’s browser.
The HSTS headers (Strict-Transport-Security and X-Content-Type-Options) in the response do not match the configuration settings defined in your HSTS settings.
You may have configured HTTP Response Header Modification Rules that are overriding the HSTS header values defined in the SSL/TLS app.
- Go to Rules > Transform Rules.
- Under HTTP Response Header Modification, check the existing rules for a rule that is setting the value of one of the HSTS headers (
Strict-Transport-SecurityorX-Content-Type-Options). - Delete (or edit) the rule so that the HSTS configuration settings defined in the SSL/TLS app are applied.
- Repeat this procedure for the other HSTS header.
You are getting the error NET::ERR_CERT_COMMON_NAME_INVALID in your browser.
- Make sure that you are using a browser that supports SNI (Server Name Indication) ↗. Refer to Browser compatibility for more details.
- Ensure that the hostname you are accessing is set to proxied (orange cloud) in the DNS tab of your Cloudflare Dashboard.
- If the hostname you are accessing is a second level subdomain (such as
dev.www.example.com), you’ll need to either:- Purchase an advanced certificate that covers
dev.www.example.com. - Upload a Custom SSL certificate that covers
dev.www.example.com. - Enable Total TLS
- Purchase an advanced certificate that covers
To avoid SSL errors with the Cloudflare dashboard when using Kaspersky
Antivirus, allow dash.cloudflare.com in Kaspersky.