Deluge Shows Seeing and Connecting
Site-specific problem with connection to tracker
Full general support for problems installing or using Deluge
- tbone
- New User
- Posts: five
- Joined: Monday Jul 09, 2007 3:39 pm
Site-specific trouble with connection to tracker
Hi,
First I want to congratulate the developers on this excellent torrent client for linux. Great work!
I compiled and built Deluge 0.5.2 from source on my Ubuntu vii.04 earlier today. When calculation torrents from various sites (besides sites with passkeys), they connect and beginning like they should. Except from at ane site, where afterwards adding the torrent(due south), it stays put at "Connecting". This site also has a passkey in the tracker url. The tracker is functioning itself, I asked for whatever tips at their forum, only haven't received any wise solutions withal
So, I'k turning to you guys, in hope for whatever skillful tips or ideas. Could this be a problem with Deluge, or is it most plausible that this is a trouble from the torrent site'due south point of view? Could it be that they don't allow the Deluge-customer? Their FAQ does not mention Deluge as a banned client. If information technology turns out this isn't a problem with Deluge, maybe I should get in touch on with the site admin at the specific site?
Torbjørn
- markybob
- Compulsive Poster
- Posts: 1230
- Joined: Thu May 24, 2007 11:27 pm
- Location: Chicago, IL, USA
- Contact:
Re: Site-specific problem with connectedness to tracker
tbone wrote:How-do-you-do,
First I want to congratulate the developers on this excellent torrent client for linux. Dandy work!
I compiled and built Deluge 0.5.2 from source on my Ubuntu 7.04 before today. When adding torrents from various sites (also sites with passkeys), they connect and start similar they should. Except from at ane site, where later on adding the torrent(s), it stays put at "Connecting". This site also has a passkey in the tracker url. The tracker is functioning itself, I asked for any tips at their forum, but oasis't received whatever wise solutions yet
![]()
So, I'm turning to you guys, in hope for any skilful tips or ideas. Could this be a problem with Deluge, or is it virtually plausible that this is a problem from the torrent site's point of view? Could information technology be that they don't allow the Drench-client? Their FAQ does not mention Deluge as a banned client. If it turns out this isn't a trouble with Drench, perhaps I should get in touch on with the site admin at the specific site?
Torbjørn
could be various things. some sites force you to log into their site showtime, and so they can take your ip, which then allows you lot to actually talk to the tracker. take you logged into the site itself and then forced deluge to reannounce?
- tbone
- New User
- Posts: v
- Joined: Mon Jul 09, 2007 3:39 pm
Re: Site-specific trouble with connection to tracker
Hi Markybob,
yes, I have tried logging in, grabbing the torrent and starting it, and and so logged out and in again at the site, with a reannounce in deluge. No success.
What are those other various potential reasons?
I notice this thing very foreign, since torrents from every other site I endeavour work just like normal. 1 thing that I have noticed, is that the tracker given with the torrent, doesn't contain a ":<port way>" after the hostname, similar many of the other tracker urls do. Information technology does not do that, because it communicates on port 80 - the standard port, according to the people at the torrent site'south forum. Could this accept relevance?
- shirish
- Seeder
- Posts: 163
- Joined: Fri May 25, 2007 4:01 am
- Location: South Asia, Bharat
Re: Site-specific problem with connection to tracker
confirmed this one also with bitnation which likewise does the same thing. There is no port denote every bit it uses port 80.
using latest changeset 882. Did the following steps
- Fabricated clean
- removed the .config/deluge
- went to the site
- logged out,
- logged back in
- paused the torrent
- did update tracker
- no effect
- while connecting did update tracker
- no effect
- changed the upload bandwidth to four kbps & fifty-fifty lower in case handshake was not happening or something
- no change
other torrents uploading happily. This used to work well with changeset 820 till changeset 870 something only with 4 kbps . http://dev.deluge-torrent.org/ticket/389. Possibly you can endeavour that. Meanwhile any other ideas?
Terminal edited past shirish on Wed Jul eleven, 2007 5:36 pm, edited 1 time in total.
Debian Sid, Intel Dual-Core, 512 kbps DL , 64 Kbps UL, deluge-1.3.5, pieces plugin, GNOME 3.four.x
All posts nether creative commons http://creativecommons.org/licenses/past-nc/three.0/
- shirish
- Seeder
- Posts: 163
- Joined: Friday May 25, 2007 4:01 am
- Location: S Asia, India
Re: Site-specific problem with connection to tracker
Another potential solution. This might be if you are on gutsy as I observed this but with svn 1023 so information technology might fit or not your use-example. See if yous have enabled meaty storage drove. Although this preference should non have any bearing only clicking on information technology past error or otherwise does two things. Yous have no incoming connection shown on the status bar, as well the ones which do not have some port defined announce urls keep on showing connecting.
Debian Sid, Intel Dual-Core, 512 kbps DL , 64 Kbps UL, drench-1.3.v, pieces plugin, GNOME 3.iv.x
All posts under creative commons http://creativecommons.org/licenses/by-nc/iii.0/
- scoffer
- New User
- Posts: 5
- Joined: Thu Jul 19, 2007 eleven:43 am
Re: Site-specific trouble with connection to tracker
Aforementioned trouble here..
I can seed and download on every site with rtorrent but with deluge I tin can connect to but some of trackers.
I have redownloaded .torrent files etc...
Could it be becouse deluges denote string is a chip different?
Drench:
my.ip.accost - - [nineteen/Jul/2007:thirteen:30:34 +0200] "Become /announce.php?passkey=b561f01981f0ac9aef56dd3c7473b5e0
&info_hash=m%e7%98Vl%90%08%b3Yrj%05G-%c8tl%b5B%f3&peer_id=-DE0520-ECWoGU5L2W2Q&port=6884
&uploaded=0&downloaded=0&left=59032168&key=1ec438d4&compact=1&numwant=200&supportcrypto=1&no_peer_id=ane
HTTP/1.0" 200 67 "-" "Deluge 0.v.2"
rTorrent
my.ip.address - - [15/Jul/2007:17:sixteen:16 +0200] "Go /announce.php?passkey=faafea09801bb5edec5aef7c87eb2a01
?info_hash=%BD%C7%F6%A8%26%EEL%85%A25%twenty%EC%E0%85%9F%BAN%D0%C2m&peer_id=-lt0A40-1000%F9%7E%3C%CAT%C3%82%0F%1C%0B%88
¢ral=110943be&compact=1&port=6978&uploaded=5163101310&downloaded=0&left=0
HTTP/ane.ane" 200 94 "-" "rtorrent/0.half dozen.iv/0.10.4"
edit :
Forgot to say but I have tried 0.v.3 RC1 and 0.v.2-1.
Distribution is Ubuntu Feisty
Also did y'all notice that at rtorrent its ?info_hash and at drench it's &info_hash
- scoffer
- New User
- Posts: 5
- Joined: Thu Jul xix, 2007 11:43 am
Re: Site-specific problem with connection to tracker
This is very strange just I found temporarily solution.
I changed the connection ports to same what rtorrent uses and it started working...altought all my other clients piece of work at deluges default ports only drench doesn't properly.
- plisk
- Member
- Posts: 42
- Joined: Sun Jul fifteen, 2007 7:52 am
Re: Site-specific trouble with connexion to tracker
shirish wrote:confirmed this one as well with bitnation which as well does the same thing. In that location is no port announce equally it uses port 80.
using latest changeset 882.
...
Meanwhile any other ideas?
Just tried bitnation in both deluge and ktorrent. In ktorrent it writes in tracker status that port 6884 is blocklisted and don't connect. In deluge it's just writes connecting and do cypher using the same port. And if you change port to same random i both clients start downloading. And so it's just because of blacklisted default ports on some trackers. So all this i think will results in just more than informative Tracker Condition message in Torrent Info surface area at the bottom and maybe some tweaks to status message in the queue.
- shirish
- Seeder
- Posts: 163
- Joined: Fri May 25, 2007 4:01 am
- Location: Southern asia, India
Re: Site-specific trouble with connexion to tracker
plisk wrote:
shirish wrote:confirmed this one besides with bitnation which too does the same affair. There is no port announce as it uses port 80.
using latest changeset 882.
...
Meanwhile any other ideas?Just tried bitnation in both deluge and ktorrent. In ktorrent it writes in tracker status that port 6884 is blocklisted and don't connect. In deluge it'southward merely writes connecting and do zero using the aforementioned port. And if yous change port to same random one both clients start downloading. Then information technology'south only because of blacklisted default ports on some trackers. So all this i remember will results in just more informative Tracker Status message in Torrent Info area at the bottom and maybe some tweaks to status message in the queue.
Plisk,
I never apply the default ports, I have ever used custom ports (port-forwarded my modem/router) in the higher ranges 30k + as that is a expert bet. I had also chatted in the bitnation IRC (irc.bitnation.com) to know if they block some ports and apart from default ports which you have said about it shouldn't be happening. I see yous closed down ticket 389 http://dev.deluge-torrent.org/ticket/389#comment:2 and would exist happy to assist in testing any new revision you throw at us. Dunno if this can/volition be done in 0.5.iii or one time it is out of the door. Just let us know when you plan to play with it. Looking forrard to testing & reporting the same on the forum. Cheers!
Debian Sid, Intel Dual-Core, 512 kbps DL , 64 Kbps UL, deluge-ane.iii.5, pieces plugin, GNOME 3.4.x
All posts under creative commons http://creativecommons.org/licenses/past-nc/three.0/
Source: https://forum.deluge-torrent.org/viewtopic.php?t=170
Posting Komentar untuk "Deluge Shows Seeing and Connecting"