1.0.0_RC9 (0.9.09) Released

[chaky]

Hello! I'm using the latest svn version and my problem was also on RCs. The problem is that I do not receive response from one private tracker (http://www.trancebits.com). It just says "announce sent" and it stays that way all the way, but the timer is counting just fine. This happens only when I put torrent to download, but if I already have some torrent downloaded with another client (eg. Transmission) and I want to seed it with Deluge, than, when I put that torrent to seed with trancebits.com tracker, I do get response from tracker just fine. So, it only happens if I want to download something. There is no problem with a tracker (I think) because if I use rtorrent or Transmission than everything is working fine. All other private or public trackers are working fine. Thanks.

btw. registrations are open on trancebits.com, so if someone want to check on its own with Deluge.

[QQ321]

need proxy setting same old version 0.5 please

[antm88]

Hello! I'm using the latest svn version and my problem was also on RCs. The problem is that I do not receive response from one private tracker (http://www.trancebits.com). It just says "announce sent" and it stays that way all the way, but the timer is counting just fine. This happens only when I put torrent to download, but if I already have some torrent downloaded with another client (eg. Transmission) and I want to seed it with Deluge, than, when I put that torrent to seed with trancebits.com tracker, I do get response from tracker just fine. So, it only happens if I want to download something. There is no problem with a tracker (I think) because if I use rtorrent or Transmission than everything is working fine. All other private or public trackers are working fine. Thanks.

btw. registrations are open on trancebits.com, so if someone want to check on its own with Deluge.

I have the same problem with a private tracker (what.cd) - all of the torrents displayed 0 seeds, 0 leechers and it could not communicate with the tracker. I removed 1.0.0_RC5 and reinstalled 0.5.9.4 a couple of times - the torrents worked perfectly in 0.5.9.4 each time and refused to work in 1.0.0_RC5. The new version is completely unusable for me at the moment and I'm dying to have it working!!!

[loki]

People, a lot of private trackers block torrent clients that are in beta, RC, etc...
It would be nice if you no longer complain about it not connecting to your private tracker because of this issue. Now an open tracker, that could be a completely different issue, but I assume 90% of these people complaining are on private trackers with banned clients for whatever reasons.

[AnomynousPierson]

Feature Request:
password for connecting to deluged daemon

It would be very nice to be able to access deluged on my remote seedbox with the gtk ui at home.
For now I'll have to continue using an ssh tunnel or the webui.

[negge]

I installed the RC5 on Ubuntu Gutsy and it seemed to work, although I had to use my neighbours extremely weak Wifi to access the Internet so I couldn't check it out that much. I hope there will be a final version sometime soon. One thing, why are these releases called RCs, in my opinion these are beta versions 'cause every RC so far has contained atleast one showstopper bug...

Feature Request:
password for connecting to deluged daemon

It would be very nice to be able to access deluged on my remote seedbox with the gtk ui at home.
For now I'll have to continue using an ssh tunnel or the webui.

I thought that was one of the main purposes of separating the engine and the GUI. If that's not possible then the whole thing is almost useless.

[johnnyg]

the purpose of separating the ui and core is so that you can run deluge on a headless machine (which you now can).
you can control it remotely via the gtk provided you are on a local network with it (I would block the daemon port from the outside world).
if you want to control deluge from a remote computer not on the local network then it's best to use the web ui.

[chaky]

People, a lot of private trackers block torrent clients that are in beta, RC, etc...
It would be nice if you no longer complain about it not connecting to your private tracker because of this issue. Now an open tracker, that could be a completely different issue, but I assume 90% of these people complaining are on private trackers with banned clients for whatever reasons.

It's not that, because SVN version of Transmission is connecting to that tracker just fine. Also on trancebits forums I do not see any thread about blocking dev versions of clients or some kind of list of stable bittorrent clients which are permited to connect (this is usual on some other private trackers). But, on the other hand I can just go there and ask them about Deluge.

update: It seems that now it's working just fine. I have no idea why it did not worked in a last few days.

[loki]

It's not that, because SVN version of Transmission is connecting to that tracker just fine. Also on trancebits forums I do not see any thread about blocking dev versions of clients or some kind of list of stable bittorrent clients which are permited to connect (this is usual on some other private trackers). But, on the other hand I can just go there and ask them about Deluge.

update: It seems that now it's working just fine. I have no idea why it did not worked in a last few days.

I usually see it listed on the FAQ about accepted clients, the ones I've seen usually say something like, "May I use any bittorrent client? No, these are the allowed ones: {list follows here} Also, clients in alpha or beta version are banned."

The way it works from my understanding is most private trackers have a blacklist... any clients they add to this blacklist get blocked. If there is very few people using a particular, very newly released client, it could slip by unnoticed by not being on their list yet which could explain why some do work.

[AnomynousPierson]

Feature Request:
password for connecting to deluged daemon

It would be very nice to be able to access deluged on my remote seedbox with the gtk ui at home.
For now I'll have to continue using an ssh tunnel or the webui.

Hey look I quoted myself.

the purpose of separating the ui and core is so that you can run deluge on a headless machine (which you now can).
you can control it remotely via the gtk provided you are on a local network with it (I would block the daemon port from the outside world).
if you want to control deluge from a remote computer not on the local network then it's best to use the web ui.

Yes, it is a very good idea to block that port from the outside world even if there was a password feature on the daemon. To get around this I'm using an ssh tunnel to the remote machine but there is a problem with that...

BUG?:
The deluge gtk ui automatically assumes that anything at 127.0.0.1 is local when I've shown this isn't always the case. I'm sure the reasoning behind this was to alter the gui to show local vs. remote paths. To get around this I've specified the local ip(192.168.x.x) and while that works, it may be better to provide a checkbox in the connection manager to mark a connection as "local" or simply to provide a non-removable local entry and assume all others are remote.

I can't complain as it works and it's free.
Just my two cents.