1.1.0 RC2 cannot find daemon on LAN

[clarknova]

I run deluged on a headless server and usually connect via web or Gtk. I just upgraded from 1.0.7 to 1.1.0 RC2 and for some reason the gtk client won't connect to the daemon on the LAN. I had it previously set up to connect automatically, but the server doesn't show up in the connections manager. I used the Add button to add it manually but it shows the daemon as offline. I use the default port and double checked it in gtk and on the daemon via the web. I don't see anything in the release notes or the FAQ about a default username or password for the daemon. Did I miss something?

[clarknova]

I found my answer (sort of) here:
http://dev.deluge-torrent.org/wiki/ThinClient

It says that your username:password need to be entered into ~/.config/deluge/auth. For some reason I had "localclient:8ef8da6c9c96f81a663f4906e93541049a62c653" already in that file, not by me. I changed it to something else and gtk now connects as expected.

[johnnyg]

I found my answer (sort of) here:
http://dev.deluge-torrent.org/wiki/ThinClient

It says that your username:password need to be entered into ~/.config/deluge/auth. For some reason I had "localclient:8ef8da6c9c96f81a663f4906e93541049a62c653" already in that file, not by me. I changed it to something else and gtk now connects as expected.

localclient is automatically generated by the daemon so that any local clients can access it.

[Mindzai]

where is this file on windows?

[loki]

where is this file on windows?

In my windows it is in /user/appdata/roaming/deluge/
It should be a similar location.