Deluge client disconnected SSL routines SSL3_GET_RECORD

[caffeine]

I'm running deluged on my Linux box (Tasty Kubuntu) 192.168.1.2 using this command line:

/usr/bin/deluged --port 58846 --ui-interface=192.168.1.2 --logfile=/var/log/deluged/logfile --loglevel=info \
--interface=192.168.1.2 --pidfile=/var/run/deluge.pid

and trying to access it from Firefox on my Win7 box (192.168.1.6) via:

http://192.168.1.2:58846

Firefox complains "The connection was reset". When I look at the logs on my Kubuntu box, it says:

Code: Select all

[INFO    ] 17:02:53 daemon:124 Deluge daemon 1.3.6
[INFO    ] 17:02:53 core:80 Starting libtorrent 0.16.13.0 session..
[INFO    ] 17:02:53 rpcserver:366 Starting DelugeRPC server 192.168.1.2:58846
[WARNING ] 17:02:53 torrentmanager:639 Unable to update state file to a compatible version: list index out of range
[WARNING ] 17:02:53 torrentmanager:742 Unable to load fastresume file: [Errno 2] No such file or directory: '/root/.config/deluge/state/torrents.fastresume'
[INFO    ] 17:03:30 rpcserver:203 Deluge Client connection made from: 192.168.1.6:62477
[INFO    ] 17:03:30 rpcserver:223 Deluge client disconnected: [('SSL routines', 'SSL3_GET_RECORD', 'wrong version number')]
[INFO    ] 17:03:33 rpcserver:203 Deluge Client connection made from: 192.168.1.6:62478
[INFO    ] 17:03:33 rpcserver:223 Deluge client disconnected: [('SSL routines', 'SSL3_GET_RECORD', 'wrong version number')]

I'm currently running deluged as root, since it's a daemon that needs to bind to a port (is this the proper way of doing it?)

I looked for .config files, but according to

dpkg -L deluge deluged deluge-web-ui deluge-web

I didn't see anything configish. Help?

Thanks!

[Cas]

First update deluge to latest version

[caffeine]

Done. Built packages from source based on Ubuntu utopic.

$ dpkg -l "*deluge*"

ii deluge 1.3.10-1 bittorrent client written in Python/PyGTK
ii deluge-common 1.3.10-1 bittorrent client written in Python/PyGTK (common files)
ii deluge-console 1.3.10-1 bittorrent client written in Python/PyGTK (console ui)
ii deluge-gtk 1.3.10-1 bittorrent client written in Python/PyGTK (GTK+ ui)
ii deluge-torrent 1.3.10-1 bittorrent client (gtk ui transitional package)
ii deluge-web 1.3.10-1 bittorrent client written in Python/PyGTK (web ui)
ii deluge-webui 1.3.10-1 bittorrent client (web ui transitional package)
ii deluged 1.3.10-1 bittorrent client written in Python/PyGTK (daemon)

I'm trying to run the daemon, headless, on Linux (satan 192.168.1.2), and access it via Firefox from Win7 (lucifer 192.168.1.3).

• From Win7, when I point Firefox to 192.168.1.2:8112, I get "Unable to connect".
• On the Linux side, according to "netstat -lnp | grep 8112", port 8112 is unbound. The only mention of this port in the deluge logs is:
  rpcserver:366 Starting DelugeRPC server 192.168.1.2:8112
• I start deluged using this command line from /root/.config/deluge_run.sh:

  /usr/bin/deluged --ui-interface=192.168.1.2 \
  --logfile=/var/log/deluged/deluged.log --loglevel=debug \
  --interface=192.168.1.2 --pidfile=/var/run/deluge.pid

  The config directory (core.config, auth, etc) were verified to be taken from /root/.config. I know this is very non-standard, but I've been tinkering with this for over 6 hours, and I've tried things only desperate people would try.
• Log at debug has messages I don't understand.
  [DEBUG] alertmanager:123 portmap_log_alert: UPnP: broadcasting search for rootdevice
  [DEBUG] alertmanager:123 portmap_log_alert: UPnP: HTTP method m-search from 192.168.1.2:41840
  [DEBUG] alertmanager:123 portmap_log_alert: UPnP: HTTP method m-search from 192.168.1.2:1900
  [DEBUG] alertmanager:123 portmap_log_alert: UPnP: HTTP method m-search from 192.168.1.3:64384
  [DEBUG] alertmanager:123 portmap_log_alert: NAT-PMP: ==> port map [ mapping: 1 action: add proto: tcp local: 4433 external: 4433 ttl: 3600 ]
  [INFO ] 21:25:57 rpcserver:203 Deluge Client connection made from: 192.168.1.3:52498
  [INFO ] 21:25:57 rpcserver:223 Deluge client disconnected: [('SSL routines', 'SSL3_GET_RECORD', 'wrong version number')]
  
• Using tcpdump -i eth0 tcp port 8112 on Linux, I verified that Win7 is making the connection to port 8112, but it looks like they never get past the syn/ack handshake.
  21:37:49.182983 IP lucifer.52661 > satan.8112: Flags , seq 942412677, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
  21:37:49.183001 IP satan.8112 > lucifer.52661: Flags [S.], seq 3931292050, ack 942412678, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
  21:37:49.183138 IP lucifer.52661 > satan.8112: Flags [.], ack 1, win 16425, length 0
  21:37:49.183585 IP lucifer.52661 > satan.8112: Flags [P.], seq 1:2559, ack 1, win 16425, length 2558
  21:37:49.183605 IP satan.8112 > lucifer.52661: Flags [.], ack 2559, win 269, length 0
  21:37:49.184350 IP satan.8112 > lucifer.52661: Flags [F.], seq 1, ack 2559, win 269, length 0
  21:37:49.184472 IP lucifer.52661 > satan.8112: Flags [.], ack 2, win 16425, length 0
  21:37:49.184737 IP lucifer.52661 > satan.8112: Flags [F.], seq 2559, ack 2, win 16425, length 0
  21:37:49.184758 IP satan.8112 > lucifer.52661: Flags [.], ack 2560, win 269, length 0
• The relevant items in core.config that I've set are:

  daemon_port: 8112
  allow_remote: true
  listen_ports: 60000, 60000

I'm out of ideas, and I don't know how to diagnose this further. Any assistance would be really appreciated!

I don't need to run deluge-web, right? That's a client and unrelated to what I'm trying to do; is that correct?

Thanks,
Pete

[Cas]

I just realised you are not accessing the daemon correctly. You cannot simply point your browser at the daemon port that will not work as it's not a web server.

The thinclient guide should explain everything, see near the end for web access: http://dev.deluge-torrent.org/wiki/UserGuide/ThinClient