After being on OS 6.2.2 on my ReadyNAS 102 for some time, I decided to uninstall PHP from the unit. This triggered the bug in 6.2.2 that basically breaks the http server on the device. Web admin GUI and any HTTP enabled shares become inaccessible. I quickly saw that this is a known issue in 6.2.2.
After some time with NETGEAR support, they were able to telnet into the device and restore access to the web admin GUI, however, I am still having issues with HTTP enabled shares and WebDAV access. The shares can be accessed on the internalnetwork by going to http://<internal IP>/<share name> but they CAN NOT be accessed by <server name>/<share name> or from the external WAN using a dynamic IP service (no-ip etc etc). When you try to access these shares, I get a 404 not found page saying that "The requested URL /<share name>/was not found on this server." I'm positive that port forwarding is set up correctly because this 404 page is being generated by the server.
WebDAV access is similar. I can access it fine using the internal IP address but if I try to access it externally, it generates errors and shows a bunch of unintelligible garbage. Again, I know it is connecting because it is accepting my login credentials and giving me a SSL cert verification failure (im using bitkinex).
All of this started as soon as I tried to uninstall PHP on OS 6.2.2. Any thoughts? This is killing some of our clients and causing a huge headache. Just now as I type this, NETGEAR has been able to replicate the failure of HTTP and WebDAV on their internal units as well. It sounds like support thinks this is an issue that is not fixed in OS 6.2.3-T1672 (beta). In other words, I'm of luck until they can figure this out. Not too happy at the moment.
I don't use WebDAV, but https://externalddnsname/sharename works on my OS 6.3.3 system.
StephenB, where did you get OS 6.3.3 from? I just upgraded my ReadyNAS 2120 to 6.2.2 and I can no longer access any of the shares I had set up with WebDAV using http or https. It was working using both when on 6.1.9. It sounds like maybe there is a bug. I will also be submitting a case to NetGear Support to see what they have to say.
I did a search on this forum and didn't find any other posts regarding this that were recent and involved 6.2.2 firmware so I am not sure if anyone else is experiencing this.
