Request Failed. POST /api/release: Failed to connect to qBittorrent

Help & Support
1

Sonarr version: 2.0.0.5163
Mono version: 4.7.0
OS: OS X 10.11.6 Darwin 15.6.0
Log: https://pastebin.com/4vf97200

Encountered this issue after updating to 2.0.0.5153, along with this issue, which has since been resolved.

2.0.0.5163 resolved the aforementioned issue, but I still cannot connect to qbittorent.
Test connection works, qbittorent WebUI is working, but when I attempt to download something, I get an error that says cannot connect to qBittorent

Every time I try to download, I get this error (pastebin of log above)
https://i.imgur.com/R8FYHZT.png

Any suggestions or help much appreciated!!! Thank you!!!

2

Trace logs may show the response (not sure offhand), if not perhaps Qbit’s logs have more information, since we need to understand why it’s failing with a 400 response (generally means it didn’t like something in the request).

3

Thanks for the suggestion! I enabled trace logging and ran through the process, but I didn’t get any additional information from Sonarr. Would that Error 400 be the response from the QB API?

qBittorrent doesn’t seem to generate logs at that level. I don’t see anything generating when I attempt the connection.

4

A 400 response tells the caller that the request was rejected because something was wrong with the request and usually what was wrong. What do your QBit settings in Sonarr look like?

5

Here are the settings in Sonarr, with a successful test connection:
https://i.imgur.com/q1MEaie.png

I’ve attempted deleting and re-adding this source. None of the settings have been changed recently, only the .5153 and subsequent .5163 updates.

6

Which version of qbit are you using?

7

qBittorent v 3.3.0

8

A post was split to a new topic: Qbit 4.0.4 Can’t add torrent

9

Qbit has had a history of making breaking changes and while we do our best to remain backwards compatible it’s likely something Sonarr is sending is not supported by 3.3.0 and instead of ignoring it, it rejects the request.

Upgrading qbit would be the best next step.

10

That was it! Upgrading qBittorent from 3.3.0 to 4.0.4 successfully resolved the issue, and it is now working as expected.

Thank you so much for your help on this! You guys are the greatest.

1 Like
11

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.