Can't connect to daemon on fresh server install [SOLVED]
Posted: Sun Oct 09, 2016 7:59 pm
I've just re-built my filesharing headless box on newer hardware and now I can't seem to connect to the Deluge daemon from remote hosts any more.
The daemon is running on a fresh install of Linux Mint 18, on the filesharing machine (we'll call it Box_1 for now)
(daemon version is whatever the linux mint repo gave me)
The client is also running on a fresh install of Linux Mint 18. There's a client on the filesharing machine (Box_1) and there's a client running on another machine on the same LAN (we'll call that Box_2).
Box_1 has an IP address of 192.168.0.1
Box_2 has an IP address of 192.168.0.2
The client on Box_1 has no problem connecting to the daemon at 127.0.0.1:58846, however the client on Box_2 shows 192.168.0.1 and 192.168.0.1:58846 both as offline/red dot. (Double-clicking on either just dismisses the connections window, but doesn't produce a connection.)
I've checked that the deluged process is running on Box_1, although the fact that the client on Box_1 can connect would seem to indicate that there's nothing wrong with the daemon itself.
My first suspicion was that there might be a firewall getting in the way, but I've ensured ufw is disabled and iptables is stopped on both machines, and /etc/hosts.allow and /etc/hosts.deny are both empty on both machines.
Also fwiw I can SSH into Box_1 from Box_2, and vice-versa, so it would appear the machines have connectivity, but Box_2 just can't see Box_1 listening.
Any suggestions would be greatly appreciated
The daemon is running on a fresh install of Linux Mint 18, on the filesharing machine (we'll call it Box_1 for now)
(daemon version is whatever the linux mint repo gave me)
The client is also running on a fresh install of Linux Mint 18. There's a client on the filesharing machine (Box_1) and there's a client running on another machine on the same LAN (we'll call that Box_2).
Box_1 has an IP address of 192.168.0.1
Box_2 has an IP address of 192.168.0.2
The client on Box_1 has no problem connecting to the daemon at 127.0.0.1:58846, however the client on Box_2 shows 192.168.0.1 and 192.168.0.1:58846 both as offline/red dot. (Double-clicking on either just dismisses the connections window, but doesn't produce a connection.)
I've checked that the deluged process is running on Box_1, although the fact that the client on Box_1 can connect would seem to indicate that there's nothing wrong with the daemon itself.
My first suspicion was that there might be a firewall getting in the way, but I've ensured ufw is disabled and iptables is stopped on both machines, and /etc/hosts.allow and /etc/hosts.deny are both empty on both machines.
Also fwiw I can SSH into Box_1 from Box_2, and vice-versa, so it would appear the machines have connectivity, but Box_2 just can't see Box_1 listening.
Any suggestions would be greatly appreciated