access share by http gives 404

Are your files publicly available (user rights) ? did you try to reboot or relaunch the web server ? Is this a new configuration or did it work previously ?
I think the URL for older NAS is different than the one for OS6, can you try https://ip.address.of.nas/webshare/yourshare and https://ip.address.of.nas/share/yourshare. I think there is something like that to add before the share name.

Hi xeltros, thank you for your reply.

xeltros wrote:
Are your files publicly available (user rights) ?

Don't know; how can I check?

did you try to reboot or relaunch the web server ?

Yes, didn't made any difference.

Is this a new configuration or did it work previously ?

I've been just starting to use the http interface for the shares.

I think the URL for older NAS is different than the one for OS6, can you try https://ip.address.of.nas/webshare/yourshare and https://ip.address.of.nas/share/yourshare. I think there is something like that to add before the share name.

Both webshare and share in front of the sharename give a 404.

did you take a look at http://kb.netgear.com/app/answers/detai ... diator-4.x) ?
Their technique makes use of the default redirection. If you only have one HTTP share to create this can be done like that, otherwise I don't know, I don't have a 4.x device so I can't test anything.

I have just read your link. I think we misunderstand each other. I don't want to make a website, I want to access my share using https from outside of my home.
Thank you.

Indeed I misunderstood but those two things are not that different.

The first thing is to make it work locally. The second is to configure the router forwarding capabilities. The third is to use a dynamic DNS to point to your router. The approach is pretty similar than for a website, except that instead of having files that will print a webpage, apache will create an index of the files automatically.

maybe you would also want to check readyNAS remote : http://www.readynas.com/?cat=52
Ultra is not mentioned here but I don't see any reason why it shouldn't work with it. It is an alternative for remote access to the NAS from internet.

see this too : http://kb.netgear.com/app/answers/detai ... lus-series,
The link for Remote is at the bottom, the link for HTTP is at the top.
They say to access http://ip/shares with an "s", can you try that ?

But since you asked for HTTP, we'll try to work this out. So just to be clear.
Does this work locally ? (IP in 192.168.x.x)
What did you do to configure the share ?

entering https://nasname/sharename, and then right-clicking on a file and selecting "save as" downloads for me. Clicking on the file launches it.
https://nasname/shares gives the full list of shares that are enabled for http. Clicking on a share opens a new tab, showing the contents.

Try this from the local LAN first.

Ok, this is tested locally:
https://nasipaddress/shares works

https://nasipaddress/sharename works, i can browse through folders. However clicking a file, or rightclick and save as, gives a 404: not found.

Looking in /var/log/frontview/error.log is can see a line:

 [error] [client 192.168.254.59] File does not exist: /opt/remote/htdocs/<sharename>/<filename>, referer: https://<ipaddress>/<sharename>/

It looks like frontview is looking at the wrong place to serve the file. In reality, the file is in /c/<sharename> and not in /opt/remote/htdocs/<sharename>

Any help?
Thank you!

Ok, I think I found it. It looks like a bug to me.

Facts:
- Readynas Remote was installed (as by default), but not activated
- My share is called "nas"

There is a file /etc/frontview/apache/addons/READYNASREMOTE.conf which defines an alias for apache:

Alias /nas /opt/remote/htdocs/nas

Once I commented that line and restarted apache it started to work.

The bug is that frontview lets you create a share with a name "nas", but that name conflicts with the defined alias.

Thank you.

Yeah this is a sneaky one. Glad you found it.
Now that this work locally, you will need to forward port 80tcp or 443 tcp depending if you use http or https and add a dynamic DNS if you want to access it over the internet.

xeltros wrote:
Now that this work locally, you will need to forward port 80tcp or 443 tcp depending if you use http or https and add a dynamic DNS if you want to access it over the internet.

That has already been done, thank you.

Is there a way to tell netgear about this bug and have them fixed it in an update? Are they on this forum?

Thank you