Post-setup-check fails: WebDAV interface seems to be broken.

[cyberdaemon]

Expected behaviour

Successful installation

Actual behaviour

Unabel to finish installation. Error message:

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.

Steps to reproduce

1. install OC from scratch
2. access webinterface
3. take a look at the nice error :)

Server configuration

Operating system: Centos 6.5

Web server: Apache 2.2.15

Database: MySQL 5

PHP version: 5.3

ownCloud version: 6 RC4

Client configuration

Browser: FF

Operating system: Linux

Logs

Web server error log

client denied by server configuration: /home/www/htdocs/owncloud/data/htaccesstest.txt

There is no htaccesstest.txt in that folder?!

ownCloud log (data/owncloud.log)

{"app":"core","message":"isWebDAVWorking: NO - Reason: Resource not found. (Sabre_DAV_Exception_NotFound)","level":2,"time":"December 09, 2013 22:31:21"}
{"app":"core","message":"User backend OC_User_IMAP not found.","level":3,"time":"December 09, 2013 22:31:22"}
{"app":"core","message":"User backend OC_User_IMAP not found.","level":3,"time":"December 09, 2013 22:31:22"}
{"app":"core","message":"User backend OC_User_IMAP not found.","level":3,"time":"December 09, 2013 22:31:22"}
{"app":"core","message":"User backend OC_User_IMAP not found.","level":3,"time":"December 09, 2013 22:31:22"}
{"app":"core","message":"User backend OC_User_IMAP not found.","level":3,"time":"December 09, 2013 22:31:22"}

Browser log

none

[enoch85]

Same as: #6242 ?

[PVince81]

Usually such errors are related to the environment.
Which PHP version do you have ? PHP 5.3.?
What's the third number ?

The minimum is 5.3.18.

In some environments, the WebDAV check fails.

See #6119 (comment) for a few ways to try and debug this.

[cyberdaemon]

php-5.3.3-26.el6.x86_64

[cyberdaemon]

@PVince81 BTW, where did you find the php prerequisetes as on this site it states =>php-5.3 http://doc.owncloud.org/server/6.0/admin_manual/installation/installation_source.html

[PVince81]

@cyberdaemon good point.
I knew it because of that recent pull request and various discussions: #6169

I think we need to update that doc... I've raised owncloud-archive/documentation#198 to clarify.

[PVince81]

This message sometimes appear even though WebDAV is working.
I think what causes this is that we try to connect to the external WebDAV IP/hostname and in some configs that one isn't accessible when called directly from the server's host (due to proxy/reverse proxy), so the call fails and that message appears.

One idea would be to do the WebDAV check from Javascript instead of PHP, this way the call is made from the right network. What do you think @karlitschek @DeepDiver1975 ?
From JS it should work since it's the same host (no cross-domain issues)

[DeepDiver1975]

One idea would be to do the WebDAV check from Javascript instead of PHP, this way the call is made from the right network. What do you think @karlitschek @DeepDiver1975 ?
From JS it should work since it's the same host (no cross-domain issues)

interesting approach ... why not?

[karlitschek]

Hmm. Interesting idea. I'm not sure if we should invest the work for something hat only happen very rarely. Perhaps a better error message that explains the issue is enough?

[PVince81]

The thing is that I heard of this many times on IRC, in some tickets and
from other users/friends.

Another idea would be to display in the error page the URL that WebDAV
was trying to contact so that admins could check whether it's really
accessible.

Not sure yet which of these solutions is the quickest to implement.

[helmo]

Showing the URL would be a good hint!

I've fixed my own install(running via a https reverse proxy) by adding this to the config/config.php

  'overwritehost' => 'www.exaple.com',
  'overwriteprotocol' => 'https',
  'forcessl' => true,

[PVince81]

I had a quick go at moving the WebDAV check to JS here: #7051 (still WIP)

[python-consulting]

The strangest thing happened : I did a clean install using debian packages (Wheezy) and the post setup check reported a webdav error (misconfiguration). However this error disappeared when I used Chromium (the error was there using firefox).
After that the error was cleared for firefox and the webdav support started working...

[PVince81]

Yes, the WebDAV check is not accurate...

[derjust]

helmo's approach worked at least for my setup.
Thanks!

[ohcibi]

@helmo's approach does not worked for me unfortunately. However what @python-consulting was suggesting did actually work. BUT I was using chrome in the first place and then firefox (and not the other way around). So it seems that just changing the browser makes the test finally pass. (I also confirmed already that webdav worked)

[PVince81]

Obsoleted by #7051
WebDAV check will be done through ajax in the next OC 7 release.