Setting up BiglyBT with DuckieTV
This is a step by step guide on how to set-up BiglyBT with DuckieTV.
This guide is based on my installation on the Windows 7 platform, but it should hold true across other platforms (more or less).
BiglyBT 1.0.x.x or newer. Get the latest version at the official download site here
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
At this early stage in BiglyBT's development, it is very much a clone of Vuze until it branches away. So the Vuze user guide at http://wiki.vuze.com/w/User_Guide is a good place for information.
Once you have installed BiglyBT, you next need to
-
Click on the Tools menu and select the Options entry
-
Click on the Arrow next to the Plugins option to expand the list
-
And scroll down to the BiglyBT Web Remote and click on that entry
-
Click the Enable check box to activate the plugin
- HTTPS is currently not supported.
-
then Scroll down and click on the Enable Password check box, and enter a Username and Password
-
Click on the Save button
Start up DuckieTV and
-
Start up DuckieTV and click on the Settings Icon
-
And then click on the Torrent button
-
Now click on the BiglyBT button
-
Next, click on the BiglyBT Integration button
-
Enter the same Username and Password that you used on the BiglyBT Web Remote settings page
-
if you are running BiglyBT on a different computer than DuckieTV then enter its IP address in the Address box
-
Now click on the Test and Save button
-
You are connected!
If all went well, you should see a green dot next the the DuckieTV BiglyBT Icon on the left hand side and a Status: Connected to BiglyBT 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 BiglyBT 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 previously tried a connection and failed, and subsequently followed this guide and are still not connected, first try clicking on the DuckieTV BiglyBT icon on the left. This will retry the connection attempt.
- If the connection is still not established, try closing both BiglyBT and DuckieTV and starting them up again. Then click on the DuckieTV BiglyBT icon to try establishing a connection.
- Still not connected? See if you can connect and login to the BiglyBT WEBUI directly via your Browser. for example,
at the address box paste
http://localhost:9091and press enter.You should get the Login challenge followed by the BiglyBT torrent page if successful.
If this does not work then you know the problem is with your BiglyBT setup or with some system setup, such as firewall or antivirus or network or something.
- In the unlikely situation where you may be running multiple torrent clients on the same PC as DuckieTV, especially either Transmission or Vuze alongside BiglyBT, ensure you allocate unique WEBUI ports on each of the clients.
- Could your local firewall or security app or router be blocking Dtv from accessing the inbound/outbound BiglyBT port? Do you need to add a permission rule?
- Also double check that the BiglyBT WEB Remote setting for Access Control Mode is set to full and not view.
- 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
You should get the Login challenge followed by the BiglyBT torrent page if successful.
If this does not work then you know the problem is with your BiglyBT setup or with some system setup, such as firewall or antivirus or network or something.
and feel free to raise a ticket on GitHub