Deluge in thin client / server mode loosing configuration

[sherbyx]

I'm using deluge 1.3.1 in client/server configuration over ssh. When I connect to the remote deluged I receive an error message that the "Download to" directory doesn't exists. Also when I use the Preferences dialog I receive 4 of these messages (one for every download path: download to, move completed to, auto add .torrents from, copy of .torrent files to).

I can understand that I receive the errors because the paths don't exist on the client machine (which is very annoying), but the problem is that in some cases the client changes these paths to "/".
Is there any way to avoid path validation or to stop deluge changing them to some existing path on the client machine? Also this is very annoying because I need to connect to the remote machine and change these paths directly in the config file (or using deluge-console) every time it happens.

Thanks,
Serban

[johnnyg]

I'm guessing that you're using a ssh tunnel bound to 127.0.0.1?
If you look at the thin client guide, you'll see that we recommend using 127.0.0.2 (so that deluge doesn't think the daemon is on the localhost).

[sherbyx]

Wow, thanks for the quick reply.
Actually I've seen the difference in the guide, but I didn't thought that there's some hidden logic behind the bind address.
I'll give it a try. Thanks again.

[johnnyg]

Actually I've seen the difference in the guide, but I didn't thought that there's some hidden logic behind the bind address.

Good point, I've added a note to the user guide.