Here are a few more.Didn't had space to include them above so here they are.


"rejected by tracker - Port xxxx is blacklisted"

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.
The tracker in question 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 necessarily limited to, the following:
Direct Connect 411 - 413
Kazaa 1214
eDonkey 4662
Gnutella 6346 - 6347
BitTorrent 6881 - 6889

In order to use use the 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.

The more random the choice is the harder it will be for ISPs to catch on to you and start limiting speeds on the ports you use. If we simply define another port range on the forum, your 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.

"Invalid or missing passkey" error?

Some torrent sites have started individually keying torrents to individual members. There is nothing you can do about it, apart from registering with the tracker's site and getting your own torrent from them.
The person who has posted this has now probably been banned/deleted from the tracker's site by now as the Passkey thing is to keep the tracker private, the usual proviso is that the member does not post the torrent on a public tracker like Youceff Torrents.


Problem connecting to tracker - <upload error (10065, 'no route to host')>

This can be caused by the remote host appearing to be down (which could be the port chosen being blocked at the said host).
This could also be down to a system admin at work having noticed unusual traffic and blocked a port or banned an IP then.
I would say try connecting for a couple of days, if you are still having problems with the same error message then I suggest you find another .torrent.