My server runs Windows and I have Deluge set up as a service via NSSM (with deluged-debug.exe & deluge-web-debug.exe) just as is outlined here in the instructions.
https://dev.deluge-torrent.org/wiki/Use ... MS_Windows
The Daemon is running. I can connect to it just fine to the daemon via 127.0.0.1:58846 on the Server system, but I can't connect to the Daemon running on the Server via the Thin Client on the regular desktop.
I can also connect just fine to Web UI on both the server via http://127.0.0.1:8112 and my regular desktop (also running Windows) via http://192.168.0.190:8112 (static IP of my server).
I have a username & password defined in C:\config_location\auth and I have allow_remote set to "true" in C:\config_location\core.conf
I have rules defined in Windows Firewall to allow connections via Port 58846 & 8112 also.
Does anyone have any ideas? This seems to be a common enough issue.
If I try and use deluge-console.exe on the Client Desktop, I get the following:
Code: Select all
C:\Program Files (x86)\Deluge>deluge-console connect 192.168.0.190:58846 mark mark
Failed to connect to 192.168.0.190:58846 with reason: No connection could be made because the target machine actively refused it.