So... if I rename the C:\config_location\core.conf to .old, and adapt the one in %APPDATA%, it makes no difference to the Daemon. A new C:\config_location\core.conf is created with the allow_remote set to "false" upon starting the Daemon via NSSM again. If I stop the service, manually set ...

Interestingly the core.conf file in the Appdata folder has an earlier modification time, and the allow_remote setting is set to "False" so I'm guessing the C:\config_location\core.conf file is the one being used, otherwise I wouldn't be able to connect to the Daemon at all. It seems the GU...

My god, I feel quite stupid now... I've solved the above issue, minutes after posting it. However this has caused me quite a bit of frustration over the last few days after going around in circles. I double checked the allow_remote setting in the C:\config_location\core.conf file , and I noticed tha...

I'm having an issue connecting to the Deluge Daemon on my home server. It's a shame since I really like running Deluge as a daemon on my server. It's only since I've upgraded the server's hardware, my old server system functioned just fine. My server runs Windows and I have Deluge set up as a servic...