Skip to content

Setting up Ktorrent with DuckieTV

garfield69 edited this page Nov 4, 2022 · 25 revisions

This is a step by step guide on how to set up Ktorrent with DuckieTV. This guide is based on my installation on a Ubuntu 16.10 platform, but this guide should hold true across the other platforms (more or less).

Pre requisites:

Ktorrent 4.3.1 or newer. Install Ktorrent by using sudo apt-get install ktorrent from a linux terminal.


ALERT

Ktorrent 5 does not include a webui plugin. So Ktorrent 4.3.1 is currently the only version to connect with DuckieTV. https://ubuntu.pkgs.org/16.04/ubuntu-universe-i386/ktorrent_4.3.1-4_i386.deb.html for Ubuntu 16.04


DuckieTV 1.1.5 or newer. Get the latest version at the official download site here
Dtv Nightly. Get the latest version at the official download site here

Documents

The Ktorrent handbook can be found at https://en.wikibooks.org/wiki/Ktorrent


Once you have installed and started Ktorrent, we can

enable the Web and Magnet plugins.

  • Click on the Plugins tool bar and enable all the plugins you wish to use. At the very minimum, make sure you enable the Web Interface and Magnet Generator plugins by clicking on their check boxes.

  • You may wish to enable the following on the Ktorrent toolbar, if they are not already visible: About Ktorrent so you can check which version you are using, and Configure Ktorrent so you access the configure settings.

    • Right click on a blank spot on the toolbar and select the Configure toolbars... option
    • click on About Ktorrent in the Available Actions window and then click on the > button to shift the entry to the Current Actions window.
    • repeat for the Configure Ktorrent entry.
    • click on the Apply and OK buttons.
  • Next, click on the Configure tool bar and then click on the Web Interface icon to view its settings

  • Now tick the Login required check box, and enter a Username and Password. Then click on the Apply and OK buttons.

Start up DuckieTV and

configure the DuckieTV Ktorrent Integration.

  • Start up DuckieTV and click on the Settings Icon

  • And then click on the Torrent button

  • Now click on the Ktorrent button

  • Next, click on the Ktorrent Integration button

  • Enter the same Username and Password that you used on the Ktorrent Web Interface settings page

  • if you are running Ktorrent on a different computer than DuckieTV then enter its ip address in the Address box

  • And press the Test and Save button

  • you are connected!
    If all went well, you should see a green dot next to the Ktorrent Icon on the left hand side and a Status: Connected to Ktorrent 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.

Problems?

  • Did you get the username or password on the DuckieTV Ktorrent Integration panel wrong? When you press the Test and Save button, and the test fails, DuckieTV does not save the username and password (or any of the other fields), so when you try again, you will need to enter both the new username and password (as well as any other field you may have changed previously) 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 Ktorrent icon on the left. This will retry the connection attempt.
  • If the connection is still not established, try closing both Ktorrent and DuckieTV and starting them up again. Then click on the DuckieTV Ktorrent icon to try establishing a connection.
  • 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? If you are using DuckieTV as a Chrome Browser Extension, or as a Nightly Standalone, then you can 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. and feel free to raise a ticket on GitHub here, or submit a post on Reddit here
Clone this wiki locally