Thin Client, auto start issues. Raspbian (jessie)

[Nablar]

I have been following three guides to install Deluge on my Raspberry Pi.
My goal is to use the thin client from my windows 10 computer.

First i followed this guide to install Deluge
http://dev.deluge-torrent.org/wiki/Inst ... ian/Jessie

Then i followed this to autostart Deluge
http://dev.deluge-torrent.org/wiki/User ... ce/systemd

Then this to set up the thin client
http://dev.deluge-torrent.org/wiki/UserGuide/ThinClient

My problem is that i cant access Deluge form the Windows 10 client after i reboot the Rasberry Pi.

If i type sudo systemctl status deluged -l after i reboot i get this:

Code: Select all

pi@raspberrypi:~ $ sudo systemctl status deluged -l
● deluged.service - Deluge Bittorrent Client Daemon
   Loaded: loaded (/etc/systemd/system/deluged.service; enabled)
   Active: active (running) since Fri 2016-08-05 17:46:41 UTC; 1h 25min ago
 Main PID: 528 (deluged)
   CGroup: /system.slice/deluged.service
           └─528 /usr/bin/python /usr/bin/deluged -d

Aug 05 17:46:41 raspberrypi systemd[1]: Started Deluge Bittorrent Client Daemon.

so to it seems to be running, but my this client cannot connect (red lamp for server down on windows 10 client)

If i however do this:

Code: Select all

pi@raspberrypi:~ $ sudo killall deluged
pi@raspberrypi:~ $ deluged

The Windows 10 client suddenly gets a good to go, and works as i want it to.

Any ideas?
I'm a beginner with Debian so i don't know where to start looking.

I'm running this on Raspbian GNU/Linux 8 (jessie).

[Cas]

Likely you are not modifying the correct deluge config for the deluged service.

[Nablar]

Thank you for you reply cas

I did the following

Code: Select all

sudo nano /etc/systemd/system/deluged.service

Than copied and pased in this from the guide

Code: Select all

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

[Service]
Type=simple
User=deluge
Group=deluge
UMask=007

ExecStart=/usr/bin/deluged -d

Restart=on-failure

# Configures the time to wait before service is stopped forcefully.
TimeoutStopSec=300

[Install]
WantedBy=multi-user.target

i have done no modifications.

[Cas]

I mean the actual location of the deluge config:

When running Deluge as a service the config directory is relative to the user specified in the service configuration.

[Nablar]

I found my fault now, but for some reason i had to go into /etc/default/deluged an set ENABLE_DELUGED=1