razaq

latest image, not remotely, same phyiscal network logs show no errors delugevpn | [info] Waiting for Deluge process to start listening on port 58846... delugevpn | delugevpn | 2021-03-15 16:39:12,462 DEBG 'watchdog-script' stdout output: delugevpn | [info] Deluge process listening on port 58846

LAN_NETWORK=192.168.178.0/24 the daemon is also set to allow remote connections. there is no firewall for the local lan and the webui works (from 192.168.178.37:8112), which should mean that the daemon is also running without issues. as i said when i do a port check on the host machine for port 58846 (daemon port) using 127.0.0.1, i see that the port is open, only when using the lan address 192.168.178.37 does it time out. doing the same port check for the webui port 8112 works in both cases.

all i am trying to do is connect to the daemon port from another machine in the same lan using the gtk ui as ThinClient, which has worked previously without any issues (I have already completely reinstalled the image, so that is ruled out)

ideally both ways obviously. i mean the webui does work from local lan (192.168.178.37:8112), just the daemon port times out (192.168.178.37:58846). how can i test the answer to your question easily? these are the ports that docker ps is showing: 0.0.0.0:8112->8112/tcp, 0.0.0.0:8118->8118/tcp, 0.0.0.0:58846->58846/tcp, 0.0.0.0:58946->58946/tcp, 58946/udp

even after hours of trial and error i can not figure this out. Daemon just does not listen to LAN ip for some reason...

Hey im having an issue with your image. It used to work like a charm but I recently cannot connect to the daemon port anymore. The webui works great, daemon port is default 58846 and remote connections are allowed. The docker container also has the port forwarded, i do not have a firewall for the local network. On the host machine (local lan address 192.168.178.37) nc -vc 192.168.178.37 58846 times out, while nc -vc 127.0.0.1 58846 shows the port as open. I start the container with LAN_NETWORK=192.168.178.0/24 so no problem there either. So it seems for some reason docker does not listen to the lan address of the machine and only on localhost. Any ideas?