Setting up qBitTorrent52plus with DuckieTV - SchizoDuckie/DuckieTV GitHub Wiki

This is a step by step guide on how to set up qBitTorrent 5.2+ with DuckieTV.
If you are using a version of qBitTorrent prior to 5.2, then read https://github.com/SchizoDuckie/DuckieTV/wiki/Setting-up-qBitTorrent-with-DuckieTV.
This guide is based on my installation on a Windows 11 platform, but this guide should hold true across the other platforms (more or less).

Pre requisites:

qBitTorrent 5.2 or newer. Get the latest version at the official download site here

Dtv nightly-202605121341 or newer. Get the latest version at the official download site here

Documents

The wiki for qBt can be found at https://github.com/qbittorrent/qBittorrent/wiki

Once you have installed and started qBitTorrent, we can

access the Web UI configuration page.

  • Click on the Tools menu, and select the Options entry

  • Click on the Web UI Icon

  • Enable the Web UI Interface by clicking the check-box, copy the APIkey and click the Apply and OK buttons

Start up DuckieTV and

configure the DuckieTV qBitTorrent 5.2+ Integration.

  • Start up DuckieTV and click on the Settings Icon

  • Click on the Torrent button

  • Click on the qBitTorrent 5.2+ button

  • Click on the qBitTorrent 5.2+ integration button

  • Paste the APIkey that you found/generated on qBitTorrent

  • Click on the Test and Save button

  • You are connected!

If all went well, you should see a green dot next to the DuckieTV qBitTorrent Icon on the left hand side
and a Status: Connected to qBitTorrent 5.2+ API on the right hand side.
Please note that being connected is not a guarantee that everything is operational. Some clients have further validation that only occurs during submissions of commands and requests for results.

Gotcha

DuckieTV polls qBitTorrent every 3 seconds to fetch the download status. If you are using qBt Seeding Limit option to remove the torrent, then do not set the trigger too low, or you may end up removing the torrent from qBt before Dtv has had a chance to see the download reach 100%. If Dtv thinks the torrent has vanished it will flag the download as lost and not mark the episode as downloaded.

Problems?

  • Did you use an expired APIKey on the DuckieTV qBitTorrent 5.2+ Integration panel?
    When you press the Test and Save button, and the test fails, DuckieTV does not save the APIkey (or any of the other fields), so when you try again, you will need to enter/paste everything again.

  • If you previously tried a connection and failed, and subsequently followed this guide and are still not connected, first try clicking on the DuckieTV qBitTorrent 5.2+ icon on the left. This will retry the connection attempt.

  • If the connection is still not established, try closing both qBitTorrent 5.2+ and DuckieTV and starting them up again. Then wait and look at the DuckieTV qBitTorrent 5.2+ icon. The Icon's Red dot should change to Orange and then Green when the connection is completed.

  • Could your local firewall or security app or router be blocking Dtv from accessing the inbound/outbound qBt port? Do you need to add a permission rule?

  • Still not connected? See if you can connect and login to the qBitTorrent 5.2+ WEBUI directly via your Browser. for example, at the address box paste http://localhost:8080 and press enter.

    You should get the Login challenge followed by the qBitTorrent 5.2+ torrent page if successful.
    If this does not work then you know the problem is with your qBitTorrent 5.2+ setup or with some system setup, such as firewall or antivirus or network or something.

  • Check the DuckieTV console log for errors, by pressing the F12 key (on Windows and Linux) or Cmd-Alt-I (OSX) to open the development tools page, and clicking on the console tab to view the log.

  • if the Dtv log shows that qBt is returning 403, then this means that you have exceeded the qBt failed attempts limit, and qBt is now banning access for a period of time. The settings for the limit on the number of attempts and how long the ban will last are in the qBt WEBUI settings. (the default limit is 5, with a ban period of 3600 seconds). And if you look at the qBt log you should find the ban record with the reason for the ban.

  • if you cannot resolve then feel free to raise a ticket on GitHub here, or submit a post on Reddit here