qBitTorrent - Can Not Connect if SSL Enabled for WebUI

[s0urc3ray]

I've just switched to SSL on qBitTorrent by importing a valid certificate into qBT, Web UI works perfectly in Browser and I updated the settings in DuckieTV to https:// however now all I get when attempting to connect is "Connect call failed"

Any idea's why SSL connections fail, I saw no mention that SSL is unsupported in the qBitTorrent DuckieTV Setup Page.

[garfield69]

Since most users run qBt and Dtv on the same PC, no one has tried using https on a localhost before (its a redundant security option in a localhost environment).

Dtv is written in the AngularJS framework, and uses its $http service to make its GET/POST requests to qBt.
In theory there should not need to be any additional changes to the calls required, as for example, Dtv makes API calls to Trakt.tv with https urls without problems, and the calls to qBt are similar.

The most likely reason is that something about the way Dtv makes calls to qBt using http urls is not compatible in the https security space, and AngularJS is downgrading the request to http which in turn gets rejected by qBt as insecure now that you have told it to enforce https protocols.

there is likely some error message that might indicate what the issue is, but you are not going to see it if you are using Dtv Standalone 1.1.5 as the Development Tools pack to view the logs in not included in that build.

But if you are using a Dtv Standalone Nightly https://github.com/DuckieTV/Nightlies/releases then using F12 to open the DevTools page, and clicking on the console tab will get you a view of the logs with any error messages that crop up with the attempt to talk to qBt via https occurs.

for that matter, the qBt logs themselves may also have an info message about why a request was rejected.