NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cannot access admin via https
Accessing my ReadyNAS admin page via https (https://192.168.0.2/admin/) results in Chrome saying the connection is not secure : I've followed the guide How do I configure HTTPS (HTTP with ...
Hello IanVaughan,
Based on the screenshot you are getting certificate error every time you access the admin page of the NAS. Please check this guide to address the certificate error.
Welcome to the community!
Regards,
Marty_M
NETGEAR Community Team
Thanks, but that is a really poor solution, it does not solve the https connection issue, it just fixes it for one browser on one computer, of which I can as bypass anyway as already stated.
This has to be either a bug or some bad config I have made, and I hope someone can shed some more light on it.
Hello IanVaughan,
The certificate error does that only apply to readynas it does apply to all Netgear device every time you access it through https. Please check this thread for more information.
Regards,
Marty_M
NETGEAR Community Team
Marty_M wrote:
The certificate error does that only apply to readynas it does apply to all Netgear device every time you access it through https.
It applies to any device (not just Netgear devices) that uses self-signed certificates. These can be mis-used (for example, a phishing site that spoofs netgear.com could use a self-signed certificate as part of the spoofing), so browsers will generate warnings whenever the web server uses a self-signed cert.
As long as you know you are connecting to your NAS, it is perfectly safe to ignore them. If you want to eliminate the click-through warning, it's easiest to use firefox (since it allows you to create a security exception, so you don't need to add certificates to the PC's root store).
The connection will still be encrypted when you click-through the warning. It can't be authenticated (by definition), since that requires a trusted third-party to issue the cert.
Thanks for the help and links, it makes sense that they cannot provide a cert for my device, when its on a IP address, which is as above.
But I wonder if this issue is linked with another problem I am having, raised in a separate thread here https://community.netgear.com/t5/Using-your-ReadyNAS/Access-ReadyNas-102-via-Hostname/td-p/1370042
The think is I used to have it working on without SSL/cert errors, so I am annoyed why I'm getting them now.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
