Cannot access the admin page for my ReadyNAS Duo V2.

[Tarl72]

Hi all,

I'm having great difficulty setting up my new (to me at least) Ready NAS Duo V2. Whenever I try to access the admin page I get a message that "The connection for this site is not secure192.168.1.52 uses an unsupported protocol."

I've tried using Edge, Chrome and Firefox but all give me the same message (just worded differently). Strangely, I can access the Shares page, even though I don't have any as I can't get into the admin.

I have also tried a software reset and a full factory reset.

Any suggestions??

Many thanks in advance,

Tarl.

[AnishaA · Accepted solution]

Hello @Tarl72 ,

And welcome to the NETGEAR Community! 🙂

You can find the solution in the below post. It is a similar issue.

This is an SSL certificate issue, not anything related to the device to work on.

You don't need to worry much you can ignore this error, Your data is safe.

You can refer for further clarification and solution.

Netgear Team  https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/Ready-NAS-1o4-This-si... 

If your issue is resolved please close the thread by clicking "Accept as solution".

Have a lovely day, 
Anisha A

[AnishaA · Accepted solution]

Hello @Tarl72 ,

And welcome to the NETGEAR Community! 🙂

You can find the solution in the below post. It is a similar issue.

This is an SSL certificate issue, not anything related to the device to work on.

You don't need to worry much you can ignore this error, Your data is safe.

You can refer for further clarification and solution.

Netgear Team  https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/Ready-NAS-1o4-This-si... 

If your issue is resolved please close the thread by clicking "Accept as solution".

Have a lovely day, 
Anisha A

[schumaku]

---

@AnishaA wrote:

Netgear Team  https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/Ready-NAS-1o4-This-si... 

---

https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/Ready-NAS-1o4-This-site-is-not-secu... 

fixed the URL referred by @AnishaA