NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS & Frontview - Certificate Error
I have had my ReadyNAS NV+ v2 for about a week now. When I hooked it up it was assigned an IP address of 10.0.0.9. Shortly after I got it running I had need to change the IP adddress to 10.0.0.50. Now everytime I start Frontview I get an Certificate error. I have tried several things to no avail.
If I do an OS reinstall following the directions in the manual will;
1) I lose all the Shares that I have created along with the data that they contain?
2) More importantly, will it reset the IP to the one the router is assigning to it. NOTE: it shows the correct IP (10.0.0.50) on the front panel and in FrontView and the router shows that it is assigned that address. It just seems that somewhere in the firmware or memory of the ReadyNAS it has stored the orginal 10.0.0.9 address. I tried running FrontView on another system this morning and when the ReadyNAS sent the certificate it had the 10.0.0.9 address and not the 10.0.0.50 that was showing on the front panel.
Any suggestions or help would be greatly appreciated. I can use it just fine, but have the red bar and have to click to run anyway. Just curious if anyone has had this issue and if an OS reinstall solved it.
If I do an OS reinstall following the directions in the manual will;
1) I lose all the Shares that I have created along with the data that they contain?
2) More importantly, will it reset the IP to the one the router is assigning to it. NOTE: it shows the correct IP (10.0.0.50) on the front panel and in FrontView and the router shows that it is assigned that address. It just seems that somewhere in the firmware or memory of the ReadyNAS it has stored the orginal 10.0.0.9 address. I tried running FrontView on another system this morning and when the ReadyNAS sent the certificate it had the 10.0.0.9 address and not the 10.0.0.50 that was showing on the front panel.
Any suggestions or help would be greatly appreciated. I can use it just fine, but have the red bar and have to click to run anyway. Just curious if anyone has had this issue and if an OS reinstall solved it.
8 Replies
Replies have been turned off for this discussion
- You can
(a) reset the IP address back to 10.0.0.9. The OS reinstall will not guarantee that the router will assign the same address; what it will do is reconfigure the NAS to use DHCP. You should be able to log into the NAS by clicking through the warning - so there is no need for the OS install.
(b) Recreate the security exception in the browser. This is the simplest thing to do. Some browsers make is easier than others, FireFox is friendlier than IE and Chrome in this regard. Note that you can recreate the security exception even though the IP address is now different. What browser are you using?
In the x86 and sparc platforms, there is a way to regenerate the SSL certificate using he new IP address. I don't see this feature in the v2 documentation, though honestly it isn't really needed. Even if you regenerate it you still need to recreate the browser security exception because it is self signed.
BTW, an OS install will not destroy your data. It will reset your admin password, and it will reset the IP configuration to use DHCP - meaning that the NAS will request an IP address from the router. - Thanks for the replay. I am using IE9 for my browser. I have actually tried to reset it back to 10.0.0.9 before and it did not change the security warning. The issue now is that I have 3 desktops and 3 laptops, each with multiple shares, that are set up using the 10.0.0.50 IP. Also, as a result of the dreaded message of "not able to reconnected all netwok drives" I am running netlogon.bat files on each of these (BTW these work perfect to reconnect all of the shares to each computer). I cannot find anywhere in IE9 or FrontView to change the IP address to 10.0.0.50. When I tried it on another system (just for grins) the NAS sent the certificate with the address 10.0.0.9 even though everywhere (front panel, FrontView and my router all show the IP as 10.0.0.50). Odd to me, but then I am by no means an expert on networking. LOL
- The IP address is 10.0.0.50, but the certificate was created when the IP address was 10.0.0.9. As I stated above, this mismatch can be overcome by re-creating the security exception (the same way you did when you originally connected to the box).
I went through this a while ago when I reset my router to use 10.0.0.x addresses instead of 192.168.1.x. Although I could have re-created the certificate on the pro, I didn't. All I did was tell the browser to make a permanent exception (this was with firefox). There is a procedure posted for IE9 here: viewtopic.php?t=59164#p348054readysecure1985 wrote: Here is the process in which I have found works with Internet Explorer
- Browse to the site whose certificate you want to trust.
- When told "There is a problem with this website's security certificate.", choose "Continue to this website (not recommended)."
- Select Tools->Internet Options.
- Select Security->Trusted sites->Sites.
- Confirm the URL matches, and click "Add" then "Close".
- Close the "Internet Options" dialog box with either "OK" or "Cancel".
- Refresh the current page.
- When told "There is a problem with this website's security certificate.", choose "Continue to this website (not recommended)."
- Click on "Certificate Error" at the right of the address bar and select "View certificates".
- Click on "Install Certificate...", then in the wizard, click "Next".
- On the next page select "Place all certificates in the following store".
- Click "Browse", select "Trusted Root Certification Authorities", and click "OK".
- Back in the wizard, click "Next", then "Finish".
- If you get a "Security Warning" message box, click "Yes".
- Dismiss the message box with "OK".
- Select Tools->Internet Options.
- Select Security->Trusted sites->Sites.
- Select the URL you just added, click "Remove", then "Close".
- Now shut down all running instances of IE, and start up IE again.
- The site's certificate should now be trusted.
Give it a try and let me know if it works for you too. - Nope did not work. I had actually tried that before and it did not work. Here is the issue that I see. When I do the install certificate it shows that it is issued to 10.0.0.9 and issued by 10.0.0.9 and that it is valid from 11/24/2012 to 1/18/2038. The IP is the address that the ReadyNAS got before I changed it and the from date is the date that I installed it to start with. For some strange reason, and I may be doing this wrong or something, the ReadyNAS certificate never changes to the address it is now using. Everything seems to work OK, it is just annoying to have to click "Continue to this website (not recommended)" and then have the IE bar in RED and showing a certificate error. That is what prompted the question about doing an OS reinstall. I should not have to do that, but I would really like to resolve this to the point it simply logs on to Frontview and everything looks right. I am assuming that there is a way to fix this short of doing a complete factory reset and starting over, which based on the data that I already have on the NAS I would really like to avoid.
Thanks again for you help. Any other suggestions would be greatly appreciated. - The certificate is not automatically regenerated when the IP address changes. If you used DHCP, that would essentially make the certificate useless.
The simple answer is to use firefox.
You could also go into the advanced tab of internet options (IE) and try unchecking "Warn about certificate address mismatch" - StephenB, have to tell you that I got my issue with the certificate error resolved. I did an OSreinstall and then followed your process. After following your steps I went to Tools and deleted the Temporary Internet Files, closed IE and then rebooted my system. When it came back up I started IE9, then Frontview. Frontview came up without the certificate error. Thanks for all of your help in resolving this issue. Much appreciated.
- Great. I take it that the NAS is now using IP address 10.0.0.9?
If so, you should look in your router to see if it lets you reserve IP addresses. If so, you can make sure that IP address sticks. - No, the NAS is using 10.0.0.50. I had reserved it on the router for the NAS based on its MAC Address. So once it restarted it showed that address and I then followed you directions and everything is working as it should. Thanks again.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
