NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS Duo V2 firmware update catch 22!
Hi All I have the above device and am having some fun trying to update the firmware. I have a Dell XPS13 laptop running Windows 11. I managed to access the old shares by enabling SMB1 in windows...
Hi
Thanks very much for your helpful replies From your description, I have the V1 as it doesn't say V2 on the front panel. only on the label on the bottom.
I've tried a couple of browsers, namely Brave and Firefox and configured both to allow TLS1.0, but no joy. The browser error is:
This site can’t provide a secure connection
192.168.1.50 uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
I didn't mention, but I did try /admin as you suggested, but get the same error. In another thread, it suggested a particular older version of Firefox, but that didn't help either.
In answer to your second question, Raidar reports FW 4.1.16. Clicking on the Admin button, simply opens the browser with the above error message.
At the start, I had some fun trying to view the shares in Windows 11, but allowing
SMB1 fixed that. I can now read and write to them.
If you know of a particular browser that does work with TLS 1.0, Please share 😁
Cheers
Steve
picitup wrote:
I've tried a couple of browsers, namely Brave and Firefox and configured both to allow TLS1.0, but no joy. The browser error is:
This site can’t provide a secure connection
192.168.1.50 uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
If you know of a particular browser that does work with TLS 1.0, Please share 😁
It sounds like you didn't set up FireFox correctly. Set security.tls.version.min to 1 (browse to about:config and search for the setting).
You definitely need the /admin to get into frontview.
Once you have figured out how to get into Frontview, you can install the ssh add-on, and then make a mod that will let you access the NAS from any browser using http://192.168.1.15/admin. Note this is not encrypted https, it is unencrypted. That avoids the problem with no support for TLS 1.2. There are step by step instructions in post 5 of this discussion thread:
Hi StephenB
Thanks for the info. I probably will install the SSH patch if I'm able to access frontview. There aren't any state secrets on the drive 😂
Firefox is configured as you mentioned. security.tls.version.min is set to 1 and I just checked again, but this hasn't helped unfortunately.
The Firefox version is 128.03 64 bit Windows. Can I ask what version you are running that works ok?
Brave browser reportedly has a great feature:
brave://flags/#allow-insecure-localhost
But I turned it on, restarted Brave and no effect on the issue.
Hmmmmm
Cheers
Steve
picitup wrote:
The Firefox version is 128.03 64 bit Windows. Can I ask what version you are running that works ok?
I haven't needed it for a while, and am not at home this week, so I can't test it.
In general, Edge should also work (using the IE legacy mode), so try googling for instructions on that.
Do you have internet security software running on the PC? If so, you might try disabling it.
Also, even when you allow TLS 1.0, you will still have to click through security warnings. That is because the certificate used in the NAS is self-signed.
picitup wrote:Hi StephenB
Brave browser reportedly has a great feature:
brave://flags/#allow-insecure-localhost
Except that localhost is just 127.0.0.1, not any host on your LAN, and that just solves the problem with a self-hosted certificate, not an outdated SSL version. I simply do not comprehend why the browser publishers don't have provisions that allow for easier access to 192.168.x.x and 10.10.x.x addresses. While some do allow you to set the minimum SSL version, you have to do that for all sites, which is not a particularly good idea, and it doesn't take care of the self-signed certificate issue.
I'm running Firefox 128.0.3 (64bit on Win 11). Security.tls.version.min set to 1. Make sure you close FF and relaunch after saving the change.
Then go to your Admin page on FF. You *may* see a warning about the risk of connecting. Press Advanced, see the notice about the security certificate, then press :"Accept Risk and Continue". You should see the login dialog. Enter "admin" and your password and Frontview should appear.
Just remember, if you launch the admin page from Raidar, Raider will use your default browser and attempt to connect using HTTPS which may or may not connect depending on your default browser (mine is Brave). Once you apply the workaround, though, just about all browsers will connect if using HTTP: (no "S").
Rather than rely on Raidar to connect, I just bookmark the page using http:
Also, once the workaround is applied, the TLS setting no longer matters and the connection to the Readynas will always be unsecure. Just make sure you consider steps secure the content if needed.
Hi StephenB
Do you have internet security software running on the PC? If so, you might try disabling it.
What a hero! After banging my head against a wall, the offender was AVG. I added the IP address of the NAS box as an exception and i'm in!
Now I can achieve the original goal of adding more disk space. Currently it has just a single 1TB disk, and I see the limit on such and old box is 2TB, so I'll grab a couple of 2TB drives, giving me 4x the space.
PM me your home address so I can send you an xmas card 😂
Seriously though, thanks for the suggestion 🥳🥳🥳
Cheers
Steve
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
