'Move Storage' error when connected to server via ssh tunnel

[mrmacedonian]

A few months ago, I decided to start connecting to a headless install via ssh tunnel because I would be traveling and I wanted that extra layer of encryption.

Normally, I use labels to manage 'move completed to..' and it is still working well. However, I just made a new label and when I attempt to set a 'move completed to..' under the Location tab it is bringing up the local file system and when I enter a file path located on the server, it brings up an error because that file path does not exist in the local file system. I tried to move the location of an existing torrent and still deluge only accepts a local file path.

At first I thought this was a bug of some sort so I made sure I updated both server and client, restarted both machines and still same behavior. It finally occurred to me that the difference between the last label I created and now is the change to connect via ssh tunnel.

Deluge is still in thin-client mode (Classic Mode disabled) and connecting to host 'user@127.0.0.1:port,' so I am not sure why there is any change as far as the thin-client is concerned, but that has been the only change. When I remove that host and add one with the direct IP 'move completed to..' and 'move storage' both work fine, so that's definitively the cause.

I looked through post subject lines on the first few pages and didn't see one concerning 'Move Storage' so I thought I would see if anyone has experienced this and if there's any fix or workaround (other than connecting directly when needing to edit 'move completed to..' or manually moving a torrent).

thanks,
endi

[Cas]

Any forum or wiki search about ssh tunnel would give you answer!

http://dev.deluge-torrent.org/wiki/User ... eSSHTunnel

[mrmacedonian]

And what answer would that be?

Nothing on that page references which file system the thin-client will use, what causes the difference, or how to have the thin-client use the server file system for 'Move Storage' or 'move completed to..' operations.

[edit]: the post does mention using 127.0.0.2 rather than localhost as this will cause issues, but I'm already doing that.

[update]: nevermind, I deleted all the hosts and my tunnel script. Once I made sure I used 127.0.0.2 in all instanced the file path issue was resolved. I mis-read the wiki when first configuring.

Thanks again,

endi