Hey!
Pretty new to this whole thing, but I believe I’m getting a hold of it.
Got a notification that the certificate had run out, so I needed to make a new one. Struggled with it for quite some time, but yesterday I finally got around to creating it. Felt like a great success, but when going to the site, it still says “Not secure” in Chrome.
I don’t know why, and can’t find anything on Google that can get me any further.
What can I do to remove the “Not secure” from my website?
I ran this command: sudo certbot certonly --webroot -w /var/www/wifi -d wifi.nodescloud.com
It produced this output: Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/wifi.nodescloud.com/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/wifi.nodescloud.com/privkey.pem
Your cert will expire on 2018-11-28. To obtain a new or tweaked
version of this certificate in the future, simply run certbot
again. To non-interactively renew all of your certificates, run
“certbot renew”
If you like Certbot, please consider supporting our work by:
My web server is (include version): Ubuntu 14.04
The operating system my web server runs on is (include version): nginx v 1.4.6
My hosting provider, if applicable, is: Amazon EC2 Instance
I can login to a root shell on my machine (yes or no, or I don’t know): Yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No
There's a good chance it would. But you should be able to figure out exactly what needs to be done (a "reload" command to your web server would be my guess), and set certbot to do that after renewing the certificate, so you don't need to do this every time your cert renews.
How do I know which certificate is being used, caus according to certbot certificates I only have one. But it doesn’t seem like it’s in use, given that my site is still labeled insecure.
Yes, you have one cert, at one path. Certbot has renewed it, but treats it as the same cert. If your cert was working previously, you should only need to reload your webserver to get it to use the renewed cert.
So the issue has nothing to do with your certificate, it's the lack of a working HTTP -> HTTPS redirect. Fix that in your nginx configuration and you'll be set.