-
Notifications
You must be signed in to change notification settings - Fork 274
Setting up uTorrent Web UI with DuckieTV
This is a step by step guide on how to set up µTorrent Classic via its WebUI with DuckieTV. This guide is based on my installation on a Windows 7 platform of µTorrent Classic, but this guide should hold true across the other platforms (more or less).
µTorrent Classic 2.2.1 or newer. Get the latest version at the official download site here
Note: this is not WEB µTorrent, which is a different product.
DuckieTV 1.1.4 or newer. Get the latest version at the official download site here
Dtv Nightly. Get the latest version at the official download site here
Support for uTorrent Classic can be found at http://help.utorrent.com/
Once you have installed and started µTorrent Classic, we can
-
Click on the Options menu entry and select Preferences
-
Now click on Advanced to expand the list
-
And then click on Web UI to bring up its configuration panel
-
Click on the Enable Web UI check box and then enter a Username and Password
-
Next, enable the Alternative Listening Port by clicking on the check box, and set the port to 8080 if it is not this already.
-
Now click on the Apply and OK buttons to save your settings.
Start up DuckieTV and
-
Start up DuckieTV and click on the Settings Icon
-
And then click on the Torrent button
-
Now click on the µTorrent Web UI button
-
Next, click on the µTorrent Web UI Integration button
-
Enter the same Username and Password that you used on the µTorrent Web UI settings page
-
if you are running µTorrent 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 µTorrent Web UI Icon on the left hand side and a Status: Connected to µTorrent WebUI 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.
- Did you get the username or password on the DuckieTV µTorrent Web UI 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 other fields), so when you try again, you will need to enter both the new username and password (and any other fields you previously changed) again.
- If you are running µTorrent on the same computer as DuckieTV and you are using
localhost
as the IP address, then try switching to127.0.0.1
instead. Some systems cannot resolve localhost, and 127.0.0.1 is the same end address. - If you previously tried a connection and failed, and subsequently followed this guide and are still not connected, first try clicking on the DuckieTV µTorrent Web UI icon on the left. This will retry the connection attempt.
- If the connection is still not established, try closing both µTorrent and DuckieTV. To shut down µTorrent properly, do not use the Window Close X button, (circled in yellow in the image below), but use the File menu and select Exit. After starting them up again, click on the DuckieTV µTorrent Web UI icon to try establishing a connection.
- Still not connected? See if you can connect and login to the µTorrent WEBUI directly via your Browser. for example,
at the address box paste
http://localhost:8080\gui
and press enter. You should get the Login challenge followed by the µTorrent torrent page if successful. If this does not work then you know the problem is with your µTorrent setup or with some system setup, such as firewall or antivirus or network or something. - 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?
- 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