Deluged never opens port 58846 for Client connection

General support for problems installing or using Deluge
Post Reply
jgdempsey
New User
New User
Posts: 2
Joined: Sun Jul 24, 2016 3:34 pm

Deluged never opens port 58846 for Client connection

Post by jgdempsey »

Recently deluged has stopped opening port 58846 for client connections, and I'm looking for assistance in troubleshooting the issue.
I am running it on Voyage Linux (Debian Jessie) and the daemon seems to start ok, but if I try to connect with the GTK client from a windows or Mac machine, the Connection manager always shows the daemon in red.
The version is 1.3.10-3 (latest for Jessie)
I have also tried connecting to it locally with deluge-console and I get

Code: Select all

Failed to connect to 127.0.0.1:58846 with reason: Connection refused
netstat -an | grep deluge returns nothing.

I have set log level to debug and the only error's I see are the following

Code: Select all

[DEBUG   ] 14:06:30 config:304 Registering function for enc_in_policy key..
[DEBUG   ] 14:06:30 preferencesmanager:347 encryption value enc_in_policy set to -1..
[ERROR   ] 14:06:30 component:118 [Failure instance: Traceback: <type 'exceptions.KeyError'>: -1
/usr/lib/python2.7/dist-packages/deluge/main.py:230:start_daemon
/usr/lib/python2.7/dist-packages/deluge/core/daemon.py:169:__init__
/usr/lib/python2.7/dist-packages/deluge/component.py:296:start
/usr/lib/python2.7/dist-packages/deluge/component.py:124:_component_start
--- <exception caught here> ---
/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:139:maybeDeferred
/usr/lib/python2.7/dist-packages/deluge/core/preferencesmanager.py:177:start
/usr/lib/python2.7/dist-packages/deluge/config.py:312:register_set_function
/usr/lib/python2.7/dist-packages/deluge/core/preferencesmanager.py:353:_on_set_encryption
]
[DEBUG   ] 14:06:30 rpcserver:396 Registering method: scheduler.get_config
[DEBUG   ] 14:06:30 rpcserver:396 Registering method: scheduler.get_state
I've tried changing the enc_in_policy to 1 and 2 without any change.

This error shows up twice in the log.

Any suggestions would be appreciated..

Thanks
Post Reply