Marc_V wrote:

Have you tried using Firefox? and setting it up with exception? or using an older version might work.

There are a couple of ways to potentially resolve this.

One is that the apache web server in the NAS explicitly redirects to https. If that can be undone, then access would be retained (using http instead of https). I believe that in OS 4.2 this requires a change in virtual.conf, but I haven't tried it, or figured out if the change would be sticky. I also haven't looked at 4.1 (and since I don't have a v2 NAS I can't check OS 5) This would (IMO) be the best solution. Though the firmware itself is end-of-life, Netgear (or potentially someone else like WhoCares_ ) could provide an add-on that would apply this change.

Another is to update apache so it uses a version of TLS that isn't being deprecated. This would be better of course, but it definitely is more work, and might require Netgear to back-port changes.

Using firefox might work at the moment, but it won't work longer term. All browser vendors are dropping support for TLS 1.1 - see for instance this: https://www.zdnet.com/article/browsers-to-block-access-to-https-sites-using-tls-1-0-and-1-1-starting-this-month/ This includes removing the "click through" that is currently possible.

Installing an out-of-date browser to access the NAS would of course work, as long as you were careful to prevent it from being automatically updated. There is a way to disable checking for updates in the FireFox preferences. But you'd need to be careful not to use that browser to access the internet.

Forum Discussion

Weird Orbi AX6000 network map