- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Unable to update SSL key host
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unable to update SSL key host
I'm using an old RND4000v2 and I'd like to stop the SSL errors in my browser. To do this I need to be able to set the SSL key host value to the same IP as the ReadyNAS. The value is currently set to 192.168.1.85, and any attempt to change it seems to fail. I had tried restarting the device, and it still loads back up set to 192.168.1.85. I'm using RADiator 5.3.13, which is the last supported version for my device. Any suggestions?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to update SSL key host
I don't have a v2 NAS, and am not sure if there is a workaround. I do want to say that generating a new self-signed cert in the NAS won't stop the errors in your browser - it will just change what those errors are. One thing that will work - use FireFox to access the NAS, and store a security exception when you hit the error. That is browser-specific (you'll still get the errors on other browsers).
Is 192.168.1.85 the current IP address of the NAS?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to update SSL key host
"Is 192.168.1.85 the current IP address of the NAS?" - Nope, That subnet doesn't even exist on my network!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Unable to update SSL key host
@tommitytom wrote:
"Is 192.168.1.85 the current IP address of the NAS?" - Nope, That subnet doesn't even exist on my network!
Likely it did exist when the self-signed cert was generated though. Is the NAS used?
Anyway, you'll still get browser warnings even if the self-signed cert uses the correct address. By definition, self-signed certs can't be verified by a certificate authority. Personally I just click through the warnings.