Help - Netvibes no longer works on Chrome Canary Browser
Here's what it looks like... See file attached.
I'm hoping for a simple fix.
The SSL certificate is now updated to sha2 on our CDN, and works on chrome Canary :)
Hi, problem is still persisting in latest DEV build of Chrome, Version 56.0.2922.1 dev (64-bit)
Error messages in Chrome are exactly the same as reported by Benjamin commented · November 19, 2016 23:40
Any indication when new certificate will be issued?
Yes, chrome canary 56 users already have a certificate warning ( see https://security.googleblog.com/2016/11/sha-1-certificates-in-chrome.html )
Renewing of cdn.netvibes.com certificate is in progress, and a sha-2 certificate should be in place in a couple of hours.
AdminNetvibes (Netvibes, Netvibes) commented
Thanks for the feedback. The development team has been informed
Oh and Josh: Try going to https://cdn.netvibes.com/img/favicon-12.png on a new tab, then manually proceed by allowing the certificate. It should then show you the favicon and if you load netvibes.com it should show it correctly for now. Probably only works for the browser session though.
Same here in Google Chrome 56.0.2922.1 dev (64-bit).
Just updated and now the page is broken.
From the developer console:
GET https://cdn.netvibes.com/assets-1132/css/uwa.css.m.css net::ERR_INSECURE_RESPONSE
1:17 GET https://cdn.netvibes.com/assets-1132/css/base/screen.css.m.css net::ERR_INSECURE_RESPONSE
1:19 GET https://cdn.netvibes.com/themes/wasabi/screen.css.m.css?v=1132 net::ERR_INSECURE_RESPONSE
1:256 GET https://cdn.netvibes.com/img/favicon-12.png net::ERR_INSECURE_RESPONSE
1:415 GET https://cdn.netvibes.com/assets-2177/js/c/mootools.js net::ERR_INSECURE_RESPONSE
1:416 GET https://cdn.netvibes.com/assets-2177/js/c/Netvibes.js net::ERR_INSECURE_RESPONSE
1:212 GET https://cdn.netvibes.com/img/s.gif net::ERR_INSECURE_RESPONSE
cdn.netvibes.com/favicon.png:1 GET https://cdn.netvibes.com/favicon.png net::ERR_INSECURE_RESPONSE
It looks like cdn.netvibes.com is using a SHA1 certificate which is now blocked by Chrome. All they need to do is update the certificate to a new one that has a better signature algorithm. Since the certificate is valid only until 1.1.2017 I really hope Netvibes can just go ahead and quickly exchange it now.