deluge client failed to connect to 127.0.0.1

#Deluge client failed to connect to 127.0.0.1 password#

Just had a thought, let's say you have your machine connected using your IP, and it's not disconnecting immediately. I can think of no smart reason why your local ip would work and the local loopback would not work, except that when you tried your actual ip the request would go to the network and back again, I presume. If it's a windows service, perhaps, and only perhaps, Windows sevices themselves check for localhost type connections and refuse them. However the service you are connecting to is the most likely culprit for refusing the connection.

This would allow you to connect to services etc on the local machine, kind of pretending to be a network machine but its not the best test.

The IP is a local loopback and is supposed to be like connecting to your machine remotely. I'm running on a raspberry pi 3b using DietPi. It's possible I think to edit the local hosts file and redirect 127.0.0.1 elsewhere and this could be a problem but I highly doubt it. Failed to connect to 127.0.0.1:58846 with reason: Username does not exist I'm trying to pass deluge-console commands through a script and also getting User name does not exist.

#Deluge client failed to connect to 127.0.0.1 password#

property authlevelsmapping property authlevelsmappingreverse connect (host '127.0.0.1', port 58846, username '', password '', skipauthentication False) Connects to a daemon. This class is used to connect to a daemon process and issue RPC requests. Maybe, sounds odd though, 127.0.0.1 is normally localhost right, so you would not expect a firewall to be in the wayĪnyway, try the word localhost instead of IP. deluge.ui.client module class deluge.ui.client.