NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Web (http) access totally broken in OS 6.6.0
I don't normally have HTTP access turned on for shares. But I was having some issues trying to install an SSL certificate for a web site and OwnCloud, so I turned it on to see what changes it made to the system. Answer: almost nothing. Web based user access is totally broken in OS 6.6.0. Here are the instructions from Netgear on using web access in green (How do I access a shared folder on my ReadyNAS OS 6 storage system by using a web browser?) and my observations in black regarding them:,
To access a share using a web browser:
1. Ensure that the HTTP file-sharing protocol is enabled on your ReadyNAS system.
For more information, see the How do I set network access rights to shared folders on my ReadyNAS OS 6 storage system?
Yep, did it.
2. Launch a web browser.
Ditto.
3. Navigate to the ReadyNAS system and shared folder you want to access using the following syntax:
http://<hostname>/<share>
- <hostname> is the name that you assigned to your ReadyNAS system or the default host name if you did not change it.
- <share> is the name of the share that you want to access.
- (Optional) For a secure encrypted connection, replace http with https.
Done.
Note: If you cannot access the ReadyNAS using its host name, try entering http://<ReadyNAS IP address> in the web browser address bar instead. <ReadyNAS IP address> is the IP address of the ReadyNAS.
Tried this to.
You are prompted to log in to your ReadyNAS system.
No, you aren't. You are shown a generic "Index of Sharename" and all the files/folders in the share. It's the built-in browser display you get when there is no index.html or redirect to something else. Since there is no way to set file permissions for HTTP access to anything other than "Everyone", why would it ask even if everything else wasn't also broken?
4. Enter a user ID and password.
You can log in with administrator or user credentials. If you log in as a user, your access is limited by the settings configured by the ReadyNAS system administrator.
No, it's not. Access can only be everyone or no one, and not even a read/write or read-only.
Your shared folders are displayed in a web page.
Well, sort of. Only the one share you specified is shown, and it's a display built into the web browser that you can't do a lot with. If you click on "Parent Directory", you are taken to the admin login (and it switches to https unless you have admin access via http enabled).
So, is there html code in there somewhere that's supposed to be executed for this? I could't find an "index.html" file anywhere that looked like it was supposed to do it, unless it's the same code as for the admin page but acts differently when /admin is not specified. Using http://<hostname>/index.html gets you this:
It works!
This is the default web page for this server.
The web server software is running but no content has been added, yet.
So, I beg to differ that it does, in fact, work. It should be noted that all my NASes are legacy and have been factory defaulted to 6.6.0, even the one on which I orignally tried earlier versions of OS6. So if there was supposed to be sometng left over from a previous version of the OS, it's not there. I'm pretty sure I did test it under 6.4.x and it worked then, but maybe it was 6.2.x when I last checked.
6 Replies
Replies have been turned off for this discussion
Have you tried ReadyNAS OS 6.6.1?
Only on one system, same result.
So I just enabled http on one of my shares. I turned off everyone access and gave a user access (only 1 user).
I went to http://ip/basgafasdfasf (basgafasdfasf is my share name).
It prompted me immediately for credentials. I hit cancel, it gave me this error
"Authorization Required
The ReadyNAS could not verify that you are authorized to access the resource requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required."
When I refreshed back to the IP/basgafasdfasf, I tried logging in.
I still got the apache2 index. Saw all the files from a share level. All my files have guest.guest ownership there. I redid all the permissions for the share to admin.admin and then changed the access level of those files to 770. When I refreshed the share page, all the folders disappeared and I was left with a file listing. When I tried to click the file, it gave me:
"Forbidden
You don't have permission to access /basgafasdfasf/contexhelp.JPG on this server."
To me, it seems to work, althought not as glamerous as it could be.
I am pretty sure this is expected behavior. You could put your own index.html file there if you wanted to host a website from your NAS. The read-write part comes into play with webdav.
I thought we used to show browse.html (http://ip/admin/browse.html) when you would visit these without an index but I guess not.
So the "expected behavior" is that it acts nothing like the instructions say it should? I'm not buying it. browse.html is still there in /frontview/dashboard, but the only way to get there is from the admin dashboard. Users can't access it as they used to be able to. And why would the access control for HTTP be intentionally changed to "all or nothing"? Now, if I do create a website, I have to be careful to set the rights to all files so that nobody can delete them, I can't just set the whole share to read-only for everyone but admin.
If it's intentional, it's downright foolish.
One minor correction. You can go to http://<nas-ip>/browse.html as admin, you don't have to go through the main admin page.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
