NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RupertGiles
Jul 07, 2017Apprentice
Self signed certificate error in Chrome 59
The self-signed certificate from the ReadyNAS O/S is no longer considered valid by Chrome 59. There are two errors: Subject Alternative Name Missing There are issues with the site's certificate ch...
- Jul 07, 2017
RupertGiles wrote:
It would be nice to never have to see that warning.
True. I used to use firefox with the NAS, since it's very simple to add a security exception there. But the click-through has become pretty automatic (which of course defeats it's purpose).
RupertGiles
Jul 07, 2017Apprentice
Yes indeed. On Chrome 59, it's More Tools/Developer Tools/View Certificate.
I dragged the certificate to the desktop, then deleted the existing certificate in Keychain, and finally, imported the certificate from my desktop and set the permissions to "Always Trust".
What's changed (from what I've gathered off Google boards) is the requirement for the SAN.
If I've missed something in my procedure, please let me know, and I'll retry. Thanks!
StephenB
Jul 07, 2017Guru - Experienced User
I meant regenerate the cert on the NAS. I don't think the firmware upgrades do that automatically.
You'd do this in system->settings->services->https. It should regenerate the cert if you simply enter "apply".
But you could change the SSL key host, apply, then change it back, apply again if you want to be certain.
- RupertGilesJul 07, 2017Apprentice
Yes, I did think of that and try that. As noted, this only started with Chrome 59. Apparently, the requirement for a SAN which previously was optional, is what's tripping things up.
- StephenBJul 07, 2017Guru - Experienced User
I've just clicked through the warnings for years, and Chrome 59 (running on Windows 10) still lets me access the NAS.
At the moment, it's not giving me a warning, it just connects - not sure if something changed, or if Chrome is somehow caching my previous click-throughs.
I am running 6.8.0-T54 on the NAS. My SSL key host is a name, not the IP address.
- RupertGilesJul 07, 2017Apprentice
Yes, absolutely...I didn't mean to imply that I couldn't gain access--only that there is always that damn certificate warning to click through the first time you access FrontView in a given browser session. It would be nice to never have to see that warning.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!