NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ddewrbbdg
Jul 22, 2024Aspirant
HTTPS certificate for ReadyNAS 312.. ReadyNAS OS 6.10.9
Hi, i have achieved in the following topic finally to get apache+php+mysql+phpmyadmin installed and working.
Have tried accessing files hosted on nas, and its not regarding only the webserver, but is same situation with the admin when tried from internet.
There was/currently is some https certificate, "that should be" vailid until 2040 year, which would be great. But im not sure whether certificate authority and provider are ok. Browser asks everytime for exception cause unsafe certificate.
Because its regarding webserver, that needs to have valid https certificate, so it could supply web content flawlessly, without asking for permission for exception. I mean solution in browser is not acceptable, i need in the NAS.
Is there some easy way how to replace, extend, validate the current certificate, for public use with nas, webserver and content, or how just get new one, its regarding less that 10 domains, including subdomains less than 100. Like guide or howto? Or some solution that could be linked or previous topic? Thank you.
7 Replies
ddewrbbdg wrote:
There was/currently is some https certificate, "that should be" vailid until 2040 year, which would be great. But im not sure whether certificate authority and provider are ok. Browser asks everytime for exception cause unsafe certificate.
ReadyNAS ships with a self-signed certificate, so there is no CA. With no CA, there is no way to authenticate the NAS. That is why browsers warn you when you connect. The https connection will still be encrypted. Note you do need to get a domain name in order to install a real cert.
There is a post here that might be useful to you:
- SandsharkSensei
In order to be assigned a certificate from a certificate authority, you need a domain name to which it is assigned. You can use a dynamic DNS provider for the link to the IP address -- you don't need a fixed IP. Once you have done that, you can get a certificate. But because of the age of the Debian version ReadyNAS OS is based upon, folks are having difficulty getting certificate update utilities to continue to operate.
Furthermore, also based on the age of the OS, you need to consider that public access to a ReadyNAS may no longer be safe. Just public exposure is questionable.
I don't know what you are running on the ReadyNAS for which you need public access, but you may want to re-think it. I personally run OwnCloud on another device and link some folders on my ReadyNAS to that, but they are all mounted as read-only.
Sandshark wrote:
I don't know what you are running on the ReadyNAS for which you need public access, but you may want to re-think it.
Very true.
Now that Debian Jessie has been archived, the only security patches you will get for the NAS are ones that Netgear chooses to backport. No idea how long they will do that.
A safer path would be to run the web server on a different machine (perhaps a VM) and mount any NAS shares you might need on that server.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!