Just had a thought, let's say you have your machine connected using your IP, and it's not disconnecting immediately. Does MacOSX system not supported After define: RxDockerClient client omDefaultEnv() It throw errors: main c.s.r.d.client.DefaultRxDockerClient. 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. I think it may have something to do with Chromes aggress. It does however, work in firefox on both of the above OS. 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. In Chrome (latest version and also in canary) (on either arch linux or macOS), the web ui fails to upload torrent files.
The IP is a local loopback and is supposed to be like connecting to your machine remotely. I think its ok, 1) because the server is not running and 2) because this is my secondary problem.
DELUGE CLIENT FAILED TO CONNECT TO 127.0.0.1 PASSWORD
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. If I try to deluge-console I get a 'Failed to connect to 127.0.0.1:58846 with reason: Password does not match'. 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.
0 kommentar(er)
