Chlorus
Dabbler
- Joined
- Feb 21, 2020
- Messages
- 11
Hi folks, I've been running the qbittorrent plugin since January without issues. I have the web UI configured to serve content over HTTPS, with a certificate from my own internal CA.
Last week, I ran an update on the jail containing it to 11.3-RELEASE-p8 - as part of this, the qbittorrent version was bumped to v4.2.5. Since then, each time I browse to the Web UI over HTTPS, the connection stalls on 'Establishing secure connection' in Chrome. The web login form loads successfully if I force an HTTP connection, but on form submission it immediately redirects back to an HTTPS scheme where the connection errors out again. I've set ''WebUI\HTTPS\Enabled=false'' in qbittorrent.conf but the server still tries to redirect to HTTPS pages, probably because the server is sending a 'Upgrade-Insecure-Requests' CSP header.
How can I fully disable the HTTPS Web UI?
Last week, I ran an update on the jail containing it to 11.3-RELEASE-p8 - as part of this, the qbittorrent version was bumped to v4.2.5. Since then, each time I browse to the Web UI over HTTPS, the connection stalls on 'Establishing secure connection' in Chrome. The web login form loads successfully if I force an HTTP connection, but on form submission it immediately redirects back to an HTTPS scheme where the connection errors out again. I've set ''WebUI\HTTPS\Enabled=false'' in qbittorrent.conf but the server still tries to redirect to HTTPS pages, probably because the server is sending a 'Upgrade-Insecure-Requests' CSP header.
How can I fully disable the HTTPS Web UI?