From July on, Chrome will brand plain old HTTP as “Not secure”
3 replies, posted
[url]https://arstechnica.com/?p=1257647[/url]
I thought they already did this?
[QUOTE=Durrsly;53121889]I thought they already did this?[/QUOTE]
nah, that was just for web forms
If anyone is running their own websites and needs some SSL certificates to not show as "Not secure", take a look at [URL="https://letsencrypt.org/"]Let's Encrypt[/URL]. It lets you generate certificates for you to use for free.
edit: Also a couple of handy notes: The certificates from Let's Encrypt needs to be renewed every 3 months, [URL="https://certbot.eff.org/"]Certbot[/URL] is a handy tool for creating certificates with Let's Encrypt, there's also a free web panel called [URL="https://vestacp.com/"]Vesta CP[/URL] that lets you create certificates by clicking a few buttons (hassle free). Setting up SSL for the actual web panel is a bit more involved, here's an article that explains how to do that (one thing to note is that if the permissions fix didn't work you may have to navigate to the directory where the SSL files actually are before running the permission fix commands "cd /home/admin/conf/web"): [URL]https://blog.flaunt7.com/how-to-use-lets-encrypt-on-vesta-login-panel/[/URL]
Sorry, you need to Log In to post a reply to this thread.