Deluge WebUI not responding to remote IPs

[kill-9]

So I love Deluge, and wanted to set it up on my RPI. Runs great, but I can't seem to get it to respond to foreign traffic.

Running tshark I get the following when I'm accessing it from the remote world.

Code: Select all

Capturing on eth0
  7.654904 (Remote IP) -> 192.168.1.51 TCP 66 9061 > xmltec-xmlmail [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
  7.654908 (Remote IP) -> 192.168.1.51 TCP 66 56678 > xmltec-xmlmail [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
  7.892072 (Remote IP) -> 192.168.1.51 TCP 66 13159 > xmltec-xmlmail [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
 10.639769 (Remote IP) -> 192.168.1.51 TCP 66 56678 > xmltec-xmlmail [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
 10.641413 (Remote IP) -> 192.168.1.51 TCP 66 9061 > xmltec-xmlmail [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
 10.891542 (Remote IP) -> 192.168.1.51 TCP 66 13159 > xmltec-xmlmail [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
 16.642481 (Remote IP) -> 192.168.1.51 TCP 62 56678 > xmltec-xmlmail [SYN] Seq=0 Win=8192 Len=0 MSS=1460 SACK_PERM=1
 16.642485 (Remote IP) -> 192.168.1.51 TCP 62 9061 > xmltec-xmlmail [SYN] Seq=0 Win=8192 Len=0 MSS=1460 SACK_PERM=1
 16.887327 (Remote IP) -> 192.168.1.51 TCP 62 13159 > xmltec-xmlmail [SYN] Seq=0 Win=8192 Len=0 MSS=1460 SACK_PERM=1

But it works fine from a local network and responds to the traffic. Is there a host whitelist somewhere that I'm missing in the configs? The listen_interface parameter is blank and allow_remote is true. Any insight you guys could provide? I'm sure I'm missing something from the config but I can't find anything.

[kill-9]

Anyone have any insight? I've tried other ports and it seems to do the same thing. I know its not a firewall issue because I captured right on the box itself.

[kill-9]

One more bump. I just want to make sure its a proper bug before I report it.

[Cas]

This is very unlikely to be a deluge (web) issue if you can access it through local network.

Note the listen_interface and allow_remote options are for the daemon not webui

[kill-9]

This is very unlikely to be a deluge (web) issue if you can access it through local network.

Note the listen_interface and allow_remote options are for the daemon not webui

While I would agree, the wireshark capture above is on the box itself and it isn't generating return traffic. Even if there was a firewall on this box (which I've ensured there isn't) I would see the traffic generated.

Good to know those are for the daemon though. Is there logging that I can do to confirm that it is receiving the traffic?