Two different warnings get called "Not secure." One is a small label next to your web address. The other is a full-page warning that says "Your connection is not private" and hides your site behind a button. They have different causes. This guide takes you from the symptom to a fix you can try yourself, and says where to stop and call someone.
Step 1: Is it your site, or your device?
Open the site on a second device, such as a phone using mobile data instead of your Wi-Fi. If it loads fine there, the problem is on the first device or network, not on your site.
Chrome's help says the cause of "Your connection is not private" can be the site, the network or the device (Chrome Help, check a site's connection). Its list of device-side fixes includes: correct the date and time (a wrong clock produces the "Your clock is ahead" or "Your clock is behind" warning), try an Incognito window, turn off extensions, update the operating system, and check whether antivirus software is scanning secure traffic. On public Wi-Fi, a sign-in page may need to load first. If you still get the error, Chrome's advice is to contact the website owner. That may be you. The list is on Chrome Help, common error messages.
Step 2: A small "Not secure" label
Chrome has marked every page served over plain HTTP as "Not Secure" since version 68, in July 2018 (Chromium security team). So this label usually means one of two things:
- People reach the HTTP address. Type your address with
https://in front. If that works, your host needs to send everyhttp://visit to thehttps://version. This is a setting at your host or in your site settings. Ask your host for "redirect HTTP to HTTPS." - The page is HTTPS but loads something over HTTP. This is called mixed content. Browsers upgrade images, video and audio to HTTPS, and block scripts, style sheets and similar files (MDN on mixed content). View the page source, search for
http://, and change each file link tohttps://. If the file is not offered over HTTPS, host a copy yourself or remove it.
Step 3: The full-page warning
If your device checks out, the certificate is the likely cause. A certificate is the file that proves your address belongs to your site, and it has an end date. Read the code under "Advanced." Chrome's help lists, for example, NET::ERR_CERT_AUTHORITY_INVALID and messages about invalid names, and the clock warning above is the date error. The common site-side causes:
- The certificate expired. It has to be renewed or replaced. Cloudflare's guide for the cipher mismatch error lists an expired custom certificate as a cause, with replacement as the fix.
- The certificate does not cover that address. Cloudflare's universal certificates cover the root domain and first-level subdomains, so
shop.example.comis covered buttest.dev.example.comis not. - The certificate is not issued yet. After a domain is added to Cloudflare, its certificate can take up to 24 hours to become active. A DNS record that is not proxied is also not covered.
- A redirect loop. The browser says "too many redirects." With Cloudflare's Flexible mode, the cause is an origin that redirects every HTTP request to HTTPS; the fix is to remove that redirect or switch the mode.
Sources: Cloudflare, cipher mismatch, Universal SSL and too many redirects. If your site is hosted elsewhere, the cause list is similar but the buttons are different.
Why this keeps happening
Certificates are getting shorter-lived. The CA/Browser Forum, the group that sets the rules for certificate authorities, voted in April 2025 to cut the maximum lifetime from 398 days to 47 days, in steps from March 2026 to March 2029 (ballot SC-081v3). Renewing by hand gets harder with each step. Choose a host that renews for you, and do not rely on reminder emails: Let's Encrypt, a free certificate authority, has ended its expiration emails (Let's Encrypt).
Check your fix
Reload in an Incognito window. For a deeper look, the free Qualys SSL Labs server test grades a public site's secure setup. We also offer a free website check that reports whether your certificate is valid, how many days remain, and whether visitors are sent to the https address. A person reads the results before they reach you.
When to call someone
- You cannot log in to your host, your domain registrar or your DNS settings, or you do not know who can.
- The fix means changing DNS records. Screenshot every record first, and leave the email records alone. A wrong change can stop email as well as the site.
- You take payments or logins on the site and the warning is still there after the steps above. Do not ask customers to click past a warning.
- The error comes back every few months. That points to a renewal that is not automatic.
Whoever you call, ask for three things in writing: what was wrong, what was changed, and how renewal now happens.
Where we fit
We build sites for Mount Pleasant and Charleston businesses on the owner's own free Cloudflare Pages account, so the logins stay with you. Our Website Care plan is $99 a month and includes a weekly check of the certificate. It is listed as IN PROGRESS on our Truth Center: the checks are written and tested, and no customer is enrolled yet. Text Chris at 843-754-8988 if you are stuck on any step above.