My site has a valid certificate, but Chrome marks it as insecure.

I tried my site using Brave and Firefox, and both mark it as secure.

I also ran this online test, and everything looks fine:

https://mxtoolbox.com/Pro/#/lookup/https:beauchamp.me

I am running Version 69.0.3497.100 (Build officiel) (64 bits) on a Apple MacBook phiên bản Pro.

In some threads I read this can happen if the date and time on my computer are incorrect, but they are correct.

asked Oct 18, 2018 at 1:44

4

I found what it was. After updating Chrome and restarting it, the lock sign was fine. Chrome did not mark my site as insecure anymore. However, as soon as I accessed my server on another port with a self-signed certificate, and I accepted browsing despite the self-signed certificate warning given in Chrome, my site got marked as insecure, even on the tab where I was accessing the standard port (443).

answered Oct 18, 2018 at 15:40

4

In my case, some of the images (or another resource) inside my trang web using http ví Chrome (and other browsers) say "Connection is not secure" while Certificate (valid)

answered Dec 21, 2020 at 2:04

For mạ, the root cause turned out lớn be that I was referencing the wrong cert tệp tin.

Everything was working well, until one day ALL of my sites suddenly became Not Secure. All the certificates were valid but I was referencing the cert.pem tệp tin instead of the fullchain.pem tệp tin.

In each of my server.js files I replaced:

var cert_url = '/etc/letsencrypt/live/.com/cert.pem';

with this:

var cert_url = '/etc/letsencrypt/live/.com/fullchain.pem';

This resolved the issue.

Source: https://community.letsencrypt.org/t/invalid-intermediate/91378/3

Peregrino69

4,8143 gold badges23 silver badges31 bronze badges

answered Oct 1, 2021 at 19:56

3

This is what worked for mạ.

First, before I configured SSL for my localhost trang web server I had previously enabled "Allow invalid certificates for resources loaded from localhost." in chrome://flags.

Later on I configured SSL properly and couldn't get the green lock lớn appear even though my certificate was valid according lớn Chrome.

After trying solution after solution eventually I went into chrome://flags and disabled the "Allow invalid certificates for resources loaded from localhost." flag, restarted Chrome, and poof - green lock.

Maybe there is a cache of some sort at play with what sites are Secure/Not Secure once that flag is enabled - not sure - but this fixed my issue.

answered Mar 24, 2022 at 14:51

I just had this exact same issue while creating a new certificate for a new trang web, I opened a tab lớn test the certificate and it was wrong, then I fixed it, refreshed the page and the message persisted, it turns out the problem was that refreshing the page on chrome doesn't refresh the lock icon, after I closed the tab and opened a new one on the same site the warning went away.

Since you don't want lớn reset all of your settings (I don't blame you), here is a liên kết on how lớn find and delete the specific certificate for your site:

http://lists.gno.org/cert-maint-mac-10.5.8/

I don't have a Mac ví I wasn't able lớn actually go through the directions lớn test it.

answered Oct 18, 2018 at 15:27

You must log in lớn answer this question.

Not the answer you're looking for? Browse other questions tagged

.