Страница 1 из 1
Rejected by trecker
Добавлено: Вт май 31, 2005 14:39
PH0b0S
Если я пытаюсь скачать или седеть фаилы с нового торрента мне выдаёт ошибку
Rejected by tracker, invalid pass-key, Re-download the torrent. Сбрасывал пасскей с меню аккаунта, не помогает.
Добавлено: Вт май 31, 2005 16:14
Force
3 В профайле есть опция Reset passkey, поставте галочку и нажмите кнопку submit changes
галочка не поставится но информация занесется и все будет окей
Добавлено: Вт май 31, 2005 17:46
PH0b0S
Сбрасывал пасскей с меню аккаунта
Добавлено: Вт май 31, 2005 18:17
Danik
после этого слей *.torrent файл с трекера еще раз
ЗЫ между прочим под той самой галочкой в профайле есть надпись "Any active torrents must be downloaded again to continue leeching/seeding."
Добавлено: Вт май 31, 2005 20:59
PH0b0S
Danik, знаю, ща уже новая фишка начала высовываться, port 6883 is blacklisted.
[off]добавлено спустя 1 час:[/off]
Похоже что новому трекеру просто не нравится опера, в ИЕ всё заработало
Добавлено: Вт май 31, 2005 21:07
Danik
опера тут не причем, вот выдержка из FAQ :
Why do I get a "rejected by tracker - Port xxxx is blacklisted" error?
Your client is reporting to the tracker that it uses one of the default bittorrent ports (6881-6889) or any other common p2p port for incoming connections.
.MD BitTorrent Tracker does not allow clients to use ports commonly associated with p2p protocols. The reason for this is that it is a common practice for ISPs to throttle those ports (that is, limit the bandwidth, hence the speed).
The blocked ports list include, but is not neccessarily limited to, the following:
Direct Connect 411 - 413
Kazaa 1214
eDonkey 4662
Gnutella 6346 - 6347
BitTorrent 6881 - 6889
In order to use use our tracker you must configure your client to use any port range that does not contain those ports (a range within the region 49152 through 65535 is preferable, cf. IANA). Notice that some clients, like Azureus 2.0.7.0 or higher, use a single port for all torrents, while most others use one port per open torrent. The size of the range you choose should take this into account (typically less than 10 ports wide. There is no benefit whatsoever in choosing a wide range, and there are possible security implications).
These ports are used for connections between peers, not client to tracker. Therefore this change will not interfere with your ability to use other trackers (in fact it should increase your speed with torrents from any tracker, not just ours). Your client will also still be able to connect to peers that are using the standard ports. If your client does not allow custom ports to be used, you will have to switch to one that does.
Do not ask us, or in the forums, which ports you should choose. The more random the choice is the harder it will be for ISPs to catch on to us and start limiting speeds on the ports we use. If we simply define another range ISPs will start throttling that range also.
Finally, remember to forward the chosen ports in your router and/or open them in your firewall, should you have them. See the Why am I listed as not connectable? section and links therein for more information on this.
если в краце то указанные порты заблокированны трекером, потому что многие провацйдеры их по умолчанию урезают
