Skip to main content

Setup Deluge For Raspberry Pi

Fix Deluge Web UI Doesn't Connect Automatically to Daemon​

To fix the issue where the Deluge Web UI doesn't connect automatically to the daemon, follow these steps:

  1. Set 127.0.0.1:58846 as the default daemon in the Deluge Web UI configuration file:
chmod 444 ~/.config/deluge/web.conf
reboot
  1. Enable the Deluge daemon:
sudo nano /etc/default/deluged

Change the line ENABLE_DELUGED=0 to ENABLE_DELUGED=1.

Configure Deluge to Start Automatically at Boot​

Since OSMC uses systemd instead of the older init.d method, we'll use systemd to start Deluge automatically at boot. Follow these steps:

  1. Remove the old init.d configuration:
sudo update-rc.d deluged remove
sudo rm /etc/init.d/deluged
  1. Create a systemd unit file:
sudo nano /etc/systemd/system/deluged.service

Add the following content to the file:

[Unit]
Description = Deluge Bittorent Daemon
After = network-online.target

[Service]
Type = simple
User = debian-deluged
Group = debian-deluged
UMask = 007
ExecStart = /usr/bin/deluged -d
Restart = on-failure
TimeoutStopSec = 300

[Install]
WantedBy = multi-user.target
  1. Reload systemd to pick up the new unit file:
sudo systemctl daemon-reload
  1. Enable the Deluge daemon to start at boot:
sudo systemctl enable deluged.service

Now, the Deluge daemon will start automatically when the Raspberry Pi boots up.