I also had this problem and I managed to find a solution so I thought I would share my findings.
Note: I am using a third party certificate, so my certificate is not self-signed. I suspect the same principals apply to those using a self-signed certificate but I have not tested it.
In my case, I installed my certificate as was able to correctly access https://cloud.mydomain.com
in my browser without any issues from either of my laptops (Win8/OSX Lion) However configuring the client on either of these would result in a "SSL handshake failed" error. After much messing around it seems that the client is expecting a TLS connection to the OwnCloud server and having the certificate installed does necessarily ensure TLS as your server name should match your certificate CN (common name).
Firstly, ensure that your certificate CN is correct. If for example you access your OwnCloud using https://cloud.yourdomain.com
then your certificate CN should be cloud.yourdomain.com. If you access your OwnCloud using https://yourdomain.com/owncloud
then your certificate CN should be yourdomain.com
If your certificate provider requires the installation of their intermediary and root certificates, make sure they are included in your apache configuration found in /etc/apache2/sites-enabled/default-ssl (in Ubuntu, probably httpd.conf in other distys). For example:
Code: Select all
Next, you need to ensure that you have the correct server name set in your apache configuration. In your /etc/apache2/sites-enabled/default-ssl, make sure that the 'ServerName' setting matches your certificate CN. For example:
Code: Select all
Options Indexes FollowSymLinks MultiViews
allow from all
I hope this helps someone.