bogenpirat
qBittorrent on subdirectory (reverse proxied)
I have just redone my setup and made various services accessible via HTTPS (proxied by IIS) and found RTA does not have the option for entering a subdirectory when set to qBittorrent. In RTA on uiTorrent it calls the option "Relative path" but as the QB web UI is much nicer I don't want to go back to utorrent.
I access the webui using the URL in the format of https://x.y.com/qbweb/ (real domain removed for obvious reasons) and it works fine. Current workaround is to use the direct IP/port for the server but that is internal only - I would like it to work externally as well hence the reverse proxying.
After looking at the source code I have found a workaround - putting "443/qbweb" in the port box. Seems to work.
Be nice to have an option for subdirectory but not vital while the workaround is functional.
I have the same problem, or sort of,
When RTA is active I can't even access https://qbittorrent.example.com/ but as soon as I disable it, it works again.
I tried your workaround and that made it work again!I can now access the url again, how ever, RTA doesn't work it throws an error!
HTTP ERROR 401
I proxy with Traefik!
After looking at the source code I have found a workaround - putting "443/qbweb" in the port box. Seems to work.
Be nice to have an option for subdirectory but not vital while the workaround is functional.
I am using an nginx proxy and essentially same setup as you. Unfortunately, the work around does not work for me. Get an error which says Failure could not contact qbt Error: And it doesn't actually print any error message.
I use Nginx these days as well. I changed to a different addon when qBittorrent got updated and it stopped working.
https://chrome.google.com/webstore/detail/xirvik-torrent-to-seedbox/gljdkkichjgocpdmiaachhlfccddcjgb
It just asks for server URL without separating port - I just enter https://my.domain/qbweb