Page tree

Welcome to FreeSoftwareServers Confluence Wiki

Skip to end of metadata
Go to start of metadata

There are mixed guides all over the internet and not one of them worked for me. I had to mix and match and even make some of my own code to get the WebUI to AutoConnect.

After having more and more issues with Deluged, I now prefer Transmission, only problem is the Windows UI is not officially supported, yet. (There is a UI tho on SourceForge)

To Install:

sudo adduser --disabled-password --system --home /var/lib/deluge --group deluge
sudo adduser $USER deluge
echo "" | sudo add-apt-repository ppa:deluge-team/ppa
sudo apt-get update
sudo apt-get install -y deluged deluge-webui
cat << 'EOL'>/etc/init/deluged.conf
# deluged - Deluge daemon
#
# The daemon component of Deluge BitTorrent client. Deluge UI clients
# connect to this daemon via DelugeRPC protocol.

description "Deluge daemon"
author "Deluge Team"
start on filesystem and static-network-up
stop on runlevel [016]

respawn
respawn limit 5 30

env uid=deluge
env gid=deluge
env umask=000

exec start-stop-daemon -S -c $uid:$gid -k $umask -x /usr/bin/deluged -- -d 
EOL
chmod +x /etc/init.d/deluged.conf
cat << 'EOL' >/etc/init/deluge-web.conf
# deluge-web - Deluge Web UI
#
# The Web UI component of Deluge BitTorrent client, connects to deluged and
# provides a web application interface for users. Default url: http://localhost:8112

description "Deluge Web UI"
author "Deluge Team"

start on started deluged
stop on stopping deluged

respawn
respawn limit 5 30

env uid=deluge
env gid=deluge
env umask=000

exec start-stop-daemon -S -c $uid:$gid -k $umask -x /usr/bin/deluge-web 
EOL
chmod +x /etc/init.d/deluge-web.conf
sudo start deluged && sudo stop deluged && sudo service deluged restart

 

You just created a User called deluge with a home directory of /var/lib/deluge and disabled a password for the user. Then you added yourself to the group deluge. Then installed PPA for Deluge and Deluge Daemon/Webui. Then created 2 Init scripts. One for the Daemon and one for the WebUI. Then Started,stopped and restarted DelugeD and WebUI.

Note:

sudo service deluged {start/stop/restart} will automatically effect deluge WebUI. But you can check via sudo service deluge-web status.

 

Now Access via HTTP://PrvateIP:8112 >> Default PWD is deluge>> Change PWD

Go to Options>> Daemon>> Allow Remote Connections

That should be it for the basics, but here comes the hard part. You will want the WebUI to auto-connect to the Daemon. The WebUI is what the program pushes the magnet link to, which then pushes that to the Daemon. If it doesn't auto-connect, you will need to manually connect after each reboot. And trust me you will forget and be outside your LAN and unable to push torrents from mobile clients like Android/IOS/Windows/MacOS.

There are 2 ways to do this. The First is the "reccomended way" but I have had serious issues if not done properly the first time, and even still then. Anyway it is worth a try!

SHUT DOWN DELUGED! (Change UNAME & PWD to same one changed from WebUI above step.)

sudo su 
service deluged stop && nano /var/lib/deluge/.config/deluge/web.conf && echo "USERNAME:PASSWORD:10" >> /var/lib/deluge/.config/deluge/auth && service deluged restart 

/var/lib/deluge/.config/deluge/web.conf

"default_daemon": "127.0.0.1:58846",

Reboot Server and Check by going to HTTP://PrvateIP:8112 >> It should be connected to Local Daemon, if not, proceed to my custom solution!

First lets see if this will work, the idea is that by restarting DelugeD the WebUI will now AutoConnect. If this works, you simply have the server restart DelugeD after Boot completes.

sudo service deluged restart 

HTTP://PrvateIP:8112 >> It should be connected to Local Daemon (If not, then this is useless)

If it is, then we are going to USE RC.Local to run the command sudo service deluged restart after boot.

  • No labels