| |
 |
Informations de site - Top |
| |
|
 |
|
 |
Informations d'utilisateur - Top |
| |
|
 |
 |
J'ai enregistré un compte(un compte rendu), mais je n'ai pas reçu le courrier électronique de confirmation!
Vous pouvez utiliser ce formulaire a> pour supprimer votre compte de sorte que vous pouvez vous réinscrire.
Notez cependant que si vous n'avez pas reçu l'e-mail la première fois il ne sera probablement sur de recevoir la deuxième fois ou l'autre de sorte que vous devriez vraiment essayer est une autre adresse e-mail.
Pourquoi mon numéro(nombre) de port est-il annoncé comme "---" ? (Et pourquoi devrais-je me soucier ?)
Le tracker a déterminé que vous êtes derrière un pare-feu ou NAT et ne peut pas accepter les connexions entrantes.
Cela signifie que d'autres pairs dans l'essaim sera pas en mesure de se connecter à vous, vous seul pour eux. Pire encore,
si les deux clients sont dans cet état, ils ne seront pas en mesure de communiquer avec tous. Ceci a évidemment un
effet néfaste sur la vitesse globale.
La façon de résoudre le problème consiste à ouvrir les ports utilisés pour les connexions entrantes
(la même gamme que vous avez définie dans votre client) sur le pare-feu et / ou la configuration de votre
Serveur NAT pour utiliser une forme de base de NAT
pour cette plage au lieu de NAPT (le processus réel varie considérablement entre les différents modèles de routeur.
Vérifiez la documentation de votre routeur et / ou forum de support. Vous trouverez également de nombreuses informations sur le
sujet à l'adresse PortForward a>).
J'ai perdu mon nom d'utilisateur ou mot de passe! Pouvez-vous me l'envoyer?
S'il vous plaît utilisez class=altlink ce formulaire a> pour avoir les informations de connexion vous recevrez un email.
Pouvez-vous supprimer mon compte?
Vous ne pouvez pas supprimer votre propre compte, vous devez demander demander à un membre du staff de la faire.
Alors, quel est mon ratio?
Cliquez sur votre profil a>, ensuite sur votre nom d'utilisateur (en haut).
Il est important de faire la distinction entre votre ratio global et le ratio individuel sur chaque torrent
vous pouvez être le seeder ou le leecher. Le ratio global prend en compte le total transféré et téléchargés à partir de votre compte. Le ratio individuel prend en compte ces valeurs pour chaque torrent.
Vous pouvez voir deux symboles au lieu d'un nombre: "Inf.", qui est juste une abréviation de Infini, et
signifie que vous avez téléchargé 0 bytes alors télécharger une quantité non nulle (ul / dl devient infini); "---",qui devrait se lire comme «non-disponible", et indique quand vous avez téléchargé et transféré 0 octets
(ul / dl = 0 / 0 qui est un montant indéterminé).
Pourquoi mon IP est affiché sur ma page de détails?
Seuls vous et les modérateurs du site peuvent afficher votre adresse IP. Les utilisateurs réguliers ne peuvent pas voir cette information.
Aidez moi! Je ne peux pas me connecter!?
Ce problème se produit parfois avec Microsoft Internet Explorer. Fermez toutes les fenêtres Internet Explorer et ouvrez Options Internet dans le panneau de contrôle. Cliquez sur le bouton Supprimer les cookies. Vous devriez maintenant être capable de se connecter.
Mon adresse IP est dynamique. Comment puis-je rester connecté?
Vous n'avez pas besoin de plus. Tout ce que vous avez à faire est de s'assurer que vous êtes connecté avec votre IP réelle lors du démarrage d'une session torrent. Après cela, même si votre IP change à mi- session, le seed ou le leech se poursuivra et les statistiques seront mises à jour sans aucun problème.
|
 |
|
 |
|
 |
 |
La raison la plus commune pour que les statistiques ne ce mettent pas à jour .
- L'utilisateur triche. (alias «Résumé Ban") li>
- Le serveur est surchargé et ne répond pas. Essayer de garder la session ouverte jusqu'à ce que le serveur réponde à nouveau. (Flooder le serveur avec mises à jour manuelles consécutifs n'est pas recommandée.) li>
ul>
Comment le NAT / ICS fonctionne t'il?
Il s'agit d'un cas très particulier où tous les ordinateurs du réseau local apparaissent au monde extérieur comme ayant la même adresse IP. Il faut distinguer
entre deux cas:
1. b> Vous êtes le seul utilisateur du réseau local i>
Vous devez utiliser le même compte sur tous les ordinateurs.
Notez également que dans le cas ICS il est préférable d'exécuter le client BITTORENT sur la passerelle ICS. Les clients tournant sur les autres ordinateurs ne seront pas connectable (leurs ports seront inscrits comme "---", comme il est expliqué ailleurs dans la FAQ) sauf si vous spécifiez
les services appropriés dans vos configurations ICS (une bonne explication de la façon de le faire pour Windows XP peut être trouvé
class=altlink ici a>).
Dans le cas du NAT vous devez configurer différentes gammes de clients sur différents ordinateurs et créer des règles appropriées pour le NAT du routeur. (Les détails varient considérablement d'un routeur à routeur et sont en dehors du champ d'application de cette FAQ. Vérifiez la documentation de votre routeur et / ou forum de support.)
2. b> Il y a plusieurs utilisateurs dans le réseau local i>
À l'heure actuelle il n'existe aucun moyen de faire fonctionner cette configuration toujours correctement.
Chaque torrent sera associé à l'utilisateur qui aura accédé au site à partir du réseau local avant que le torrent a été lancé.
A moins qu'il y ait coopération entre les utilisateurs des statistiques de mélange est possible.
(Un utilisateur accède au site, télécharge un fichier torrent., Mais ne démarre pas immédiatement le torrent.
Pendant ce temps, l'utilisateur accède à B le site. Un utilisateur lance son torrent. Le torrent comptera vers des statistiques de l'utilisateur B, et non l'utilisateur A.)
Il est de votre responsabilité la gestion de votre réseau local.
Ne nous demandez pas de bannir les utilisateurs d'autres réseau local,avec la même IP, nous ne le ferons pas. (Pourquoi doit-on bannir lui i> au lieu de vous i>?)
Les meilleures pratiques
- Si un torrent que vous êtes en train de leecher / seeder n'apparaît pas sur votre profil, il suffit d'attendre ou de forcer la mise à jour manuelle. li>
- Assurez-vous que vous quittez votre client correctement, de sorte à ce que le tracker reçoive «event = completed". li>
- Si le tracker est hors service, n'arrêtez pas de seeder. Attendre que le tracker redevienne opérationnelle est sauvegarder avant de quitter le client car il doit mettre à jour les stats correctement. li>
ul>
Puis-je utiliser n'importe quel client bittorrent?
Oui. Les Tracker font maintenant les mises à jour correctement ainsi que les statistiques pour tous les clients bittorrent. Toutefois, nous recommandons
que vous évitiez b> les clients suivants:
Pourquoi un torrent que je suis entrain de leecher / seeder est listé plusieurs fois dans mon profil?
Si pour une raison quelconque (par exemple le crash pc ou votre client) issues de votre client de façon inappropriée et que vous le redémarrez,il aura une nouvelle peer_id, alors il sera considéré comme un nouveau torrent. L'ancien ne recevra jamais un "event = completed"
ou "event = stopped" et seront admises jusqu'à un timeout.Il faut simplement l'ignorer, il finira par disparaître.
J'ai fini ou annulé un torrent. Pourquoi est-il toujours dans mon profil?
Certains clients, notamment TorrentStorm et Nova Torrent, ne préviennent pas correctement le tracker lors de l'annulation ou de la finition d'un torrent.
Dans ce cas le tracker attendra l'un des messages soit du seed ou du leech et donc la liste des torrents se remettront à jour à expiration du délai. Sinon l’ignorer, il finira par disparaître.
Pourquoi vois-je parfois des torrents que je ne suis pas entrain de leecher dans mon profil!?
Quand un torrent est démarré en premier, le tracker utilise l'IP pour identifier l'utilisateur. Par conséquent le torrent sera associer au dernier utilisateur qui aura accédé au site i> à partir de cette IP. Si vous partagez votre IP dans certains cas (vous êtes derrière un NAT / ICS, ou en utilisant un proxy), et quelques-unes des personnes que vous le partager avec les utilisateurs sont également,
Vous pouvez parfois voir leurs torrents listés dans votre profil. (Si elle démarre une session torrent à partir de cette IP et vous avez été le dernier à visiter le site, le torrent sera associé à vous). Notez que maintenant les torrents listés dans votre profil seront toujours pris en compte dans vos statistiques.
|
 |
|
 |
Pourquoi ne puis-je pas télécharger des torrents?
Seuls les utilisateurs disposant d'un compte sur le site ( Uploaders b> font>) ont la permission de télécharger des torrents.
Quels critères dois-je remplir avant de pouvoir rejoindre l’équipe des Uploader font>?
Vous devez savoir uploader des torrents en vous conformant aux règles de l’upload.
Et être capable d’uploader au moins 3 torrents par semaines.
|
 |
|
 |
|
 |
 |
Comment puis-je utiliser les fichiers que j'ai téléchargé?
Check out this guide.
Downloaded a movie and don't know what CAM/TS/TC/SCR means?
Check out this guide.
Why did an active torrent suddenly disappear?
There may be three reasons for this:
(1) The torrent may have been out-of-sync with the site
rules.
(2) The uploader may have deleted it because it was a bad release.
A replacement will probably be uploaded to take its place.
(3) Torrents are automatically deleted after 28 days.
How do I resume a broken download or reseed something?
Open the .torrent file. When your client asks you for a location, choose the location of the existing file(s) and it will resume/reseed the torrent.
Why do my downloads sometimes stall at 99%?
The more pieces you have, the harder it becomes to find peers who have pieces you are missing. That is why downloads sometimes slow down or even stall when there are just a few percent remaining. Just be patient and you will, sooner or later, get the remaining pieces.
What are these "a piece has failed an hash check" messages?
Bittorrent clients check the data they receive for integrity. When a piece fails this check it is
automatically re-downloaded. Occasional hash fails are a common occurrence, and you shouldn't worry.
Some clients have an (advanced) option/preference to 'kick/ban clients that send you bad data' or
similar. It should be turned on, since it makes sure that if a peer repeatedly sends you pieces that
fail the hash check it will be ignored in the future.
The torrent is supposed to be 100MB. How come I downloaded 120MB?
See the hash fails topic. If your client receives bad data it will have to redownload it, therefore
the total downloaded may be larger than the torrent size. Make sure the "kick/ban" option is turned on
to minimize the extra downloads.
Pourquoi dois-je obtenir un "Non autorisé (xx h) - LIRE LA FAQ" erreur?
From the time that each new torrent is uploaded to the tracker, there is a period of time that
some users must wait before they can download it.
This delay in downloading will only affect users with a low ratio, and users with low upload amounts.
| Ratio below |
0.50 |
|
and/or upload below |
5.0GB |
|
delay of |
48h |
| Ratio below |
0.65 |
|
and/or upload below |
6.5GB |
|
delay of |
24h |
| Ratio below |
0.80 |
|
and/or upload below |
8.0GB |
|
delay of |
12h |
| Ratio below |
0.95 |
|
and/or upload below |
9.5GB |
|
delay of |
06h |
"And/or" means any or both. Your delay will be the largest one for which you meet at least one condition.
This applies to new users as well, so opening a new account will not help. Note also that this
works at tracker level, you will be able to grab the .torrent file itself at any time.
N.B. Due to some users exploiting the 'no-delay-for-seeders' policy we had to change it. The delay
now applies to both seeding and leeching. So if you are subject to a delay and get the files from
some other source you will not be able to seed them until the delay has elapsed.
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.
This 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.
What's this "IOError - [Errno13] Permission denied" error?
If you just want to fix it reboot your computer, it should solve the problem.
Otherwise read on.
IOError means Input-Output Error, and that is a file system error, not a tracker one.
It shows up when your client is for some reason unable to open the partially downloaded
torrent files. The most common cause is two instances of the client to be running
simultaneously:
the last time the client was closed it somehow didn't really close but kept running in the
background, and is therefore still
locking the files, making it impossible for the new instance to open them.
A more uncommon occurrence is a corrupted FAT. A crash may result in corruption
that makes the partially downloaded files unreadable, and the error ensues. Running
scandisk should solve the problem. (Note that this may happen only if you're running
Windows 9x - which only support FAT - or NT/2000/XP with FAT formatted hard drives.
NTFS is much more robust and should never permit this problem.)
What's this "TTL" in the browse page?
The torrent's Time To Live, in hours. It means the torrent will be deleted
from the tracker after that many hours have elapsed (yes, even if it is still active).
Note that this a maximum value, the torrent may be deleted at any time if it's inactive.
|
 |
|
 |
How can I improve my download speed? - Top |
| |
|
 |
 |
Do not immediately jump on new torrents
The download speed mostly depends on the seeder-to-leecher ratio (SLR). Poor download speed is
mainly a problem with new and very popular torrents where the SLR is low.
(Proselytising sidenote: make sure you remember that you did not enjoy the low speed.
Seed so that others will not endure the same.)
There are a couple of things that you can try on your end to improve your speed:
In particular, do not do it if you have a slow connection. The best speeds will be found around the
half-life of a torrent, when the SLR will be at its highest. (The downside is that you will not be able to seed
so much. It's up to you to balance the pros and cons of this.)
Limit your upload speed
The upload speed affects the download speed in essentially two ways:
- Bittorrent peers tend to favour those other peers that upload to them. This means that if A and B
are leeching the same torrent and A is sending data to B at high speed then B will try to reciprocate.
So due to this effect high upload speeds lead to high download speeds.
- Due to the way TCP works, when A is downloading something from B it has to keep telling B that
it received the data sent to him. (These are called acknowledgements - ACKs -, a sort of "got it!" messages).
If A fails to do this then B will stop sending data and wait. If A is uploading at full speed there may be no
bandwidth left for the ACKs and they will be delayed. So due to this effect excessively high upload speeds lead
to low download speeds.
The full effect is a combination of the two. The upload should be kept as high as possible while allowing the
ACKs to get through without delay. A good thumb rule is keeping the upload at about 80% of the theoretical
upload speed. You will have to fine tune yours to find out what works best for you. (Remember that keeping the
upload high has the additional benefit of helping with your ratio.)
If you are running more than one instance of a client it is the overall upload speed that you must take into account.
Some clients (e.g. Azureus) limit global upload speed, others (e.g. Shad0w's) do it on a per torrent basis.
Know your client. The same applies if you are using your connection for anything else (e.g. browsing or ftp),
always think of the overall upload speed.
Limit the number of simultaneous connections
Some operating systems (like Windows 9x) do not deal well with a large number of connections, and may even crash.
Also some home routers (particularly when running NAT and/or firewall with stateful inspection services) tend to become
slow or crash when having to deal with too many connections. There are no fixed values for this, you may try 60 or 100
and experiment with the value. Note that these numbers are additive, if you have two instances of
a client running the numbers add up.
Limit the number of simultaneous uploads
Isn't this the same as above? No. Connections limit the number of peers your client is talking to and/or
downloading from. Uploads limit the number of peers your client is actually uploading to. The ideal number is
typically much lower than the number of connections, and highly dependent on your (physical) connection.
Just give it some time
As explained above peers favour other peers that upload to them. When you start leeching a new torrent you have
nothing to offer to other peers and they will tend to ignore you. This makes the starts slow, in particular if,
by change, the peers you are connected to include few or no seeders. The download speed should increase as soon
as you have some pieces to share.
Why is my browsing so slow while leeching?
Your download speed is always finite. If you are a peer in a fast torrent it will almost certainly saturate your
download bandwidth, and your browsing will suffer. At the moment there is no client that allows you to limit the
download speed, only the upload. You will have to use a third-party solution,
such as NetLimiter.
Browsing was used just as an example, the same would apply to gaming, IMing, etc...
|
 |
|
 |
My ISP uses a transparent proxy. What should I do? - Top |
| |
|
 |
 |
What is a proxy?
Basically a middleman. When you are browsing a site through a proxy your requests are sent to the proxy and the proxy
forwards them to the site instead of you connecting directly to the site. There are several classifications
(the terminology is far from standard):
| Transparent |
|
A transparent proxy is one that needs no configuration on the clients. It works by automatically redirecting all port 80 traffic to the proxy. (Sometimes used as synonymous for non-anonymous.) |
| Explicit/Voluntary |
|
Clients must configure their browsers to use them. |
| Anonymous |
|
The proxy sends no client identification to the server. (HTTP_X_FORWARDED_FOR header is not sent; the server does not see your IP.) |
| Highly Anonymous |
|
The proxy sends no client nor proxy identification to the server. (HTTP_X_FORWARDED_FOR, HTTP_VIA and HTTP_PROXY_CONNECTION headers are not sent; the server doesn't see your IP and doesn't even know you're using a proxy.) |
| Public |
|
(Self explanatory) |
A transparent proxy may or may not be anonymous, and there are several levels of anonymity.
How do I find out if I'm behind a (transparent/anonymous) proxy?
Try ProxyJudge. It lists the HTTP headers that the server where it is running
received from you. The relevant ones are HTTP_CLIENT_IP, HTTP_X_FORWARDED_FOR and REMOTE_ADDR.
Why is my port listed as "---" even though I'm not NAT/Firewalled?
The tracker is quite smart at finding your real IP, but it does need the proxy to send the HTTP header
HTTP_X_FORWARDED_FOR. If your ISP's proxy does not then what happens is that the tracker will interpret the proxy's IP
address as the client's IP address. So when you login and the tracker tries to connect to your client to see if you are
NAT/firewalled it will actually try to connect to the proxy on the port your client reports to be using for
incoming connections. Naturally the proxy will not be listening on that port, the connection will fail and the
tracker will think you are NAT/firewalled.
Can I bypass my ISP's proxy?
If your ISP only allows HTTP traffic through port 80 or blocks the usual proxy ports then you would need to use something
like socks and that is outside the scope of this FAQ.
Otherwise you may try the following:
- Choose any public non-anonymous proxy that does not use port 80
(e.g. from this,
this or
this list).
- Configure your computer to use that proxy. For Windows XP, do Start, Control Panel, Internet Options,
Connections, LAN Settings, Use a Proxy server, Advanced and type in the IP and port of your chosen
proxy. Or from Internet Explorer use Tools, Internet Options, ...
- (Facultative) Visit ProxyJudge. If you see an HTTP_X_FORWARDED_FOR in
the list followed by your IP then everything should be ok, otherwise choose another proxy and try again.
- Visit this site. Hopefully the tracker will now pickup your real IP (check your profile to make sure).
Notice that now you will be doing all your browsing through a public proxy, which are typically quite slow.
Communications between peers do not use port 80 so their speed will not be affected by this, and should be better than when
you were "unconnectable".
How do I make my bittorrent client use a proxy?
Just configure Windows XP as above. When you configure a proxy for Internet Explorer you
re actually configuring a proxy for
all HTTP traffic (thank Microsoft and their "IE as part of the OS policy" ). On the other hand if you use another
browser (Opera/Mozilla/Firefox) and configure a proxy there you'll be configuring a proxy just for that browser. We don't
know of any BT client that allows a proxy to be specified explicitly.
Why can't I signup from behind a proxy?
It is our policy not to allow new accounts to be opened from behind a proxy.
|
 |
|
 |
Why can't I connect? Is the site blocking me? - Top |
| |
|
 |
 |
Maybe my address is blacklisted?
The site blocks addresses listed in the (former) PeerGuardian
database, as well as addresses of banned users. This works at Apache/PHP level, it's just a script that
blocks logins from those addresses. It should not stop you from reaching the site. In particular
it does not block lower level protocols, you should be able to ping/traceroute the server even if your
address is blacklisted. If you cannot then the reason for the problem lies elsewhere.
If somehow your address is indeed blocked in the PG database do not contact us about it, it is not our
policy to open ad hoc exceptions. You should clear your IP with the database maintainers instead.
Your ISP blocks the site's address
(In first place, it's unlikely your ISP is doing so. DNS name resolution and/or network problems are the usual culprits.)
There's nothing we can do.
You should contact your ISP (or get a new one). Note that you can still visit the site via a proxy, follow the instructions
in the relevant section. In this case it doesn't matter if the proxy is anonymous or not, or which port it listens to.
Notice that you will always be listed as an "unconnectable" client because the tracker will be unable to
check that you're capable of accepting incoming connections.
|
 |
|
 |
What if I can't find the answer to my problem here? - Top |
| |
|
 |
 |
You can try these:
Post in the Forums, by all means. You'll find they
are usually a friendly and helpful place,
provided you follow a few basic guidelines:
- Make sure your problem is not really in this FAQ. There's no point in posting just to be sent
back here.
- Before posting read the sticky topics (the ones at the top). Many times new information that
still hasn't been incorporated in the FAQ can be found there.
- Help us in helping you. Do not just say "it doesn't work!". Provide details so that we don't
have to guess or waste time asking. What client do you use? What's your OS? What's your network setup? What's the exact
error message you get, if any? What are the torrents you are having problems with? The more
you tell the easiest it will be for us, and the more probable your post will get a reply.
- And needless to say: be polite. Demanding help rarely works, asking for it usually does
the trick.
|
 |
|
|
|
 |