Go to Configure, System, Services. Then I think right click on https (it should already be activated). You should then see something that allows you to verify/change the ip address of the nas for the certificate, and something to regenerate it. This is the way it works in all of the other readynas operating systems so i assume it will be the same for 5.3.9
Go to Configure, System, Services. Then I think right click on https (it should already be activated). You should then see something that allows you to verify/change the ip address of the nas for the certificate, and something to regenerate it. This is the way it works in all of the other readynas operating systems so i assume it will be the same for 5.3.9
Thanks, but it did. No button to generate a new certificate? Am I wrong thing?
Delete all the certificates that have been generated by the Nas from the browser certificate store first. Then go to the https settings and click on apply again
The certificates can be found in Internet Options, Content, Certificates, Trust Root Certification Authority.
Delete all the certificates with the old ip address and the new ip address, then go to the https settings and regenerate the certificate. Make sure the nas ip is in your trusted sites list (also in Internet Options, Security, Trusted sites.
Ok. Let's try again. Open the browser without connecting to the NAS. Delete the NAS IP address from the trusted sites list, delete the 192.168.168.168 address and the new address if they are both there. Delete the certificates from the trusted root certification certificate store, delete those with the 192.168.168.168 address and the new address. Clear the browser cache. Add the NAS IP address to the trusted sites list Use https://ipaddressofnas Restart the browser and connect to the NAS. Regenerate the certificate. Clear the browser cache and restart the browser.
When the certificate error appears and you click on the error, what do you see.
I have just completed the whole process on my machine. I am not using a duo v2, but the process is the same.
I acivated dhcp without a dhcp server and the nas got 192.168.168.168. I generated a key using this address and got a certificate error with this certificate (192.168.168.168) I installed this certificate after adding that address to trusted sites.
I then changed the network settings in the nas to a fixed ip address 192.168.2.172, changed the setting in the https settings and regenerated the key - I received a confirmation message after about 20 seconds.
Then I closed the browser.
I reopened the browser, deleted the old ip address from trusted sites and deleted the key from Trsuted root certification authority store.
Closed browser again
I reconnected to the nas using the fixed ip address, got the certificate error, added the nas ip to trusted sites again.
I then reconnected to the nas ip, clicked on the certificate error and the correct certificate was there..
It seem your nas is not regenerating the key.
Try rebooting the nas and repeating the process. Also clear the ssl cache in your browser.
It should work, I helped someone else with the same problem here:
I have the same problem on my Duo and the only solution is to contact hotline by email or by phone. Someone take a remote access to your ReadyNAS after you have added a temporary "Enable SSH support" add-on. I reported this bug to Netgear for 1 year and Tier 2 support told me that it is to validate a future update. another embarrassing Bug that I reported, imposible to make backup directory on an imac (not time machine) but I wait the retrun of NETGEAR. I fear that these two bugs are never fixed because the product is end of life.
I know this is an old thread but I have been following the instructions and struggling to make it work, but I have figured out why so thought it might be useful to post what happened in case anyone else is also struggling.
Like most things it is simple when you know what is happening, when I was exporting the newly generated certificate the process was being hijacked by my antivirus software (Avast Free) with the effect the cert did not contain the correct info - I found this out by examining the cert file in a text editor to see Avast all over it. Disabling the AV software for a few minutes allowed me to export a correct certificate which I could then import to the certificate store. End of warning messages.
Just use a bit of common sense when doing this, disable the AV software for the shortest time possible, don't do anything else whilst it is disabled, particularly accessing the internet, etc.
