New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup warning : WebDAV interface seems to be broke #2495

Closed
alexisju opened this Issue Mar 21, 2013 · 46 comments

Comments

Projects
None yet
@alexisju

alexisju commented Mar 21, 2013

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
owncloudarchive/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.

@BernhardPosselt

This comment has been minimized.

Show comment
Hide comment
@BernhardPosselt

BernhardPosselt Mar 21, 2013

Contributor

Please read the contribution guidelines ;)

Contributor

BernhardPosselt commented Mar 21, 2013

Please read the contribution guidelines ;)

@BernhardPosselt

This comment has been minimized.

Show comment
Hide comment
@BernhardPosselt
Contributor

BernhardPosselt commented Mar 21, 2013

@DeepDiver1975

This comment has been minimized.

Show comment
Hide comment
@DeepDiver1975

DeepDiver1975 Mar 21, 2013

Member

@alexisju please post your logs files

Member

DeepDiver1975 commented Mar 21, 2013

@alexisju please post your logs files

@alexisju

This comment has been minimized.

Show comment
Hide comment
@alexisju

alexisju Mar 21, 2013

INSTALL 1 :
Operating system: Linux mini 3.2.0-39-powerpc-smp #62-Ubuntu

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
http://php5-3.web4all.fr/

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
Warning PHP curl_setopt_array() [function.curl-setopt-array]: CURLOPT_FOLLOWLOCATION cannot be activated when safe_mode is enabled or an open_basedir is set at /datas/vol2/xxxx/var/www/effingo.be/htdocs/owncloud/3rdparty/Sabre/DAV/Client.php#464

ps: on both install, with same server config, all was worked fine with 4.5* version.
Now, sync is impossible with client due to this issue

alexisju commented Mar 21, 2013

INSTALL 1 :
Operating system: Linux mini 3.2.0-39-powerpc-smp #62-Ubuntu

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
http://php5-3.web4all.fr/

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
Warning PHP curl_setopt_array() [function.curl-setopt-array]: CURLOPT_FOLLOWLOCATION cannot be activated when safe_mode is enabled or an open_basedir is set at /datas/vol2/xxxx/var/www/effingo.be/htdocs/owncloud/3rdparty/Sabre/DAV/Client.php#464

ps: on both install, with same server config, all was worked fine with 4.5* version.
Now, sync is impossible with client due to this issue

@DeepDiver1975

This comment has been minimized.

Show comment
Hide comment
@DeepDiver1975

DeepDiver1975 Mar 21, 2013

Member

Looks like safe_mode is enabled - please disable that:

Warning PHP curl_setopt_array() [function.curl-setopt-array]: CURLOPT_FOLLOWLOCATION cannot be activated when safe_mode is enabled or an open_basedir is set at /datas/vol2/w4a134834/var/www/effingo.be/htdocs/owncloud/3rdparty/Sabre/DAV/Client.php#464
Member

DeepDiver1975 commented Mar 21, 2013

Looks like safe_mode is enabled - please disable that:

Warning PHP curl_setopt_array() [function.curl-setopt-array]: CURLOPT_FOLLOWLOCATION cannot be activated when safe_mode is enabled or an open_basedir is set at /datas/vol2/w4a134834/var/www/effingo.be/htdocs/owncloud/3rdparty/Sabre/DAV/Client.php#464
@DeepDiver1975

This comment has been minimized.

Show comment
Hide comment
@DeepDiver1975

DeepDiver1975 Mar 21, 2013

Member

Second:
What version number is in your 3rdparty/Sabre/DAV/Version.php

Member

DeepDiver1975 commented Mar 21, 2013

Second:
What version number is in your 3rdparty/Sabre/DAV/Version.php

@alexisju

This comment has been minimized.

Show comment
Hide comment
@alexisju

alexisju Mar 21, 2013

The sabre version is '1.7.5'

on install 2, it is a mutualized server; i cannot disable safe_mode

alexisju commented Mar 21, 2013

The sabre version is '1.7.5'

on install 2, it is a mutualized server; i cannot disable safe_mode

@DeepDiver1975

This comment has been minimized.

Show comment
Hide comment
@DeepDiver1975

DeepDiver1975 Mar 21, 2013

Member

on install 2, it is a mutualized server; i cannot disable safe_mode

generally speaking ownCloud cannot run in safe_mode

Member

DeepDiver1975 commented Mar 21, 2013

on install 2, it is a mutualized server; i cannot disable safe_mode

generally speaking ownCloud cannot run in safe_mode

@alexisju

This comment has been minimized.

Show comment
Hide comment
@alexisju

alexisju Mar 21, 2013

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)

alexisju commented Mar 21, 2013

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)

@DeepDiver1975

This comment has been minimized.

Show comment
Hide comment
@DeepDiver1975

DeepDiver1975 Mar 21, 2013

Member

I'm sorry, i just rechecked: safe_mod is off on both install

the curl warning is telling a different story ;-)

Member

DeepDiver1975 commented Mar 21, 2013

I'm sorry, i just rechecked: safe_mod is off on both install

the curl warning is telling a different story ;-)

@bartv2

This comment has been minimized.

Show comment
Hide comment
@bartv2

bartv2 Mar 21, 2013

Member

open_basedir can also be the problem

Member

bartv2 commented Mar 21, 2013

open_basedir can also be the problem

@JFOC

This comment has been minimized.

Show comment
Hide comment
@JFOC

JFOC Mar 21, 2013

I am also having problem but for MacOSX 1.2.1 Client http://forum.owncloud.org/viewtopic.php?f=14&t=9067
openbasedir is disabled for current user, safe_mode is off

JFOC commented Mar 21, 2013

I am also having problem but for MacOSX 1.2.1 Client http://forum.owncloud.org/viewtopic.php?f=14&t=9067
openbasedir is disabled for current user, safe_mode is off

@mrvanes

This comment has been minimized.

Show comment
Hide comment
@mrvanes

mrvanes Mar 21, 2013

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).

mrvanes commented Mar 21, 2013

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).

@mrvanes

This comment has been minimized.

Show comment
Hide comment
@mrvanes

mrvanes Mar 21, 2013

btw: The warning I had was
isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception' with message '[CURL] Error while making request: couldn't connect to host (error code: 7)'

mrvanes commented Mar 21, 2013

btw: The warning I had was
isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception' with message '[CURL] Error while making request: couldn't connect to host (error code: 7)'

@DeepDiver1975

This comment has been minimized.

Show comment
Hide comment
@DeepDiver1975

DeepDiver1975 Mar 21, 2013

Member

btw: The warning I had was
isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception' with message '[CURL] Error while making request: couldn't connect to host (error code: 7)'

This at the end means your setup is not proper to allow WebDAV and sync clients to work without issues.
Fix the setup -> fix webdav and have fun with syncing.

Generally speaking:
the webdav test we have incorporated will give you hints that your web server setup is not proper.
We cannot solve all your setup issues and we cannot foresee all configuration combinations.
The details error message is always int the logs - we try to help out as good as we can.

There are cases where we most probably produce false positives - we will fix this if possible.

Member

DeepDiver1975 commented Mar 21, 2013

btw: The warning I had was
isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception' with message '[CURL] Error while making request: couldn't connect to host (error code: 7)'

This at the end means your setup is not proper to allow WebDAV and sync clients to work without issues.
Fix the setup -> fix webdav and have fun with syncing.

Generally speaking:
the webdav test we have incorporated will give you hints that your web server setup is not proper.
We cannot solve all your setup issues and we cannot foresee all configuration combinations.
The details error message is always int the logs - we try to help out as good as we can.

There are cases where we most probably produce false positives - we will fix this if possible.

@SteveAliff

This comment has been minimized.

Show comment
Hide comment
@SteveAliff

SteveAliff Mar 22, 2013

My situation appears similar (identical?) to what mrvanes reported. My
ownCloud server is NATed with a high port mapped to 443,
i.e. connecting to https://myserver.realdomain:8888/owncloud port
forwards to https://192.168.1.123:443/owncloud on my LAN.

If I connect to the LAN address, e.g. https://192.168.1.123/owncloud I
do NOT get the error message. If I connect to the WAN address, I do.

SteveAliff commented Mar 22, 2013

My situation appears similar (identical?) to what mrvanes reported. My
ownCloud server is NATed with a high port mapped to 443,
i.e. connecting to https://myserver.realdomain:8888/owncloud port
forwards to https://192.168.1.123:443/owncloud on my LAN.

If I connect to the LAN address, e.g. https://192.168.1.123/owncloud I
do NOT get the error message. If I connect to the WAN address, I do.

@BernhardPosselt

This comment has been minimized.

Show comment
Hide comment
@BernhardPosselt
Contributor

BernhardPosselt commented Mar 22, 2013

#2511 dup?

@simonlange

This comment has been minimized.

Show comment
Hide comment
@simonlange

simonlange Mar 27, 2013

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:

sWebDAVWorking: NO - Reason: exception 'InvalidArgumentException' with message 'The passed data is not valid XML' in /var/www/slc/htdocs/cloud/3rdparty/Sabre/DAV/Client.php:531
Stack trace:
#0 /var/www/slc/htdocs/cloud/3rdparty/Sabre/DAV/Client.php(181): Sabre_DAV_Client->parseMultiStatus(false)
#1 /var/www/slc/htdocs/cloud/lib/util.php(590): Sabre_DAV_Client->propFind('', Array)
#2 /var/www/slc/htdocs/cloud/settings/admin.php(34): OC_Util::isWebDAVWorking()
#3 /var/www/slc/htdocs/cloud/lib/route.php(113) : runtime-created function(1): require_once('/var/www/slc/ht...')
#4 [internal function]: __lambda_func(Array)
#5 /var/www/slc/htdocs/cloud/lib/router.php(127): call_user_func('?lambda_908', Array)
#6 /var/www/slc/htdocs/cloud/lib/base.php(606): OC_Router->match('/settings/admin')
#7 /var/www/slc/htdocs/cloud/index.php(28): OC::handleRequest()
#8 {main}

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
PS: just edit the "code" section for better reading.

simonlange commented Mar 27, 2013

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:

sWebDAVWorking: NO - Reason: exception 'InvalidArgumentException' with message 'The passed data is not valid XML' in /var/www/slc/htdocs/cloud/3rdparty/Sabre/DAV/Client.php:531
Stack trace:
#0 /var/www/slc/htdocs/cloud/3rdparty/Sabre/DAV/Client.php(181): Sabre_DAV_Client->parseMultiStatus(false)
#1 /var/www/slc/htdocs/cloud/lib/util.php(590): Sabre_DAV_Client->propFind('', Array)
#2 /var/www/slc/htdocs/cloud/settings/admin.php(34): OC_Util::isWebDAVWorking()
#3 /var/www/slc/htdocs/cloud/lib/route.php(113) : runtime-created function(1): require_once('/var/www/slc/ht...')
#4 [internal function]: __lambda_func(Array)
#5 /var/www/slc/htdocs/cloud/lib/router.php(127): call_user_func('?lambda_908', Array)
#6 /var/www/slc/htdocs/cloud/lib/base.php(606): OC_Router->match('/settings/admin')
#7 /var/www/slc/htdocs/cloud/index.php(28): OC::handleRequest()
#8 {main}

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
PS: just edit the "code" section for better reading.

@ldanko

This comment has been minimized.

Show comment
Hide comment
@ldanko

ldanko Mar 29, 2013

I had similar problem.

This is because of dynamic dns use.
To solve it, simply modify your /etc/hosts file
http://alexis.no-ip.org/info.php 127.0.0.1

ldanko commented Mar 29, 2013

I had similar problem.

This is because of dynamic dns use.
To solve it, simply modify your /etc/hosts file
http://alexis.no-ip.org/info.php 127.0.0.1

@simonlange

This comment has been minimized.

Show comment
Hide comment
@simonlange

simonlange Mar 29, 2013

why should a working network setup be responsible for development mistakes?
and why should anyone modifying a working network setup to a wrong configured one because of ONE piece of php code? oO

Thanks for the idea, but its not a solution. i prefer the devs do fix this asap among other bugs.

simonlange commented Mar 29, 2013

why should a working network setup be responsible for development mistakes?
and why should anyone modifying a working network setup to a wrong configured one because of ONE piece of php code? oO

Thanks for the idea, but its not a solution. i prefer the devs do fix this asap among other bugs.

@kaoz3000

This comment has been minimized.

Show comment
Hide comment
@kaoz3000

kaoz3000 Mar 31, 2013

I think I had the same problem:

  • webDav warning in Admin Panel
  • unable to sync with desktop or iPhone client

I think I had the wrong php modules installed or something was missing, because this:

apt-get install libapache2-mod-php5 libapache2-mod-ruby libapache2-mod-python php5 php5-common php5-curl php5-dev php5-gd php5-idn php-pear php5-imagick php5-imap php5-mcrypt php5-memcache php5-mhash php5-ming php5-mysql php5-pspell php5-recode php5-snmp php5-sqlite php5-suhosin php5-tidy php5-xcache php5-xmlrpc php5-xsl

resolved the problem!

the output was this:

root@host:/var/www/owncloud# apt-get install libapache2-mod-php5 libapache2-mod-ruby libapache2-mod-python php5 php5-common php5-curl php5-dev php5-gd php5-idn php-pear php5-imagick php5-imap php5-mcrypt php5-memcache php5-mhash php5-ming php5-mysql php5-pspell php5-recode php5-snmp php5-sqlite php5-suhosin php5-tidy php5-xcache php5-xmlrpc php5-xsl
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut       
Statusinformationen werden eingelesen... Fertig
Hinweis: »php5-common« wird an Stelle von »php5-mhash« gewählt
php-pear ist schon die neueste Version.
php5 ist schon die neueste Version.
php5-common ist schon die neueste Version.
php5-common wurde als manuell installiert festgelegt.
php5-curl ist schon die neueste Version.
php5-gd ist schon die neueste Version.
php5-mcrypt ist schon die neueste Version.
php5-mcrypt wurde als manuell installiert festgelegt.
php5-mysql ist schon die neueste Version.
php5-sqlite ist schon die neueste Version.
Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt:
  libcap-ng0
Verwenden Sie »apt-get autoremove«, um sie zu entfernen.
Die folgenden zusätzlichen Pakete werden installiert:
  autoconf automake libapache-ruby1.8 libaspell15 libc-client2007e libgif4 libice6 libjasper1 liblcms1 liblqr-1-0 libmagickcore3
  libmagickwand3 libming1 libperl5.10 libpython2.6 libreadline5 librecode0 libruby1.8 libsensors4 libsm6 libsnmp-base libsnmp15
  libtidy-0.99-0 libtiff4 libtool libxext6 libxslt1.1 libxt6 m4 mlock perl perl-base perl-modules python python-central
  python-minimal python2.6 python2.6-minimal shtool x11-common
Vorgeschlagene Pakete:
  autoconf2.13 autoconf-archive gnu-standards autoconf-doc libapache2-mod-python-doc liberuby aspell uw-mailutils libjasper-runtime
  liblcms-utils libmagickcore3-extra snmp-mibs-downloader libtool-doc automaken gfortran fortran95-compiler gcj perl-doc
  libterm-readline-gnu-perl libterm-readline-perl-perl memcached python-tk python-profiler python2.6-doc python2.6-profiler
  binfmt-support
Empfohlene Pakete:
  aspell-en aspell-dictionary aspell6a-dictionary ghostscript gsfonts lm-sensors
Die folgenden Pakete werden ENTFERNT:
  libapache2-mod-php5filter
Die folgenden NEUEN Pakete werden installiert:
  autoconf automake libapache-ruby1.8 libapache2-mod-php5 libapache2-mod-python libapache2-mod-ruby libaspell15 libc-client2007e
  libgif4 libice6 libjasper1 liblcms1 liblqr-1-0 libmagickcore3 libmagickwand3 libming1 libperl5.10 libpython2.6 libreadline5
  librecode0 libruby1.8 libsensors4 libsm6 libsnmp-base libsnmp15 libtidy-0.99-0 libtiff4 libtool libxext6 libxslt1.1 libxt6 m4
  mlock php5-dev php5-idn php5-imagick php5-imap php5-memcache php5-ming php5-pspell php5-recode php5-snmp php5-suhosin php5-tidy
  php5-xcache php5-xmlrpc php5-xsl python python-central python-minimal python2.6 python2.6-minimal shtool x11-common
Die folgenden Pakete werden aktualisiert (Upgrade):
  perl perl-base perl-modules
3 aktualisiert, 54 neu installiert, 1 zu entfernen und 127 nicht aktualisiert.
Es müssen 31,4 MB an Archiven heruntergeladen werden.

kaoz3000 commented Mar 31, 2013

I think I had the same problem:

  • webDav warning in Admin Panel
  • unable to sync with desktop or iPhone client

I think I had the wrong php modules installed or something was missing, because this:

apt-get install libapache2-mod-php5 libapache2-mod-ruby libapache2-mod-python php5 php5-common php5-curl php5-dev php5-gd php5-idn php-pear php5-imagick php5-imap php5-mcrypt php5-memcache php5-mhash php5-ming php5-mysql php5-pspell php5-recode php5-snmp php5-sqlite php5-suhosin php5-tidy php5-xcache php5-xmlrpc php5-xsl

resolved the problem!

the output was this:

root@host:/var/www/owncloud# apt-get install libapache2-mod-php5 libapache2-mod-ruby libapache2-mod-python php5 php5-common php5-curl php5-dev php5-gd php5-idn php-pear php5-imagick php5-imap php5-mcrypt php5-memcache php5-mhash php5-ming php5-mysql php5-pspell php5-recode php5-snmp php5-sqlite php5-suhosin php5-tidy php5-xcache php5-xmlrpc php5-xsl
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut       
Statusinformationen werden eingelesen... Fertig
Hinweis: »php5-common« wird an Stelle von »php5-mhash« gewählt
php-pear ist schon die neueste Version.
php5 ist schon die neueste Version.
php5-common ist schon die neueste Version.
php5-common wurde als manuell installiert festgelegt.
php5-curl ist schon die neueste Version.
php5-gd ist schon die neueste Version.
php5-mcrypt ist schon die neueste Version.
php5-mcrypt wurde als manuell installiert festgelegt.
php5-mysql ist schon die neueste Version.
php5-sqlite ist schon die neueste Version.
Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt:
  libcap-ng0
Verwenden Sie »apt-get autoremove«, um sie zu entfernen.
Die folgenden zusätzlichen Pakete werden installiert:
  autoconf automake libapache-ruby1.8 libaspell15 libc-client2007e libgif4 libice6 libjasper1 liblcms1 liblqr-1-0 libmagickcore3
  libmagickwand3 libming1 libperl5.10 libpython2.6 libreadline5 librecode0 libruby1.8 libsensors4 libsm6 libsnmp-base libsnmp15
  libtidy-0.99-0 libtiff4 libtool libxext6 libxslt1.1 libxt6 m4 mlock perl perl-base perl-modules python python-central
  python-minimal python2.6 python2.6-minimal shtool x11-common
Vorgeschlagene Pakete:
  autoconf2.13 autoconf-archive gnu-standards autoconf-doc libapache2-mod-python-doc liberuby aspell uw-mailutils libjasper-runtime
  liblcms-utils libmagickcore3-extra snmp-mibs-downloader libtool-doc automaken gfortran fortran95-compiler gcj perl-doc
  libterm-readline-gnu-perl libterm-readline-perl-perl memcached python-tk python-profiler python2.6-doc python2.6-profiler
  binfmt-support
Empfohlene Pakete:
  aspell-en aspell-dictionary aspell6a-dictionary ghostscript gsfonts lm-sensors
Die folgenden Pakete werden ENTFERNT:
  libapache2-mod-php5filter
Die folgenden NEUEN Pakete werden installiert:
  autoconf automake libapache-ruby1.8 libapache2-mod-php5 libapache2-mod-python libapache2-mod-ruby libaspell15 libc-client2007e
  libgif4 libice6 libjasper1 liblcms1 liblqr-1-0 libmagickcore3 libmagickwand3 libming1 libperl5.10 libpython2.6 libreadline5
  librecode0 libruby1.8 libsensors4 libsm6 libsnmp-base libsnmp15 libtidy-0.99-0 libtiff4 libtool libxext6 libxslt1.1 libxt6 m4
  mlock php5-dev php5-idn php5-imagick php5-imap php5-memcache php5-ming php5-pspell php5-recode php5-snmp php5-suhosin php5-tidy
  php5-xcache php5-xmlrpc php5-xsl python python-central python-minimal python2.6 python2.6-minimal shtool x11-common
Die folgenden Pakete werden aktualisiert (Upgrade):
  perl perl-base perl-modules
3 aktualisiert, 54 neu installiert, 1 zu entfernen und 127 nicht aktualisiert.
Es müssen 31,4 MB an Archiven heruntergeladen werden.
@simonlange

This comment has been minimized.

Show comment
Hide comment
@simonlange

simonlange Mar 31, 2013

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.

simonlange commented Mar 31, 2013

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.

@kaoz3000

This comment has been minimized.

Show comment
Hide comment
@kaoz3000

kaoz3000 Mar 31, 2013

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.

kaoz3000 commented Mar 31, 2013

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.

@bturrie

This comment has been minimized.

Show comment
Hide comment
@bturrie

bturrie Apr 3, 2013

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.

bturrie commented Apr 3, 2013

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.

@td007

This comment has been minimized.

Show comment
Hide comment
@td007

td007 Apr 4, 2013

I also upgraded from 4.8 to 5.03.

With Login https.//myserver:444

I have the following warning:
"Einrichtungswarnung Dein Web-Server ist noch nicht für Datei-Synchronisation bereit, weil die WebDAV-Schnittstelle vermutlich defekt ist."

Output log:
isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception' with message '[CURL] Error while making request: couldn't connect to host (error code: 7)' in /var/www/html/owncloud/3rdparty/Sabre/DAV/Client.php:410 Stack trace: #0 /var/www/html/owncloud/3rdparty/Sabre/DAV/Client.php(179): Sabre_DAV_Client->request('PROPFIND', '', '<?xml version="...', Array) #1 /var/www/html/owncloud/lib/util.php(590): Sabre_DAV_Client->propFind('', Array) #2 /var/www/html/owncloud/settings/admin.php(34): OC_Util::isWebDAVWorking() #3 /var/www/html/owncloud/lib/route.php(113) : runtime-created function(1): require_once('/var/www/html/o...') #4 [internal function]: __lambda_func(Array) #5 /var/www/html/owncloud/lib/router.php(127): call_user_func('?lambda_789', Array) #6 /var/www/html/owncloud/lib/base.php(608): OC_Router->match('/settings/admin') #7 /var/www/html/owncloud/index.php(28): OC::handleRequest() #8 {main}

Clientsync and Webdav works.

With Login https://myserver
I have no warning!

td007 commented Apr 4, 2013

I also upgraded from 4.8 to 5.03.

With Login https.//myserver:444

I have the following warning:
"Einrichtungswarnung Dein Web-Server ist noch nicht für Datei-Synchronisation bereit, weil die WebDAV-Schnittstelle vermutlich defekt ist."

Output log:
isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception' with message '[CURL] Error while making request: couldn't connect to host (error code: 7)' in /var/www/html/owncloud/3rdparty/Sabre/DAV/Client.php:410 Stack trace: #0 /var/www/html/owncloud/3rdparty/Sabre/DAV/Client.php(179): Sabre_DAV_Client->request('PROPFIND', '', '<?xml version="...', Array) #1 /var/www/html/owncloud/lib/util.php(590): Sabre_DAV_Client->propFind('', Array) #2 /var/www/html/owncloud/settings/admin.php(34): OC_Util::isWebDAVWorking() #3 /var/www/html/owncloud/lib/route.php(113) : runtime-created function(1): require_once('/var/www/html/o...') #4 [internal function]: __lambda_func(Array) #5 /var/www/html/owncloud/lib/router.php(127): call_user_func('?lambda_789', Array) #6 /var/www/html/owncloud/lib/base.php(608): OC_Router->match('/settings/admin') #7 /var/www/html/owncloud/index.php(28): OC::handleRequest() #8 {main}

Clientsync and Webdav works.

With Login https://myserver
I have no warning!

@GDI123

This comment has been minimized.

Show comment
Hide comment
@GDI123

GDI123 Apr 5, 2013

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.
I 've perform some debug of this situation and I found that Sabre DAV Server wait for Authentification header from Sabre DAV Client then it try to connect to server in function isWebDAVWorking() from lib/util.php. But I didn't found any place there Authorization header was sent. I didn't seen the setup warning like in first message, I just seen 504 error instead of it. The $_SERVER['HTTP_AUTHORIZATION'] variable is empty.
Could somebody explain how should work Sabre DAV Server in this case?

GDI123 commented Apr 5, 2013

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.
I 've perform some debug of this situation and I found that Sabre DAV Server wait for Authentification header from Sabre DAV Client then it try to connect to server in function isWebDAVWorking() from lib/util.php. But I didn't found any place there Authorization header was sent. I didn't seen the setup warning like in first message, I just seen 504 error instead of it. The $_SERVER['HTTP_AUTHORIZATION'] variable is empty.
Could somebody explain how should work Sabre DAV Server in this case?

@prdatur

This comment has been minimized.

Show comment
Hide comment
@prdatur

prdatur Apr 5, 2013

Hello I had all the errors above too.
I finally got it to work, so the welcome screen to download the app appears without giving an error.

How to fix the problem:
sWebDAVWorking: NO - Reason: exception 'InvalidArgumentException' with message 'The passed data is not valid XML' in /var/www/slc/htdocs/cloud/3rdparty/Sabre/DAV/Client.php:531

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.
I added the entry to the host file because my router has a "nice feature" it routes all internal requests to my public dynamic ip to the router.....

Maybe this helps.

prdatur commented Apr 5, 2013

Hello I had all the errors above too.
I finally got it to work, so the welcome screen to download the app appears without giving an error.

How to fix the problem:
sWebDAVWorking: NO - Reason: exception 'InvalidArgumentException' with message 'The passed data is not valid XML' in /var/www/slc/htdocs/cloud/3rdparty/Sabre/DAV/Client.php:531

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.
I added the entry to the host file because my router has a "nice feature" it routes all internal requests to my public dynamic ip to the router.....

Maybe this helps.

@JFOC

This comment has been minimized.

Show comment
Hide comment
@JFOC

JFOC Apr 6, 2013

I am still have no idea what things makes this WebDAV failed after all of necessary actions is taken:

  • disable all other DAV server like in cPanel disable webdisk webdav
  • mod rewrite on
  • open_basedir are disabled from both apache and php
  • safe_mode is off
  • disable firewall for test

note for a2enmod in owncloud documentation should be marked as 'debian or ubuntu' command.

JFOC commented Apr 6, 2013

I am still have no idea what things makes this WebDAV failed after all of necessary actions is taken:

  • disable all other DAV server like in cPanel disable webdisk webdav
  • mod rewrite on
  • open_basedir are disabled from both apache and php
  • safe_mode is off
  • disable firewall for test

note for a2enmod in owncloud documentation should be marked as 'debian or ubuntu' command.

@davidreher

This comment has been minimized.

Show comment
Hide comment
@davidreher

davidreher Apr 11, 2013

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 :(

davidreher commented Apr 11, 2013

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 :(

@BernhardPosselt

This comment has been minimized.

Show comment
Hide comment
@BernhardPosselt

BernhardPosselt Apr 11, 2013

Contributor

@JFOC please send a pull request to the documentation repo, its really easy to do ;)

Contributor

BernhardPosselt commented Apr 11, 2013

@JFOC please send a pull request to the documentation repo, its really easy to do ;)

@purewooder

This comment has been minimized.

Show comment
Hide comment
@purewooder

purewooder Apr 14, 2013

The same problem here. And I have this in my warning log file:
isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception' with message '[CURL] Error while making request: couldn't connect to host (error code: 7)' in /var/www/html/cloud/3rdparty/Sabre/DAV/Client.php:410 Stack trace: #0 /var/www/html/cloud/3rdparty/Sabre/DAV/Client.php(179): Sabre_DAV_Client->request('PROPFIND', '', '<?xml version="...', Array) #1 /var/www/html/cloud/lib/util.php(590): Sabre_DAV_Client->propFind('', Array) #2 /var/www/html/cloud/settings/admin.php(34): OC_Util::isWebDAVWorking() #3 /var/www/html/cloud/lib/route.php(113) : runtime-created function(1): require_once('/var/www/html/c...') #4 [internal function]: __lambda_func(Array) #5 /var/www/html/cloud/lib/router.php(127): call_user_func('?lambda_8', Array) #6 /var/www/html/cloud/lib/base.php(608): OC_Router->match('/settings/admin') #7 /var/www/html/cloud/index.php(28): OC::handleRequest() #8 {main}

purewooder commented Apr 14, 2013

The same problem here. And I have this in my warning log file:
isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception' with message '[CURL] Error while making request: couldn't connect to host (error code: 7)' in /var/www/html/cloud/3rdparty/Sabre/DAV/Client.php:410 Stack trace: #0 /var/www/html/cloud/3rdparty/Sabre/DAV/Client.php(179): Sabre_DAV_Client->request('PROPFIND', '', '<?xml version="...', Array) #1 /var/www/html/cloud/lib/util.php(590): Sabre_DAV_Client->propFind('', Array) #2 /var/www/html/cloud/settings/admin.php(34): OC_Util::isWebDAVWorking() #3 /var/www/html/cloud/lib/route.php(113) : runtime-created function(1): require_once('/var/www/html/c...') #4 [internal function]: __lambda_func(Array) #5 /var/www/html/cloud/lib/router.php(127): call_user_func('?lambda_8', Array) #6 /var/www/html/cloud/lib/base.php(608): OC_Router->match('/settings/admin') #7 /var/www/html/cloud/index.php(28): OC::handleRequest() #8 {main}

@bartv2

This comment has been minimized.

Show comment
Hide comment
@bartv2

bartv2 Apr 16, 2013

Member

@purewooder your problem is that your webserver can't connect to itself

Member

bartv2 commented Apr 16, 2013

@purewooder your problem is that your webserver can't connect to itself

@gdmnt

This comment has been minimized.

Show comment
Hide comment
@gdmnt

gdmnt Apr 18, 2013

Same problem too. My warning log file says :
isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception' with message '[CURL] Error while making request: Failed connect to host; Connection timed out (error code: 7)' in /var/www/localhost/htdocs/owncloud/3rdparty/Sabre/DAV/Client.php:410 Stack trace: #0 /var/www/localhost/htdocs/owncloud/3rdparty/Sabre/DAV/Client.php(179): Sabre_DAV_Client->request('PROPFIND', '', '<?xml version="...', Array) #1 /var/www/localhost/htdocs/owncloud/lib/util.php(590): Sabre_DAV_Client->propFind('', Array) #2 /var/www/localhost/htdocs/owncloud/settings/admin.php(34): OC_Util::isWebDAVWorking() #3 /var/www/localhost/htdocs/owncloud/lib/route.php(113) : runtime-created function(1): require_once('/var/www/localh...') #4 [internal function]: __lambda_func(Array) #5 /var/www/localhost/htdocs/owncloud/lib/router.php(127): call_user_func('?lambda_256', Array) #6 /var/www/localhost/htdocs/owncloud/lib/base.php(608): OC_Router->match('/settings/admin') #7 /var/www/localhost/htdocs/owncloud/index.php(28): OC::handleRequest() #8 {main}

OS : Linux Gentoo
webserver : lighttpd

gdmnt commented Apr 18, 2013

Same problem too. My warning log file says :
isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception' with message '[CURL] Error while making request: Failed connect to host; Connection timed out (error code: 7)' in /var/www/localhost/htdocs/owncloud/3rdparty/Sabre/DAV/Client.php:410 Stack trace: #0 /var/www/localhost/htdocs/owncloud/3rdparty/Sabre/DAV/Client.php(179): Sabre_DAV_Client->request('PROPFIND', '', '<?xml version="...', Array) #1 /var/www/localhost/htdocs/owncloud/lib/util.php(590): Sabre_DAV_Client->propFind('', Array) #2 /var/www/localhost/htdocs/owncloud/settings/admin.php(34): OC_Util::isWebDAVWorking() #3 /var/www/localhost/htdocs/owncloud/lib/route.php(113) : runtime-created function(1): require_once('/var/www/localh...') #4 [internal function]: __lambda_func(Array) #5 /var/www/localhost/htdocs/owncloud/lib/router.php(127): call_user_func('?lambda_256', Array) #6 /var/www/localhost/htdocs/owncloud/lib/base.php(608): OC_Router->match('/settings/admin') #7 /var/www/localhost/htdocs/owncloud/index.php(28): OC::handleRequest() #8 {main}

OS : Linux Gentoo
webserver : lighttpd

@daltam

This comment has been minimized.

Show comment
Hide comment
@daltam

daltam Apr 28, 2013

I had the same situation as mrvanes and steveAliff.
My ownCloud server is NATed with a high port mapped to 443,
i.e. connecting to https://myserver.realdomain:8888/owncloud port
forwards to https://192.168.1.123:443/owncloud on my LAN.

Add a line to /etc/hosts:
127.0.0.1 myserver.realdomain
and execute the iptables command:

iptables -t nat -A OUTPUT -p tcp --dport 8888 -j DNAT --to 127.0.0.1:443

daltam commented Apr 28, 2013

I had the same situation as mrvanes and steveAliff.
My ownCloud server is NATed with a high port mapped to 443,
i.e. connecting to https://myserver.realdomain:8888/owncloud port
forwards to https://192.168.1.123:443/owncloud on my LAN.

Add a line to /etc/hosts:
127.0.0.1 myserver.realdomain
and execute the iptables command:

iptables -t nat -A OUTPUT -p tcp --dport 8888 -j DNAT --to 127.0.0.1:443

@fancer

This comment has been minimized.

Show comment
Hide comment
@fancer

fancer May 9, 2013

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
leads to

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.

if I change the address as follows:
http://192.168.1.252/owncloud/index.php/settings/admin
the message disappears.

So I hope the information will help.

fancer commented May 9, 2013

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
leads to

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.

if I change the address as follows:
http://192.168.1.252/owncloud/index.php/settings/admin
the message disappears.

So I hope the information will help.

@khartahk

This comment has been minimized.

Show comment
Hide comment
@khartahk

khartahk Jun 22, 2013

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)

khartahk commented Jun 22, 2013

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)

@jancborchardt

This comment has been minimized.

Show comment
Hide comment
@jancborchardt

jancborchardt Aug 8, 2013

Member

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!

Member

jancborchardt commented Aug 8, 2013

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!

@clauderobi

This comment has been minimized.

Show comment
Hide comment
@clauderobi

clauderobi Aug 18, 2013

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......

clauderobi commented Aug 18, 2013

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......

@jancborchardt

This comment has been minimized.

Show comment
Hide comment
@jancborchardt

jancborchardt Aug 23, 2013

Member

So what’s the plan of action here?

Member

jancborchardt commented Aug 23, 2013

So what’s the plan of action here?

@jancborchardt jancborchardt reopened this Aug 23, 2013

@jistr

This comment has been minimized.

Show comment
Hide comment
@jistr

jistr Sep 21, 2013

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 commented Sep 21, 2013

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.

@karlitschek

This comment has been minimized.

Show comment
Hide comment
@karlitschek

karlitschek Sep 21, 2013

Member

@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.
I still think that this warning shoud be shown if full internet access ist not working.
This is a feature and not a bug.

Member

karlitschek commented Sep 21, 2013

@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.
I still think that this warning shoud be shown if full internet access ist not working.
This is a feature and not a bug.

@karlitschek

This comment has been minimized.

Show comment
Hide comment
@karlitschek

karlitschek Sep 21, 2013

Member

@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.

Member

karlitschek commented Sep 21, 2013

@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.

@jistr

This comment has been minimized.

Show comment
Hide comment
@jistr

jistr Sep 21, 2013

@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' :)

jistr commented Sep 21, 2013

@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' :)

@scarleo

This comment has been minimized.

Show comment
Hide comment
@scarleo

scarleo Mar 1, 2014

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.

scarleo commented Mar 1, 2014

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.

@JanneM

This comment has been minimized.

Show comment
Hide comment
@JanneM

JanneM May 13, 2014

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.

JanneM commented May 13, 2014

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.

@gedm

This comment has been minimized.

Show comment
Hide comment
@gedm

gedm Aug 30, 2014

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:
Type: http
IP Address: All assigned
Port: 80
Host name:
(Host name blank)

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?

gedm commented Aug 30, 2014

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:
Type: http
IP Address: All assigned
Port: 80
Host name:
(Host name blank)

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment