emtec666 Posted January 5, 2006 Report Share Posted January 5, 2006 I created some torrents with µTorrent 1.3.000 (build 364) meant for a private trackers. So I have to re-download the torrent file from the site after uploading it (because a private passkey is added to the announce URL). Now when I start seeding after opening the torrent (containing the passkey) I can't connect to the trackers because µTorrent seems to be still sending the original non-passkeyed announce to the tracker. So it basically "remembers" the URL from the original torrent file (even when I have removed the torrent from the µTorrent folder and try again).Also on one site even the downloaders got an "invalid passkey" error even after I started seeding it after manually altering the announce URL. Very strange.If I create the torrents with Azureus and start seeding with µTorrent everything works fine.So I hope it can be changed so µTorrent does not remember the original URL from the torrent creation, but rather erases it, so I can seed right away without having to change the URL manually. For now I switch back to Azureus for torrent creation (at least for private trackers, on public trackers -no passkey needed- it works fine). Link to comment Share on other sites More sharing options...
Firon Posted January 6, 2006 Report Share Posted January 6, 2006 It actually adds the tracker to the properties, so it has BOTH URLs (the non-PID one and the PID one). And if you remove the torrent and load the new one, it will not remember any such thing, you must've loaded the wrong one. The tracker may have a timeout for changing PIDs (which has happened to me), which may be also your problem. Link to comment Share on other sites More sharing options...
emtec666 Posted January 8, 2006 Author Report Share Posted January 8, 2006 It actually adds the tracker to the properties, so it has BOTH URLs (the non-PID one and the PID one). And if you remove the torrent and load the new one, it will not remember any such thing, you must've loaded the wrong one. The tracker may have a timeout for changing PIDs (which has happened to me), which may be also your problem. I have tried it several times with multiple torrents......and of course I checked if I loaded the right torrent with MakeTorrent/TorrentSpy if it contained the passkeyed URL (I'm not that n00b LOL) and still the old non-passkeyed URL was loadedThen again I have seen the same problem with Azureus the last few times (it "remembers" the old non-passkeyed URL even though I load the new torrent)So it could very well be something on my comp (I use WinXP SP 1 ) Link to comment Share on other sites More sharing options...
EndsOfTime Posted January 8, 2006 Report Share Posted January 8, 2006 I seem to be having the same problem on my XP SP2 machine.Turning off firewall didn't help either.1 Seeder (Me) 8 Peers - can't upload to any of them.Happened on 2 separate private trackers with or without private torrent enabled.I am now in the midst of verifying this by seeding the exact same file with a torrent created using MakeTorrent. Link to comment Share on other sites More sharing options...
EndsOfTime Posted January 8, 2006 Report Share Posted January 8, 2006 Okay I've verified that it is probably some bug with the seeding engine of uTorrent.1. I've created 2 separate torrent using uTorrent's create a Torrent feature and MakeTorrent.2. Tested both torrents on 2 separate private trackers.3. Unable to uplaod one bit to the peers or more correctly unable to connect to them in the first place.4. Tried the same torrents with Azureus and voila it uploads. Link to comment Share on other sites More sharing options...
Firon Posted January 8, 2006 Report Share Posted January 8, 2006 Turn on peer.lazy_bitfield. THe reason it works on Azureus is because Azureus has the equivalent of it on always. Your ISP interferes with seeding. Link to comment Share on other sites More sharing options...
EndsOfTime Posted January 8, 2006 Report Share Posted January 8, 2006 Thanks its working fine now!!!GREAT! Link to comment Share on other sites More sharing options...
emtec666 Posted January 9, 2006 Author Report Share Posted January 9, 2006 Turn on peer.lazy_bitfield. THe reason it works on Azureus is because Azureus has the equivalent of it on always. Your ISP interferes with seeding.I'll try that next time too and see if it helps.Could it hurt (e.g. performance) to have the peer.lazy_bitfield it turned on always (since the default setting is off)? Link to comment Share on other sites More sharing options...
Firon Posted January 9, 2006 Report Share Posted January 9, 2006 I'm not sure if it could hurt, in all honesty. Link to comment Share on other sites More sharing options...
EndsOfTime Posted January 10, 2006 Report Share Posted January 10, 2006 It didn't work again. This time even "peer.lazy_bitfield" didn't help.Same thing I have no idea what I should enable in uTorrent this time. Any clue?Uploading fine with Azureus. Link to comment Share on other sites More sharing options...
EndsOfTime Posted January 10, 2006 Report Share Posted January 10, 2006 Its so weird...its working now...But I wonder why it took so long...I've cracked XP SP2 to allow for 100 half open TCP connections and enabled that many in uTorrent. Is this the cause for the slow connection.Sorry for bombarding this thread. Link to comment Share on other sites More sharing options...
Firon Posted January 10, 2006 Report Share Posted January 10, 2006 Try using 70 in µTorrent.By the way, do you have Network OK in the status bar? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.