<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Pierre,<div><br></div><div>I am a bit surprised because what you are describing (called Server Name Indication (SNI) btw) should work perfectly fine with mod_ssl, provided that:</div><div><ul style="color: rgb(0, 0, 0); font-family: sans-serif; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); "><li>Use OpenSSL 0.9.8f or later<span class="anchor" id="line-57"></span></li><li>Build OpenSSL with the TLS Extensions option enabled (option enable-tlsext; OpenSSL 0.9.8k and later has this enabled by default).<span class="anchor" id="line-58"></span></li><li>Apache must have been built with that OpenSSL (./configure --with-ssl=/path/to/your/openssl). In that case, mod_ssl will automatically detect the availability of the TLS extensions and support SNI.<span class="anchor" id="line-59"></span></li><li>Apache must use that OpenSSL at run-time, which might require setting LD_LIBRARY_PATH or equivalent to point to that OpenSSL, maybe in bin/envvars. (You'll get unresolved symbol errors at Apache startup if Apache was built with SNI but isn't finding the right openssl libraries at run-time.)</li></ul><div><font class="Apple-style-span" face="sans-serif">(see <a href="http://wiki.apache.org/httpd/NameBasedSSLVHostsWithSNI">http://wiki.apache.org/httpd/NameBasedSSLVHostsWithSNI</a>)</font></div></div><div><font class="Apple-style-span" face="sans-serif"><br></font></div><div><font class="Apple-style-span" face="sans-serif">An additional requirement is servers and clients can handle at least TLS 1.1 (SSL 3.0 will not suffice, and SSL 2.0 support should be deactivated anyway), which is the case with all modern web browsers and Apache with mod_ssl which fulfill above criteria.</font></div><div><font class="Apple-style-span" face="sans-serif"><br></font></div><div><font class="Apple-style-span" face="sans-serif">Is it possible that you are using CentOS 5 or a similarly old distro (even Debian Squeeze supports SNI)? Could it be that TLS support was disabled in the Apache configuration? Anyway, mod_gnutls should not be required to make SNI work with Apache.</font></div><div><font class="Apple-style-span" face="sans-serif"><br></font></div><div><font class="Apple-style-span" face="sans-serif">About </font>Rigzen Oliver Latshang's error:</div><div><font class="Apple-style-span" face="sans-serif"><br></font></div><div><font class="Apple-style-span" face="sans-serif"><blockquote type="cite" style="font-family: Helvetica; "><div><blockquote type="cite">SSL23_GET_SERVER_HELLO:unknown protocol (error code: 35)</blockquote></div></blockquote><br></font></div><div><font class="Apple-style-span" face="sans-serif">This usually means that the server is not speaking SSL/TLS on port 443 (</font><span class="Apple-style-span" style="font-family: sans-serif; ">usually because it responds with plain HTTP</span><span class="Apple-style-span" style="font-family: sans-serif; ">). Did you ask Apache to listen to port 443 without enabling mod_ssl? The most basic check here is to check with openssl s_client -connect mycloud.com:443. Add -servername <a href="http://mycloud.com">mycloud.com</a> to specify the vhost in an SNI setup.</span></div><div><font class="Apple-style-span" face="sans-serif"><br></font></div><div><font class="Apple-style-span" face="sans-serif">Cheers,</font></div><div><font class="Apple-style-span" face="sans-serif"> Daniel</font></div><div><font class="Apple-style-span" face="sans-serif"><br></font></div><div><br><div><div>Am 23.03.2013 um 20:25 schrieb Pierre Malard:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi,<br><br>I have the solution... but it's not really a good one for us.<br><br>Explanation:<br>On our sites we have a lot of virtual hosts (Apache2) and their is a problem to have multiples SSL certificate to them. So, the solution we had choose is to replace mod_ssl by mod_gnutls which can refer to differents certificates on one Apache server.<br><br>OC can't (don't know how?) use GnuTLS system. So, I declare mod_ssl specialy for OC on our server. But, for the others apache virtual hosts, GnuTLS were conserved. This was the mistake!<br><br>So, I create a new Apache server specialy to OC with just our OC servers in differents virtual hosts (4.5.7 for production one and 5.0 to test). As these servers are on the same domain name, I can use a wilcard SSL certifictate (*.MyDomain) and no GnuTLS reference.<br><br>As is, OC5 accept WebDAV and I don't have any error.<br><br>I don't know if it's really a bug but I have open an issue on OC GitHUB service.<br><br>Cheers<br><br>Le 21 mars 2013 à 08:53, Rigzen Oliver Latshang <<a href="mailto:rigzen.latshang@math.ethz.ch">rigzen.latshang@math.ethz.ch</a>> a écrit :<br><blockquote type="cite">it looks like Sabre DAV the "PHP Webdav Server" is having issues<br></blockquote><blockquote type="cite">connecting to your domain with ssl:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">[CURL] Error while making request: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol (error code: 35)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">You may have to check that your webserver can access your domain with<br></blockquote><blockquote type="cite">"php curl". Maybe your webserver can't resolve your domain locally.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 21.03.2013 08:37, Thomas Müller wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">please open a bug report on github:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://github.com/owncloud/core">http://github.com/owncloud/core</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Am Donnerstag, dem 21.03.2013 um 1:01 schrieb Pierre Malard:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I have just update our owncloud server which run on Debian. So, now, we have and OC 5.0 server.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">After the hard way to modify "config/config.php" file and suppress "maintenance" line, everything seems to work but I have an error about my webdav configuration on admin tag:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre"> </span>Setup Warning<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre"> </span>Your web server is not yet properly setup to allow files synchronization <br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre"> </span>because the WebDAV interface seems to be broken.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre"> </span>Please double check the installation guides.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I'm follow the link "installationn guide". The only indication about Debian installation/update is:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre"> </span>"Go to the linux package sources page and execute the steps as described <br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre"> </span>there for your distribution."<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">and the fabulous "steps" are:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">"echo 'deb <a href="http://download.opensuse.org/repositories/isv:ownCloud:community/Debian_6.0/">http://download.opensuse.org/repositories/isv:ownCloud:community/Debian_6.0/</a> /' >> /etc/apt/sources.list.d/owncloud.list <br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">apt-get update<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">apt-get install owncloud"<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">If I read the general informations about "manual installation", I read:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">"You don’t need any WebDAV support of your webserver (i.e. apache’s mod_webdav) to access your ownCloud data via WebDAV, ownCloud has a WebDAV server built in. In fact, you should make sure that any built-in WebDAV module of your webserver is disabled (at least for the ownCloud directory), as it can interfere with ownCloud’s built-in WebDAV support."<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">It was the same thing with OC 4 and I never had this message...<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">In my "data/owncloud.log", I have this:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">"{"app":"core","message":"isWebDAVWorking: NO - Reason: exception 'Sabre_DAV_Exception' with message '[CURL] Error while making request: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol (error code: 35)' in \/var\/www\/owncloud\/3rdparty\/Sabre\/DAV\/Client.php:410\nStack trace:\n#0 \/var\/www\/owncloud\/3rdparty\/Sabre\/DAV\/Client.php(179): Sabre_DAV_Client->request('PROPFIND', '', '<?xml version=\"...', Array)\n#1 \/var\/www\/owncloud\/lib\/util.php(590): Sabre_DAV_Client->propFind('', Array)\n#2 \/var\/www\/owncloud\/settings\/admin.php(34): OC_Util::isWebDAVWorking()\n#3 \/var\/www\/owncloud\/lib\/route.php(113) : runtime-created function(1): require_once('\/var\/www\/ownclo...')\n#4 [internal function]: __lambda_func(Array)\n#5 \/var\/www\/owncloud\/lib\/router.php(127): call_user_func('?lambda_8', Array)\n#6 \/var\/www\/owncloud\/lib\/base.php(606): OC_Router->match('\/settings\/admin')\n#7 \/var\/www\/owncloud\/index.php(28): OC::handleRequest()\n#8 {main}","level":2,"time":1363823944}"<br></blockquote></blockquote></blockquote><br>----<br>Pierre Malard<br><br> « Si l'on veut croire en l'humanité,<br> il faut voir et comprendre l'inhumanité »<br><br> |\ _,,,---,,_<br> /,`.-'`' -. ;-;;,_<br> |,4- ) )-,_. ,\ ( `'-'<br> '---''(_/--' `-'\_)<br><br>perl -e '$_=q#: 3|\ 5-,3-3,2-: 3/,`.'"'"'`'"'"' 5-. ;-;;,-: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(-/--'"'"' `-'"'"'\-): 22PLM::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'<br>- --> Ce message n’engage que son auteur <-- <br><br>_______________________________________________<br>Owncloud mailing list<br><a href="mailto:Owncloud@kde.org">Owncloud@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/owncloud">https://mail.kde.org/mailman/listinfo/owncloud</a><br></div></blockquote></div><br><div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>--</div><div><a href="http://www.owncloud.com">www.owncloud.com</a> - Your Data, Your Cloud, Your Way!</div><div><br>ownCloud GmbH, GF: Markus Rex, Holger Dyroff<br>Schloßäckerstrasse 26a, 90443 Nürnberg, HRB 28050 (AG Nürnberg)</div></div></div>
</div>
<br></div></body></html>