NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
WebDAV
2 Topics
OwnCloud 9.1 WebDAV, Permissions and HTTP Issue
Hey everyone, I installed lastest OwnCloud 9.1 on my Ready NAS (RN214,FW6.5.1). Not the Addon, but normally on the webserver using MySQL. So only apps installed are PHP, MySQL and phpMyAdmin. Port 80 is forwarded, it works. But I read 3 security notifications in OwnCloud administration. And I can't find anyting to help me. 1) Your web server is not yet set up properly to allow file synchronization because the WebDAV interface seems to be broken. I set WebDAV enabled on folder setting in Share admin page, but still... Should I configure someting else? 2) Your data directory and your files are probably accessible from the Internet. The .htaccess file is not working. We strongly suggest that you configure your web server in a way that the data directory is no longer accessible or you move the data directory outside the web server document root. Unfortunatelly I have no idea how to do that. 3) You are accessing this site via HTTP. We strongly suggest you configure your server to require using HTTPS instead as described in our security tips. I'd like to. I followed security tips, but I did't got what exactly I have to do. HTTPS in ReadyNAS Services is enabled, but it takes no effect. I'll be glad for any advice and sorry for my poor english Thank you Mike
Can't get WebDAV to work properly
On a ReadyNAS Pro 2 with RAIDiator 4.2.28 I followed the instruction here (p. 41) to activate WebDAV. I registered a ddns domain name on NO-IP.Com. I then set my router to use this ddns domain name. I also set it to give a static IP address to the ReadyNAS and to forward ports 80 and 443 to the ReadyNAS. Using Firefox 44.0 I'm able to access the ReadyNAS by entering "https://<domain name>/ in the URL field and then my username and password in the dialog box that pops up, where <domain name> is the full, 3-part name from NO-IP.Com. I'm also able to access it using http. First Question. When I use Firefox, the first screen I see shows all of my shares with HTTP/S access. Is there any way to access only shares with WebDAV activated from Firefox's URL field? Second Question. I'm confused about what URL to use for WebDAV access. Suppose, for example, I allow 3 shares to have WebDAV access. Is the correct URL https://<domain name>/<share name> for each different share? If so, if only one share has WebDAV access, must the share name be included in the URL? Third Question (THIS IS REALLY WHERE I'M HAVING TROUBLE). I've tried accessing the share via WebDAV all sorts of ways: with and without the share name, with and without capitalization in the username, using the domain name, using the assigned WAN IP address instead, etc., etc., etc. No matter what I do, I seem to be unable to access the share via WebDAV. When I try to access it via Finder on my iMac (running OS X Yosemite 10.10.5) via Finder > Go > Connect to Server and enter "http://<domain name>/" or "http://<domain name>/<share name>, I initially get the login dialog. I choose "Registered User" and enter my user password on the ReadyNAS, but up until a few minutes ago, I always got an error message, "There was a problem connecting to the server "<domain name>" .... Of course, once I started writing this post, the freaking thing started working! (I've spent the last 2 days on this!!!) But, I'm also using Zotero, which is a reference management system. It has a way to store pdf files on a WebDAV server. It has a dialog with a URL broken into two, possibly 3 parts: protocol (http or https), path (<domain name>/<share name>, and folder (/zotero/). The folder seems to be mandator and automatically added to the path. Two other fields are the Username and Password. It also has a button, "Verify Server", and that's where I'm still having trouble. If I use http, it tells me "You don't have permission to access /<share name>/zotero/ on the WebDAV server. If I use https, it tells me, "SSL certificate error connecting to <domain name>. See the certificate override documentation for more information." I did see the overide documentation, and did follow the instructions by copying a certificate file from the Firefox profile to Zotero's user setting folder. But that didn't make a difference. Besides, if I can't get http working because of the path, I doubt fixing the certificate will make a difference for https. Any suggestions for fixing this?Solved4.2KViews0likes3Comments