#12
I've got the the same issue. The test in nzb360 passes put nothing else I tried works for qBittorrent. It also works fine if I point nzb360 directly to the container's IP and port but fails with the "Could not connect to Torrent Client" error when going through my nginx reverse proxy with a setup matching the wiki entry at https://github.com/qbittorrent/qBittorr ... for-Web-UI. The qBittorent API works fine through my reverse proxy using Postman though. If I have time this evening I'll look into this further.
#13
Looks like not all the calls nzb360 is making to qBittorrent use the full Primary Connection Address. I have a Primary Connection Address like http://mydomain.com/qbittorrent. nzb360 is correctly calling /qbittorrent/api/v2/auth/login, /qbittorrent/api/v2/transfer/uploadLimit and /qbittorrent/api/v2/downloadLmit using that Primary Connection Address but calls /api/v2/torrents/info without the leading /qbittorrent.
#15
kakalaky wrote:
Tue Dec 10, 2019 10:39 pm
Looks like not all the calls nzb360 is making to qBittorrent use the full Primary Connection Address. I have a Primary Connection Address like http://mydomain.com/qbittorrent. nzb360 is correctly calling /qbittorrent/api/v2/auth/login, /qbittorrent/api/v2/transfer/uploadLimit and /qbittorrent/api/v2/downloadLmit using that Primary Connection Address but calls /api/v2/torrents/info without the leading /qbittorrent.
Yep can confirm. I have the same exact setup and same exact issue.
I used HttpCanary to check the HTTP requests and

Code: Select all

/api/v2/torrents/info
is made without

Code: Select all

/qbittorrent
.
It should be

Code: Select all

domain.com/qbittorrent/api/v2/torrents/info
#16
Interesting. That is very odd that it isn't respecting that subdomain only for one call. Amazing debugging info though, I will resolve this over the weekend. I appreciate the info!
cron