Deluge Forum

why would the listening port change all the time. ???
every few days i notice that the "no incoming connections" indicator is active at bottom
i go into prefs and my port range are both set to lets say 44456, yet the active port is displayed as something else.
now to change this, i change both port range fields to something random, apply, then change them back to 44456, the only port open in my router.

wtf

i love the potential of deluged and its a nice interface, but
since i can never find anything i'm looking for by searching these forums, and since deluged crashes on me more than once a day, and since i spent most of the day trying to track down these problems, im pretty much over this.

oh yeah: and since these problems have persisted for me for several years over 3 or 4 versions of deluge..

yes my port has been changing once a week or for years. i ever reformatted my server, changed distros, and got the latest version of deluge, and it now crashes even more than it did before. all the other problems still persist. why even come out with new versions, when all the same problems from years ago are still not fixed. arg

See: http://dev.deluge-torrent.org/ticket/2122

I have the exact same problem.

Is great knowing the reason, but what would be great *and* useful would be knowing also a solution or a workaround at least

Maybe giving deluge a port range would fix it? and if so, how wide the range, 2 ports? 5 ports? more?

I think it has something to do with this, very often I find the described problem (random port selected, no incoming) and also deluged is using a lot of CPU (like 175% or so). Even forcing to use the selected port (change to whatever, apply, change back to desired port, apply) turns the port correctly but the high usage persists. Restarting deluged usually takes like 30 seconds and coming back, all downloading torrents need recheck and soon enough CPU use goes again to the roof and/or all torrents (even those with plenty of seeds that I know would be at several MiB/s in normal conditions) will download really slow if at all (like less than 10KiB/s)

The workaround is to set a range of 5-10 incoming ports

ok thanks for that cas. will give it a try.

i havn't had the high cpu usage. maybe i should check the server..
what i do get is a memory leak or something in deluge-gtk client 1.3.5. it runs on a different computer, but if i don't close it when im done with it it will quickly use all 2gig of ram and all 4gigs of swap. within about an hour the hardrive is thrashing painfully and the entire computer is frozen from lack of available memory. but perhaps this would be fixed in 1.3.6

i was so much happier using 1.3.1, but my main torrent site banned it becuase appearantly it causes their tracker problems.

too bad i havn't found anything else..

transmission is missing a few key features, and i found rtorrent a pain.

If you are referring to memory leak in Windows OS client then yes it's a known issue relating to gtk/pygtk and is out of our hands.

You can use any 1.3.x client with 1.3.x server (only server version is reported to tracker) but you should really use the latest release as there are quite a lot of bug fixes over these releases.