 |
Login |
|
|
|
|
CONTENTS |
|
|
|
Site information - Top |
|
|
|
User information - Top |
|
|
I've lost my user name or password! Can you send it to me?
Please use this form to have the login details mailed back to you.
Can you delete my account?
You cannot delete your own account, please ask a member of staff
Why is my IP displayed on my details page?
Only you and the site moderators can view your IP address and email. Regular users do not see that information.
Help! I cannot login!?
This problem sometimes occurs with MSIE. Close all Internet Explorer windows and open Internet Options in the control panel. Click the Delete Cookies button. You should now be able to login.
|
|
|
|
Most common reason for stats not updating
- The user is cheating. (a.k.a. "Summary Ban")
- The server is overloaded and unresponsive. Just try to keep the session open until the server responds again. (Flooding the server with consecutive manual updates is not recommended.)
How does NAT/ICS change the picture?
This is a very particular case in that all computers in the LAN will appear to the outside world as having the same IP. We must distinguish
between two cases:
1. You are the single user in the LAN
You should use the same account in all the computers.
Note also that in the ICS case it is preferable to run the BT client on the ICS gateway. Clients running on the other computers
will be unconnectable (their ports will be listed as "---", as explained elsewhere in the FAQ) unless you specify
the appropriate services in your ICS configuration (a good explanation of how to do this for Windows XP can be found
here).
In the NAT case you should configure different ranges for clients on different computers and create appropriate NAT rules in the router. (Details vary widely from router to router and are outside the scope of this FAQ. Check your router documentation and/or support forum.)
2. There are multiple users in the LAN
At present there is no way of making this setup always work properly.
Each torrent will be associated with the user who last accessed the site from within
the LAN before the torrent was started.
Unless there is cooperation between the users mixing of statistics is possible.
(User A accesses the site, downloads a .torrent file, but does not start the torrent immediately.
Meanwhile, user B accesses the site. User A then starts the torrent. The torrent will count
towards user B's statistics, not user A's.)
It is your LAN, the responsibility is yours. Do not ask us to ban other users
with the same IP, we will not do that. (Why should we ban him instead of you?)
Best practices
- If a torrent you are currently leeching/seeding is not listed on your profile, just wait or force a manual update.
- Make sure you exit your client properly, so that the tracker receives "event=completed".
- If the tracker is down, do not stop seeding. As long as the tracker is back up before you exit the client the stats should update properly.
May I use any bittorrent client?
Yes. The tracker now updates the stats correctly for all bittorrent clients. However, we still recommend
that you avoid the following clients:
?BitTorrent++,
?Nova Torrent,
?TorrentStorm.
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.
Why is a torrent I'm leeching/seeding listed several times in my profile?
If for some reason (e.g. pc crash, or frozen client) your client exits improperly and you restart it,
it will have a new peer_id, so it will show as a new torrent. The old one will never receive a "event=completed"
or "event=stopped" and will be listed until some tracker timeout. Just ignore it, it will eventually go away.
I've finished or cancelled a torrent. Why is it still listed in my profile?
Some clients, notably TorrentStorm and Nova Torrent, do not report properly to the tracker when canceling or finishing a torrent.
In that case the tracker will keep waiting for some message - and thus listing the torrent as seeding or leeching - until some
timeout occurs. Just ignore it, it will eventually go away.
|
|
|
|
Uploading - Top |
|
|
|
Downloading - Top |
|
|
How do I use the files I've downloaded?
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.
Why do I get a "Not authorized (xx h) - READ THE FAQ" error?
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 |
|
|
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 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.
|
|
|
|
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.
|
|
|
|
|
ADDTHIS |
|
|
|
