Howto: Using the GtkUi over a SSH tunnel

[Chiphead2XS]

If you want to use Deluge e.g. on a dedicated server but do not want to open up the administration port for the whole outside world, then this little guide is for you.
Another benefit is, that the whole communication with the server (deluged) is encrypted.

Set up Deluge as described in the Thin Client Tutorial.
In the "Server Setup" part, skip step two ("Enable remote connections") which means basically: leave "allow_remote" set to "False".

Now it is time to start up the tunnel. On a terminal type:

Code: Select all

ssh -l yourusername -L 127.0.1.1:58846:127.0.0.1:58846 yourdomainorip.tld

Yes, 127.0.1.1 is not a typo, it won't work if you use 127.0.0.1, so make sure you typed it correct.

Now proceed in the tutorial onto the Client Setup.
In step five do not use your servers public IP but 127.0.1.1 (again: it is not 127.0.0.1).
Proceed as described in the tutorial.

Congratulations! You can now access deluge on the server via the GTK UI over an encrypted connection and noone is able to start bruteforcing your login since the port is still closed for the outside world.

Remember that you need to start the tunnel every time before you can access deluged via the GtkUi.

Further reading: http://www.google.de/search?q=ssh+tunnel

Maybe someone can merge this little guide into the wiki - thx.

Kind Regards

[johnnyg]

Thanks, I've stickied this for the moment and I'll eventually include it in the wiki.

[yawie]

The GTKui is quite bandwidth eating for slow remote connection.
I do the same but with the web client. As you pointed out, this technique does not implys port forwarding and publicly open some connection to deluge.

If the daemon is started you only have to do this :

Code: Select all

ssh login@publicIP -L8112:localhost:8112
deluge --ui web
in a browser go to http://localhost:8112

With the Ajax webui interface, this solution is very nice.

[Chiphead2XS]

Hi yawie,

yes, this is indeed one solution for securely accessing the web ui. However, if I remember correct, then the web ui natively supports (with some setup) connections over HTTPS which is basically the same as tunneling over SSH.
But there is still the problem that the port for the web ui is publicly accessible which might not be preferred since mighty Bob (remember Alice ) could
a) find out that Deluge is running on that machine and
b) start guessing/bruteforcing the passphrase

But that is something I targeted in the other thread.

Kind regards

[johnnyg]

Wiki has been updated: http://dev.deluge-torrent.org/wiki/ThinClient.