NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNASs 314 privacy error when connecting with Chrome
Two of my disks died and for some reason I got no warning. Luckily I had everything backed up!
I wound up completely reinstalling the system and installed 4 new drives. In the process, I have now confused Chrome so that when I go to the ReadyNAS, Chrome will flat out not let me in! (note there is no option to continue at your own risk):
Your connection is not private
Attackers might be trying to steal your information from andraia (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_INVALID
andraia normally uses encryption to protect your information. When Google Chrome tried to connect to andraia this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be andraia, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.
You cannot visit andraia right now because the website sent scrambled credentials that Google Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later.
I had to trick Chrome and go to the IP address instead of the hostname to be able to login at all.
1) I need to be able to access this by hostname as I can never remember the IP address
2) I would love to be able to install an SSL certificate so I don't get the nag when I login.
Any suggestions on either of these questions?
So here is the solution...
I was trying to log into https://myNas which was giving me fits on Chrome. All I had to do was go to http://myNas, accept the certificate, and now I can access it normally. Sheesh, what a PITA!
thank you everyone for your suggestions.
15 Replies
Your NAS does have an SSL certificate, it's just self-generated. Since you re-installed, and especially if the IP address changed, you probably need to re-generate it (go to System > Settings > Services and select the HTTPS button), and that may get you back to where you were. A standard SSL certificate cannot be used on a private network, and the self-signed one is still going to give you a strong warning, but you should be able to click through it. If not, you may need to change your Chrome security preferences.
I'm pretty sure Chrome first uses the Windows Hosts file for DNS look-up, so putting an entry there may also help. You can find instructions by Googling.
- I've replaced the SSL certificate.
Chrome is not having any problem finding the ReadyNAS so it's not a DNS problem.
Believe me, I have Googled for this.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
