Setup warning : WebDAV interface seems to be broke #2495
Comments
|
Please read the contribution guidelines ;) |
|
@schiesbn @icewind1991 @bartv2 @DeepDiver1975 |
|
@alexisju please post your logs files |
|
INSTALL 1 : Web server: apache2 Database: sqlite PHP version: 5.3 ownCloud version: 5.0.0 isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception_NotImplemented' with message 'Not Implemented' in /var/www/cloud/3rdparty/Sabre/DAV/Client.php:436 Stack trace: #0 /var/www/cloud/3rdparty/Sabre/DAV/Client.php(179): Sabre_DAV_Client->request('PROPFIND', '', '<?xml version="...', Array) #1 /var/www/cloud/lib/util.php(590): Sabre_DAV_Client->propFind('', Array) #2 /var/www/cloud/settings/admin.php(34): OC_Util::isWebDAVWorking() #3 /var/www/cloud/lib/route.php(113) : runtime-created function(1): require_once('/var/www/cloud/...') #4 [internal function]: __lambda_func(Array) #5 /var/www/cloud/lib/router.php(127): call_user_func('?lambda_131', Array) #6 /var/www/cloud/lib/base.php(606): OC_Router->match('/settings/admin') #7 /var/www/cloud/index.php(28): OC::handleRequest() #8 {main} INSTALL 2 : i tryed here with https and self signed certificate Operating system: Linux apache-11c.w4a.fr 2.6.32-379.22.1.lve1.2.12.el6.x86_64 Web server: apache2 Database: mysql PHP version: 5.3 more info ownCloud version: 5.0.0 isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception' with message '[CURL] Error while making request: Peer certificate cannot be authenticated with known CA certificates (error code: 60)' in /datas/vol2/xx/var/www/effingo.be/htdocs/owncloud/3rdparty/Sabre/DAV/Client.php:412 Stack trace: #0 /datas/vol2/xxxx/var/www/effingo.be/htdocs/owncloud/3rdparty/Sabre/DAV/Client.php(179): Sabre_DAV_Client->request('PROPFIND', '', '<?xml version="...', Array) #1 /datas/vol2/xxxx/var/www/effingo.be/htdocs/owncloud/lib/util.php(590): Sabre_DAV_Client->propFind('', Array) #2 /datas/vol2/xxxxx/var/www/effingo.be/htdocs/owncloud/settings/admin.php(34): OC_Util::isWebDAVWorking() #3 /datas/vol2/xxxx/var/www/effingo.be/htdocs/owncloud/lib/route.php(113) : runtime-created function(1): require_once('/datas/vol2/w4a...') #4 [internal function]: __lambda_func(Array) #5 /datas/vol2/xxxx/var/www/effingo.be/htdocs/owncloud/lib/router.php(127): call_user_func('?lambda_49', Array) #6 /datas/vol2/xxxx/var/www/effingo.be/htdocs/owncloud/lib/base.php(606): OC_Router->match('/settings/admin') #7 /datas/vol2/xxxx/var/www/effingo.be/htdocs/owncloud/index.php(28): OC::handleRequest() #8 {main} 21.03.2013 11:32 ps: on both install, with same server config, all was worked fine with 4.5* version. |
|
Looks like safe_mode is enabled - please disable that: |
|
Second: |
|
The sabre version is '1.7.5' on install 2, it is a mutualized server; i cannot disable safe_mode |
generally speaking ownCloud cannot run in safe_mode |
|
I'm sorry, i just rechecked: safe_mod is off on both install (as we can see here http://php5-3.web4all.fr/ & http://alexis.no-ip.org/info.php) |
the curl warning is telling a different story ;-) |
|
open_basedir can also be the problem |
|
I am also having problem but for MacOSX 1.2.1 Client http://forum.owncloud.org/viewtopic.php?f=14&t=9067 |
|
I had the same error, but for me the reason was quite obscure. My webserver is a guest running on private ip address that is NAT'ed at the hosts external interface. A connection from the guest to the public one is "refused" so the guest is not able to curl it's own url. Quick fixed by adding a host entry to the private address in /etc/hosts. Need to investigate further why the guest can not connect to the public address (iptables). |
|
btw: The warning I had was |
This at the end means your setup is not proper to allow WebDAV and sync clients to work without issues. Generally speaking: There are cases where we most probably produce false positives - we will fix this if possible. |
|
My situation appears similar (identical?) to what mrvanes reported. My If I connect to the LAN address, e.g. https://192.168.1.123/owncloud I |
|
#2511 dup? |
|
when entering administrator page it says that there is something wrong with the webdav interface and i should consider instructions manual for solving the issue. i double checked, here is everything correct - at least depending on those written in that specifiy manual. webdav also works (syncing at least works) so we may talk about false detection of owncloud. owncloud itself throws this: to avoid any silly thoughts like safe_mode on or maybe set open_basedir. both are def. OFF or unset. (safe_mode off and open_basedir isnt set). also to prevent talkings about missing php capabilities im offering for a short time phpinfo (https://s-l-c.biz/cloud/info.php) as i understand the defending attitude of developers sometimes because nobody wants to hear something "bad" about his "baby", but i want to remind that many ppl (look into owncloud board) reported/verified that "bug" who have upgraded ONLY owncloud (and didnt touch php or the environment at all). so i would suggest we focus on finding the dirty lil mistake somewhere in the source. :) if you need more information related to php, backend stuff u actually using in your source or may some requirements which are not enlisted in the installation manual, gimme a notice! :D best regards Simon |
|
I had similar problem. This is because of dynamic dns use. |
|
why should a working network setup be responsible for development mistakes? Thanks for the idea, but its not a solution. i prefer the devs do fix this asap among other bugs. |
|
I think I had the same problem:
I think I had the wrong php modules installed or something was missing, because this: resolved the problem! the output was this: |
|
well im capable syncing, and i do meet the written requirements. no need to blindly install any modules. If you name a particular extension they may "need" i can check if i have it enabled or not and may add it to the configuration. blindly installing modules is unprofessional. |
|
I know that the solution for my problem is not professional. I am not a professional. But I had luck. So I hope that someone (a developer) may extract some usefull information out of my post to get an solution for the problem. |
|
I upgraded from 4.7 to 5.02 using the upgrade app. Prior to the upgrade my system had no issues. At this point my admin page has the following line at the top of the page: Your web server is not yet properly setup to allow files synchronization because the WebDAV interface seems to be broken. Please double check the installation guides. File synchronization is working however, and so is the Owncloud app on my Android tablet. The log messages at the bottom of the page show: Error core storage backend \OC\Files\Storage\Dropbox not found April 2, 2013 19:34 Not sure what the Dropbox error is about since I am not using the External Storage app, it's disabled. |
|
I also upgraded from 4.8 to 5.03. With Login https.//myserver:444 I have the following warning: Output log: Clientsync and Webdav works. With Login https://myserver |
|
I have the same issue in OC5.0 on my local setup. I use WinXP, Nginx 1.0.12, PHP 5.4.3, MySQL 5. |
|
Hello I had all the errors above too. How to fix the problem: Open the file /var/www/owncloud/remote.php got to the last line and change require_once to require Also i add in the /etc/hosts my used dynamic domain to the localhost 127.0.0.1. Maybe this helps. |
|
I am still have no idea what things makes this WebDAV failed after all of necessary actions is taken:
note for a2enmod in owncloud documentation should be marked as 'debian or ubuntu' command. |
|
I only get the message, when i am using https to connect to my owncloud instance ... i would like to use https, but it seems not to work correctly :( |
|
@JFOC please send a pull request to the documentation repo, its really easy to do ;) |
|
The same problem here. And I have this in my warning log file: |
|
@purewooder your problem is that your webserver can't connect to itself |
|
Same problem too. My warning log file says : OS : Linux Gentoo |
|
I had the same situation as mrvanes and steveAliff. Add a line to /etc/hosts:
|
|
Hello everyone, who is getting this issue. I've realized, that the strange warning message appears if I use the domain name instead of the IP address (I don't use any forwarding). http://webservices.home.net/owncloud/index.php/settings/admin
if I change the address as follows: So I hope the information will help. |
|
I added: 'overwritehost' => '192.168.1.1' into config/config.php $CONFIG array and the message disapeard. Be sure to check if you're behind a NAT like me and whats your internal server address. Here's where I got the tip: #2511 (comment) |
|
I’m closing this issue because it has been inactive for a few months. This probably means that the issue is not reproducible or it has been fixed in a newer version. Please reopen if you still encounter this issue with the latest stable version (currently ownCloud 5.0.9) and then please use the issue template. You an also contribute directly by providing a patch – see the developer manual. :) Thank you! |
|
I am using 5.0.10 and the issue is still present. But in my case, I was able to resolve it by fixing my firewall, which runs on the same machine as the server. I already posted the finding somewhere else but essentially, the server is doing an access to itself using its external IP address (i.e. not 127.0.0.1) . If the situation is not allowed by iptables, then the server will time out and eventually serve the page to the browser albeit after a long time...... |
|
So what’s the plan of action here? |
|
I came across this too while doing a test-drive install in a VM. The problem was of course with my VM setup. (I used faux vhost name in Apache to mount ownCloud, but forgot to add a corresponding entry in the VM's /etc/hosts, i only had the entry in my bare metal machine's /etc/hosts.) Could you guys add the URL of your test request to the message? If it was present, i'd immediately realize what's going on. Currently it's not visible what kind of check you perform, so it's not obvious how to debug the problem. E.g.: Your web server is not yet properly setup to allow files synchronization because the WebDAV interface seems to be broken -- request to "https://cloud.example.org/remote.php/webdav" failed. Please double check the installation guides. |
|
@jistr Actually the url that we test shoudn't be important. If you would "fix" to this url that you would hide the warning but ownCloud wouldn't work correctly in general because a lot of other services on the internet are still not working. This is the whole point of this warning. |
|
@clauderobi So this warning helped you to fix a bug in your firewall. I still think that this warning is a useful feature and not a bug. |
|
@karlitschek Yeah absolutely, the warning helped me fix a configuration issue with my VM. It's very useful. My point was that if that warning conained a bit more info, i'd realize what's the problem a bit sooner. Just sayin' :) |
|
I had the same error messages as OP, turns out ownCloud does some requests with empty user agent (bad habit?) and my modsec rules didn't like that so they got blocked. Running pretty much standard OWASP rules. Just adjust them or comment them and error message is gone. |
|
If you see this with https but not http; or when you access using your machine host name but not when you use the IP address; then a possible reason is that your certificate name does not match your host name. |
|
Hi, I'm not sure this should be closed. The only way I could get the message to disappear on Windows server was to ensure 127.0.0.1 pointed to the website OwnCloud was running on. That is, in IIS select the site you have OC installed on, open the bindings, Add a new binding with the following values: The problem with this approach is it requires the owncloud site to be set to 127.0.0.1. If you run a local web app on 127.0.0.1, it is no longer available on the same machine as OC. Is it possible to ensure the webdav check using the OC sitename? |
ghost
mentioned this issue
and others
By connecting to admin account and access to: "Admin" screen, the following warning is shown:
Setup Warning
Your web server is not yet properly setup to allow files synchronization because the WebDAV interface seems to be broken. Please double check the installation guides.
I have this message after an installation with the web-installer.
I'm sorry but it still an issue (not resolve as
owncloud-archive/acceptance-testing#21). After an automatic installation, have this kind of message who refer to the manual installation (http://doc.owncloud.org/server/5.0/admin_manual/installation.html) in not helpfull for non-developer users.
Moreover, the alert don't give enough information to understand what is the trouble.
The text was updated successfully, but these errors were encountered: