Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by JeanMarcS on Wednesday July 25, 2018 @06:34AM
(#17608219)
I’ve got a bunch of (very) old websites of clients who never wanted to update them, whatever strategies we tried to make them change.
Now they are all asking to migrate, so it’s a good financial opportunity :)
(But to be honest, this is money that should have been earned during past years. Some of them are really stubborn)
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by Arkanosis on Wednesday July 25, 2018 @05:13AM
(#17607890)
OVH did the same thing silently in mid-2016 for shared hosting. GitHub Pages did that silently too earlier this year for custom domains, and made an announce in May.
That's awesome :)
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by ams6110 on Wednesday July 25, 2018 @05:25AM
(#17607955)
My GitHub pages site is serving a certificate that expired in June though, any idea how to get that updated?
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure”
by laurent123456 on Wednesday July 25, 2018 @05:53AM
(#17608068)
I had the same problem and it got fixed quickly after I contacted them. It's a bug in their auto-renewal script.
JustHost, one of the hosts I have a few clients websites on for years, suddenly started to offer free Let's Encrypt SSL certs to protect users from this change (previously you had to pay for fixed IP, and the certificate itself) - what a great thing to happen.
All I had to do was change a few .htaccess files, a few DB entries and track down a few template files that had HTTP external JS references.
It was enough work that I had to invoice for the conversion (with the option of not bothering) - but annual fees are still the same, clients websites have SSL and every client wanted the upgrade, rather than be marked "insecure".
I really think this is a breakthrough change!