Client 1.1.1 can't connect with SSL self-signed certificate on 4.5.1 server about client HOT 5 CLOSED

Please try running the client with --logfile

from client.

Hi,

I get the same issue with a commercially signed certificate. The issue occurs with the Windows 1.1.1 client, but not with a Linux client.

Here's the log file... I've changed the server name, if you need it for troubleshooting, please let me know and we can work something out.

11-19 13:39:36:815 Logging into logfile: "D:\OwnCloud.log" with flush false
11-19 13:39:36:816 "################## ownCloud en_CA 1.1.1 "
11-19 13:39:37:770 Trying to read config ini file at "C:/Program Files (x86)/ownCloud/custom.ini"
11-19 13:39:37:771 Trying to read config ini file at "C:/Program Files (x86)/ownCloud/custom.ini"
11-19 13:39:37:771 Trying to read config ini file at "C:/Program Files (x86)/ownCloud/custom.ini"
11-19 13:39:37:771 Trying to read config ini file at "C:/Program Files (x86)/ownCloud/custom.ini"
11-19 13:39:37:787 Trying to read config ini file at "C:/Program Files (x86)/ownCloud/custom.ini"
11-19 13:39:37:825 * Network is offline
11-19 13:39:37:958 Network Location: ""
11-19 13:39:40:898 00 client update check to "https://download.owncloud.com/clientupdater.php"
11-19 13:39:43:962 Client is on latest version!
11-19 13:39:46:451 No configured folders yet, start the Owncloud integration dialog.
11-19 13:39:46:451 Returning configured owncloud url: ""
11-19 13:39:46:500 Current Wizard page changed to 0
11-19 13:39:46:500 Page_install is 5
11-19 13:40:07:582 Current Wizard page changed to 5
11-19 13:40:07:582 Page_install is 5
11-19 13:40:07:582 Connect to url: "https://xxx.org/owncloud"
11-19 13:40:07:583 OO Custom config file in use: "C:\Users\douglask\AppData\Local\ownCloud/owncloud.cfg_111912134007"
11-19 13:40:07:583 *** writing mirall config to "C:\Users\douglask\AppData\Local\ownCloud/owncloud.cfg_111912134007" Skippwd: false
11-19 13:40:07:587 OO Custom config file in use: "C:\Users\douglask\AppData\Local\ownCloud/owncloud.cfg_111912134007"
11-19 13:40:07:587 Get Request to "status.php"
11-19 13:40:07:587 OO Custom config file in use: "C:\Users\douglask\AppData\Local\ownCloud/owncloud.cfg_111912134007"
11-19 13:40:07:588 Returning configured owncloud url: "https://xxx.org/owncloud/"
11-19 13:40:07:588 OO Custom config file in use: "C:\Users\douglask\AppData\Local\ownCloud/owncloud.cfg_111912134007"
11-19 13:40:07:588 Returning configured owncloud url: "https://xxx.org/owncloud/"
11-19 13:40:07:588 Setting up host header: "xxx.org"
11-19 13:40:07:588 OO Custom config file in use: "C:\Users\douglask\AppData\Local\ownCloud/owncloud.cfg_111912134007"
11-19 13:40:07:588 OO Custom config file in use: "C:\Users\douglask\AppData\Local\ownCloud/owncloud.cfg_111912134007"
11-19 13:40:07:589 Setting config handle "111912134007"
11-19 13:40:07:883 ownCloudInfo Network Error: 6
11-19 13:40:07:884 status.php returns: "" 6 Reply: QNetworkReplyImpl(0x2b5c768)
11-19 13:40:07:884 No proper answer on "https://xxx.org/owncloud/status.php"
11-19 13:40:07:941 OO Custom config file in use: "C:\Users\douglask\AppData\Local\ownCloud/owncloud.cfg_111912134007"
11-19 13:40:09:749 Config Changes were accepted!
11-19 13:40:09:749 OO Custom config file in use: "C:\Users\douglask\AppData\Local\ownCloud/owncloud.cfg_111912134007"

from client.

@DouglasK In this case, Windows is not able to create a complete chain of trust to one of its root certificates, but Linux is (which is perfectly possible since they carry different CA bundles). Can you verify that a pedantic browser (i.e. chrome) allows to access your owncloud from the same server without a certificate error/warning?)

from client.

@danimo

The website shows a valid SSL lock in Chrome, Firefox and IE9 . An image of Chrome connected to it is here: http://imgur.com/fUDrf (cert info from Chrome: http://imgur.com/0YwWG ) , and here's the site showin in IE: http://imgur.com/aGNA8

If you need anything further, including a test account on the server, please let me know.

~~Douglas

from client.

It should work with 1.2.0. If not, please reopen.

from client.