Allow for qBittorrent WebGUI to run in HTTPS #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The default setup was to query the qBittorrent WebGUI over HTTP.
This is fine normally, but in order to register qBittorrent WebGUI to handle magnet links, qBittorrent needs to run in HTTPS.
This causes problems with qbittorrent-natmap. Because qBittorrent WebGUI only operates out of one port, the HTTP/HTTPS setting in qBittorrent WebGUI means that it will only respond to one or another. If we set qBittorrent WebGUI to use HTTPS, qbittorrent-natmap will be unable to query the qBittorrent WebGUI.
The solution was twofold:
I have tested this container both with and without https, and it is working for me.