Why my site which uses "Let's Encrypt" is marked as "not safe" by Chrome?

Posted May 11, 2017 13.2k views
NginxLet's EncryptUbuntu 16.04

Hi, I have successfully installed Let’s Encrypt and Firefox marks my website as safe (green padlock). But Chrome marks my site as not safe. Why is that? Did I do something wrong? I followed this guide [1] to the end.

Is it possible to fix this? Should I need to get a non-free certificate?


  • Depends, chrome might be a bit stricter. About which site are we talking?
    You could check why chrome doesn’t mark it as safe by checking the certificate (left upper corner) or the console. To open the console, right mouse click your site and hit “Inspect”. The console will probably tell you more about it.

  • Thank you for your comment. I did what you said and Chrome says: “This page includes a password or credit card input over HTTP. A warning has been added to the URL bar.”

    From that, I noticed (by copying-pasting the url to notepad because it was not on the url bar) that Chrome does not redirect to https (as firefox does). So, this is an entirely new problem. Why Chrome does not redirect to https? is this something to do with Nginx?

  • Chrome itself will never redirect something, if thats what you are saying (I might understand it differently). You need to do it all server side;

    So for example, when you have a contact form or some sort of payment application on your site, all the files you use need to be served over HTTPS. I could check your site if you would like me to , to see if I can find anything (skype: cryptic-designs). Otherwise I would advise you to recheck your source / redirection code to make sure everything goes over HTTPS.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
3 answers

@Mohsen47 raises a good point. Check the browser console to make sure you don’t have any http links like this . I generally put // instead. This will default to https if the host server supports ssl while at the same time as your browser checks for http links, it won’t find any and mark this as a secure page.

Regarding the http-https redirect, double check the Adjust the Nginx Configuration to Use SSL section of the guide to make sure you configured the files as directed. Also restart Ngix for good measure. Hope that helps

  • Thanks. It seems you have a point. In the guide I decided to follow this paragraph “(Alternative Configuration) Allow Both HTTP and HTTPS Traffic”. So, (for some reason) Chrome selects http over https (if I explicitly request https://, Chrome works over SSL as expected). I will try to modify the .conf file and see how it goes.

Maybe because some of the resources on your page are not transferred over HTTPS, Apache’s default web page is marked as not safe because of the images inside it try to remove them then refresh to see the results.

Hope this helps.

Are you serving your site with an IP address instead of the secure URL? I was doing this and when I changed it, I fixed this problem