When trying to use a torrent from an anti leech tracker (for example torrentbytes.net) every Bitcomet newer than 0.70 gets this error:
Tracker Response Error:torrent not registered with this tracker
please fix this (I tried every Version 0.71 0.72 0.73 and 0.74 and all 4 do have this problem)
When trying to use a torrent from an anti leech tracker (for example torrentbytes.net) every Bitcomet newer than 0.70 gets this error:
Tracker Response:torrent not registered with this tracker
please fix this (I tried every Version 0.71 0.72 0.73 and 0.74 and all 4 do have this problem)
I´m not a leecher in a private tracker or “anti-leech tracker”, but I get the same message.
Only 0.70 is the Stable version. We´ve keep using this one.
Plz, ppl fix this lil-bug
Cheers men.
tracker must not support the beta versions…
tracker must not support the beta versions…
0.71-0.74 are not beta versions. They’re just not stable, so trackers are banning them since they have problems shareing & connecting.
0.75 also gets this error: Tracker Response Error:torrent not registered with this tracker
0.75 works better than 0.71-0.74 but it still isn’t a stable release.
0.75 works better than 0.71-0.74 but it still isn’t a stable release.
and when we will see a stable reliase?
I like bitcomet 
:rolleyes:
0.75 is close. There are still issues with UDP that need to be worked out. When thats done other features need to be reenabled.
So basically we’ll see it when its done.
0.75 is close. There are still issues with UDP that need to be worked out. When thats down other features need to be reenabled.
So basically we’ll see it when its done.
Thank You
0.76 is out, and still I get the torrent not registered error which makes the new version useless
→ going back to 0.70 again
Send a message to Rny Smile about this telling him it’s happened on 0.71-0.76. I’m downloading 0.76 now to work it over and see what its doing.
0.77 still has this error
I had send an e-mail to support@bitcomet.com, now I just did send another one to bitcomet@yahoo.com
Excuse me, but there is no canonical “correct way” to report when finishing a torrent. The matter is, and has always been, undefined. So it is perhaps just a little arrogant to decide that there is only One True Way and that client X isn’t following someone’s bigotry and so is banned.
I suggest that the folks over at Bitsoup lack programming skills, can’t deal with any client that varies from their preconceptions, and so blame the clients rather than admitting their own shortcomings and repairing them.
The best cure for this is to stick to more enlightened trackers.
I’ve downloaded bitcomet 0.79 and its still not working. ,torrent not registered with this tracker, bitcomet 0.70 works fine, and whats the problem? :huh: :blink:
OK, here’s the reason for this problem.
Any version of Bitcomet higher than 0.70 has user-agent set to be Internet Explorer instead of Bittorrent/3.4.2 as it was in the previous versions… i suppose this is done because of the new http/ftp download capabilites… the problem is most of the trackers based on the torrentbits core have a piece of code in their announce scripts that prohibits access with browsers…
I think there are 2 possible solutions for this thing:
1 - all those sites change their codes to check both for user agent and peerid instead of user-agent only (like if that is ever gonna happen)
2 - BitComet can be fixed to change it’s user-agent dynamically - for example - if a torrent is downloaded it will be BitComet, BitTorrent, etc) and if BitComet is used as a http/ftp download manager the user-agent could be changed to IE, or whatever other browser…
Let’s hope someone from the coders will see this and fix the problem…
Version 0.80 finally solves this problem, but introduces another, download speeds are way lower than 0.70 and upload speed is zero or it’s incorrectly shown. If I install .70 all goes back to normal again.
edit: when uninstalling .80 and revgerting back to .70, my tracker complains that i have too many torrents transfering at the same time (which is not true), there’s something wrong there too…
Bitcomet is bannded from some trackers(bitsoup, …)… why? Because Bitcomet send to tracker wrong information…
They still recommend that you avoid the following clients:
• BitTorrent++,
• Nova Torrent,
• TorrentStorm.
• Bitcomet any version.
These clients do not report correctly to the tracker when canceling/finishing a torrent session. If you use them then a few MB may not be counted towards the stats near the end, and torrents may still be listed in your profile for some time after you have closed the client.
Also, clients in alpha or beta version should be avoided.
(from bitsoup site)
BitComet is banned from certain trackers because its DHT system works too well, thus avoiding to having to subscribe/sign-up to a private community (if only 1 member of a private community uses BitComet, all non members can connect through that 1 person).
Secondly, when connecting through DHT, boards that use stats get all haywire cuz the stats don’t show, simply because you are down/uploading from/to peers directly, not via the tracker… that is why BitComet has been wrongly tagged as the “Leecher’s Client”…
Even a dumpsite like Demonoid urges folks to not turn their DHT on when down/uploading, because their stats would get even more screwy than they are now…
JJ
I don’t think so…if that were true, then ALL versions of bitcomet would fail, but only verisions .71 ~ .79 have that problem…