Remote GUI accesses local filesystem instead of remote one

Suggestions and discussion of future versions
Post Reply
Nuwanda
New User
New User
Posts: 3
Joined: Tue Jul 21, 2009 6:09 pm

Remote GUI accesses local filesystem instead of remote one

Post by Nuwanda »

Hi.

I am using Deluge 1.1.9 on an PC running openSUSE in classic mode (daemon + GUI), but with remote connections allowed. I also use a client-only (also 1.1.9) in a PC running Windows that connects to the daemon in the openSUSE PC.

Everything seems to works fine, except filesystem-related stuff in the Windows client. Whenever it tries to access a folder, it accesses the local (Windows PC) filesystem instead of the server (openSUSE PC) one, and I get the following error (note that the Windows PC has a Spanish locale):

"The folder contents could not be displayed

Error getting information for '/mnt/datos/Downloads':
El sistema no puede hallar la ruta especificada."

This, among other things, doesn't let me add new torrents using the Windows client, because it sets the download folder to / instead of the default /mnt/datos/Downloads.

On a side note, it is the expected behavior the Windows client to access the local filesystem to add a new torrent by file, but for mostly everything else, it should access the server filesystem.
Nuwanda
New User
New User
Posts: 3
Joined: Tue Jul 21, 2009 6:09 pm

Re: Remote GUI accesses local filesystem instead of remote one

Post by Nuwanda »

I continued searching on this issue, and I arrived to this post XD
(BTW, I had searched the forum before posting, but it seems I didn't use the right keywords)

Anyway, using 127.0.0.2 doesn't seem to work in Windows XP SP3. If I ping 127.0.0.2, I get a response from 127.0.0.1 instead of 127.0.0.2, and the Status in the Deluge Connection Manager doesn't turn green (it does if I use 127.0.0.1)...
Nuwanda
New User
New User
Posts: 3
Joined: Tue Jul 21, 2009 6:09 pm

Re: Remote GUI accesses local filesystem instead of remote one

Post by Nuwanda »

OK, I figured it out :-P

I need to do:
putty -L127.0.0.2:58846:server_ip:58846 ...
to bind the port to 127.0.0.2 instead of 127.0.0.1...

BTW, the ThinClient article in the wiki should be updated, in the GTK UI client Setup with SSH tunneling section, it says to use "localhost", which has this problem...
Post Reply