Sounds like it could be one and the same. My server runs fine to the best of my knowledge (at least it doesn't ever require manual intervention to keep it running) and my server is also fairly taxed overall. In the process of coming here to finally post about this, I noticed the 2.0 beta. I get the ...

Occasionally my client (windows) seems to disconnect from the server (window blanks out and I have to connect again). Even though other network based apps I use don't seem to experience disconnections, I assume this is some sort of network glitch like a timeout (I have ~600 torrents and fetching all...

Cool. So then the question is how to move forward. Is that something you want to fix? If not, can I fix it and submit it for inclusion in future releases? I would prefer the former since I would have to ramp up on deluge development but if it'll only get done if I do it myself, I'm willing to give i...

To expand on my prior post, I'm talking about escaping required by the Windows OS command line. Unless an ampersand is escaped, Windows interprets it as separating 2 commands, so it runs everything before the ampersand as one command and everything after it as another command (ref: http://www.robvan...

No, I'm not talking about encoding. I'm talking about escaping.

Wondering about this limitation again. I'm tempted to download source and attempt a fix. Could a fix potentially be committed into the source repository? Hoping to get tentative approval since that would help motivate me to go to the trouble.

I'm also now getting the dreaded urlopen internal error. Maybe we can petition for a new Deluge release with a version of python that solves this problem? It's a real bummer not to be able to use this plugin!

Any chance of enhancing this to allow a torrent to have multiple labels?

That specifically calls out Linux and this is Windows, not to mention the fact that I didn't have this problem before upgrading *and* I was getting incoming connections. Weird.

Restarting didn't help but changing it to a range of 3 ports did (it chose a different port than I had been using). All 3 ports are port forwarded (and the 1 was port forwarded before). So why would a singe port stop working in 1.3.9 but a range of 3 does work?