Apparently the WebUI isn't alone in having difficulty staying connected with a large number of torrents. The GTK UI over SSH starts to fail at around 1000 torrents. It simply becomes unresponsive, then silently drops the connection (at this point the UI becomes responsive again, it's just that there...

I don't appear to have permission to do that.

Ah, just in the Development sub-forum, or is there an official place for such (since it's not technically a "bug")?

Hah, OK, I've got it solved. The articles you linked to were missing one minor detail, the tiny puzzle piece that gives the same result in PuTTY as the guide's original SSH commandline: For the "Source port" field in PuTTY, one needs to specify "127.0.0.2:58846" instead of just t...

Yeah, I have no idea where I'm going wrong, but I can't get Deluge on my local system to see the remote daemon. I started a PuTTY session with a tunnel for port 58846 to localhost:58846 (also tried the full 127.0.0.2:58846:localhost:58846 as in the guide), then followed the rest of the guide, and th...

OK, I'll give the GTK client a shot... but I need a bit of help in terms of how to set it up on a Windows (7, x64) machine and connect to the server over SSH. The Thin Client Userguide seems to be written for someone using Linux on both ends. What I'm not clear on: I use PuTTY to SSH into the server...

I'm curious why you would have any reason to do this. Don't you want the data that you torrent?

Nothing crucial; I just prefer the simplicity of the WebUI (i.e. not needing an application installed). I'd like to try to resolve the issue first if possible...

I'm running Deluge 1.3.2 on an OVH server (SP2010 Storage) under Ubuntu Server 10.04 64-bit. If I remember correctly the server has a 3 GHz dual-core CPU, 4 GB of RAM, and a 4 x 1.5 TB RAID-5 array. I'm connecting to that using the WebUI in either Firefox or Chrome (usually Chrome, but I tried Firef...