Re: https access returns unexpected files

els76uk · ‎2011-08-25

hello, i recently changed the name of my readynas duo share (from "fileserver" to "nas", in order to maintain compatibility with MS Word 2011 Mac) and upgraded to RAIDiator 4.1.8-T5 (to make the readynas compatible with OS X Lion).

since then, i've been having issues accessing my files via https. it used to be that when i clicked on the share name from a remote location using https, it would offer a list of all my files and folders. however, since then, i've been seeing the following instead, which I don't recognise. The other share (I have two shares) works fine. I repaired permissions, to no avail.

Any info would be appreciated.

In the meantime, I switched on ftp access, which works fine.

els76uk · ‎2011-09-05

hello, i was wondering if anyone can give me a clue on this? wd be really appreciated.

ewok · ‎2011-09-07

Have you installed any addons that may have affected this? I don't immediately recognize this content either.

els76uk · ‎2011-09-07

nope, nothing at all. the only thing i've ever done is upgrade to the latest firmware (RAIDiator 4.1.8-T5)

Our other share works fine.

ewok · ‎2011-09-13

Do a config backup of the share access settings and send them to me using the info in my sig and I'll take a look.

ewok · ‎2011-09-13

You can also try disabling HTTP access to the share, then re-enabling it. That should reset the HTTP configuration for the share.

ewok · ‎2011-09-19

Thanks for the config backup. Everything looks fine. If you try to access the nas share over CIFS, do you see the correct files?

els76uk · ‎2011-09-20

yes, all absolutely fine via CIFS.

ewok · ‎2011-09-23

Try updating the 4.1.8 final. As I mentioned earlier, your config files look fine, so I'm puzzled at what might be causing this.

els76uk · ‎2011-09-26

thank ewok. i did that, makes no difference.

ewok · ‎2011-09-26

In that case, I'd suggest opening up a case with support. They may need to access the NAS remotely to see what's going on.

dbott67 · ‎2011-09-26

A couple of thoughts:

What is the hostname of your NAS? Is it also nas? If it's the same, can you try renaming the NAS to nas1 or something other than the name of the share? Alternatively, you could change the name of the share back to fileserver and/or something different (ie nas-share)?

If the NAS name is not nas, do you have a user called nas?

Trying either (or both) of the above may offer some insight into some sort of naming conflict.

Have a look at this for a bit of insight (under the "configuration" section): http://home.bott.ca/webserver/?p=346

els76uk · ‎2011-09-26

thanks dbott67. yes, both the host and share name is nas. it used to be called fileserver, but that made Word crash so I had to rename it.

I'll try renaming again.

els76uk · ‎2011-09-26

dbott67, you're a star! i renamed it, and it works now. weird that when you call it something it doesn't like, it returns those odd files; and also that frontview stops you from calling the share "readynas" but not simply "nas". any way to pass that comment to the developer team?