You can use this form to delete the account so you can re-register. Note though that if you didn't receive the email the first time it will probably not succeed the second time either so you should really try another email address.

Please use this form to have the login details mailed back to you.

We do not rename accounts. Please create a new one. (Use this form to delete your present account.)

You can do it yourself by using this form.

Click on your profile, then on your user name (at the top).

It's important to distinguish between your overall ratio and the individual ratio on each torrent you may be seeding or leeching. The overall ratio takes into account the total uploaded and downloaded from your account since you joined the site. The individual ratio takes into account those values for each torrent.

You may see two symbols instead of a number: "Inf.", which is just an abbreviation for Infinity, and means that you have downloaded 0 bytes while uploading a non-zero amount (ul/dl becomes infinity); "---", which should be read as "non-available", and shows up when you have both downloaded and uploaded 0 bytes (ul/dl = 0/0 which is an indeterminate amount).

Only you and the site moderators can view your IP address and email. Regular users do not see that information.

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.

You do not have to anymore. All you have to do is make sure you are logged in with your actual IP when starting a torrent session. After that, even if the IP changes mid-session, the seeding or leeching will continue and the statistics will update without any problem.

The tracker has determined that you are firewalled or NATed and cannot accept incoming connections.

This means that other peers in the swarm will be unable to connect to you, only you to them. Even worse, if two peers are both in this state they will not be able to connect at all. This has obviously a detrimental effect on the overall speed.

The way to solve the problem involves opening the ports used for incoming connections (the same range you defined in your client) on the firewall and/or configuring your NAT server to use a basic form of NAT for that range instead of NAPT (the actual process differs widely between different router models. Check your router documentation and/or support forum. You will also find lots of information on the subject at PortForward).

Peasant		Those With A Very Poor Ratio.
User		Default Class For New Members.
Power_User		A step Above User Good Seeder And they are moving up.
		Has donated money to Mega-Bits .
P2P_VIP		Is A Personal Friend of Mega-Bits Immune to automatic ban.
DONATOR_VIP		Has Donated To Mega-Bits And Has 30 Days Immunity From Hit And Run Warnings And Immune to automatic ban.
Uploader		A Valued Member Who Knows How To Upload.
Supe_Uploader		Is The Cream of The Crop Is Constantly Delivering Quantity And Quality Torrents.
Forum Moderator		Moderates The Forums.
Moderator		Moderates The Site And Torrents.
Administrator		Administers The site And Is In Charge Of Uploaders.
Sysops		Monitors Site Operation And Is In Charge Of Super uploaders.
Gods		Monitors Everyone Below Them.
Coders		Can Do Anything They Want And We Never Sleep

First, find an image that you like, and that is within the rules. Then you will have to find a place to host it, popular choices are Photobucket, Upload-It! or ImageShack. All that is left to do is copy the URL you were given when uploading it to the avatar field in your profile.

Please do not make a post just to test your avatar. If everything is allright you'll see it in your details page.

• 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.)
• You are using a faulty client. If you want to use an experimental or CVS version you do it at your own risk.

• 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.

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.

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.

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.

When a torrent is first started, the tracker uses the IP to identify the user. Therefore the torrent will become associated with the user who last accessed the site from that IP. If you share your IP in some way (you are behind NAT/ICS, or using a proxy), and some of the persons you share it with are also users, you may occasionally see their torrents listed in your profile. (If they start a torrent session from that IP and you were the last one to visit the site the torrent will be associated with you). Note that now torrents listed in your profile will always count towards your total stats.

To make sure your torrents show up in your profile you should visit the site immediately before starting a session.

(The only way to completely stop foreign torrents from showing in profiles is to forbid users without an individual IP from accessing the site. Yes, that means you. Complain at your own risk.)

Yes, the tracker is now capable of following sessions from different IPs for the same user. A torrent is associated with the user when it starts, and only at that moment is the IP relevant. So if you want to seed/leech from computer A and computer B with the same account you should access the site from computer A, start the torrent there, and then repeat both steps from computer B (not limited to two computers or to a single torrent on each, this is just the simplest example). You do not need to login again when closing the torrent.

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 TorrentBits users in the LAN

You should use the same TorrentBits 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 TorrentBits users in the LAN

At present there is no way of making this setup always work properly with TorrentBits. 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?)

You only may upload torrents when you have uploaded atleast 20GB or there are to many torrents uploaded in one day, then you will have to wait until the next day

When you upload a torrent please give some information about that release. The folowing information is required:

VIDEO:	RE-ENCODED / UNTOUCHED
MENU:	RE-ENCODED / UNTOUCHED / STRIPPED
EXTRAS:	RE-ENCODED / UNTOUCHED / STRIPPED
APSECT REGIONS:	16:9 / 4:3
AUDIO:	2.0 DD / 5.1 DD / 6.1 DTS
AUDIO LANGUAGES:	ENGLISH / GERMAN / FRENCH / SPANISH / JAPANESE / ETC
SUBTITELS:	ENGLISH / GERMAN / FRENCH / SPANISH / JAPANESE / ETC
OPTIONAL
COMPRESSION:	CCE / DVDSHRINK / RE-ENCODE / DVD2ONE / ETC
COMPRESSION RATE:	BITRATE / COMPRESSION in % / ETC

1. First you need a DVD movie which you can share. Note that the movie can't be bigger than 4.3GB. If you want to compress the movie you can read alot of tutorials on Doom9.org.
2. Put the movie in a directory which as the movie name, for example X:\Big_Fish or X:\Big_Fish\VIDEO_TS.
3. Download MakeTorrent (its free}, install and run it. Browse to your files and select the files in the directory (from step 2), put this adress in the tracker window: http://www.mega-bits.com/announce.php and press create torrent. Save the torrent on your HDD.
4. Now you can upload the torrent to the site, click upload in the top of the screen and fill in all the release info.
5. When the torrent is uploaded download the torrent and open it with your bittorrent client, go to the directory where the DVD is stored (step 2). If everything is oke it will check your data first (for a few minutes) and says download completed, which means you are now seeding.

No. We are a closed, limited-membership community. Only registered users can use the this tracker. Posting our torrents on other trackers or sites is useless, since most people who attempt to download them will be unable to connect with us. This generates a lot of frustration and bad-will against us at DVDr-Core, and will therefore not be tolerated.

Complaints from other sites' administrative staff about our torrents being posted on their sites will result in the banning of the users responsible.

(However, the files you download from us are yours to do as you please. You can always create another torrent, pointing to some other tracker, and upload it to the site of your choice.)

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 when they are seedless for a while.

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.

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.

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.

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.

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.
Look at the rules for how long you will have to wait

This connection limit is build in so people who don not have high upload speeds or do not download much can not open alot torrents in one time.
This limitation will only affect users with a low ratio, and users with low upload amounts.
Look at the rules for how to improve this limitation

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.

TorrentBits 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

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 is my port listed as "---"  section and links therein for more information on this.

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.)

Often you will get a red error message when there's a problem connecting to the tracker, but the client will keep on retrying. The newer versions of the experimental client "age away" the error messages after 5 minutes to deal with this situation.

Problem getting response info - [Errno 2] No such file or directory: "C:\\Documents and Sett..."

For some reason, Internet Explorer sometimes doesn't save the torrent file in the Temporary Internet Files directory properly. The solution seems to be to right click on the link and choose Save As..., and save the torrent file to disk, and then double-click the file to launch the client.

Too many args - 0 max

This error in indicative of a bad command line. See this site for arguments you can use: BTfaq.com

A piece failed hash check, re-downloading it

This is a benign message, you can safely ignore it. It means that you received a piece of the file that didn't check out as being correct, so it will be downloaded again. Probable cause of this might be someone incorrectly using the "skip hash check" option. If this option is incorrectly used on a not-yet complete file, the client will send pieces to its peers that are not correct and fail the built-in hash checking routines meant to catch such errors

- bad data from tracker -

Usually you can ignore this, it seems to happen when the tracker is overloaded or otherwise flaky

Problem connecting to tracker - timeout exceeded

There was a problem contacting the tracker. Trackers tend to be heavily loaded, and connections sometimes fail. The best thing to do is just be patient and leave the client open.

Problem connecting to tracker - HTTP Error 503: Connect failed

There was a problem contacting the tracker. Trackers tend to be heavily loaded, and connections sometimes fail. The best thing to do is just be patient and leave the client open.

Problem connecting to tracker - [Errno socket error] (10061, "Connection refused")

There was a problem contacting the tracker. Trackers tend to be heavily loaded, and connections sometimes fail. The best thing to do is just be patient and leave the client open.

Problem connecting to tracker - (111, 'Connection refused')

There was a problem contacting the tracker. Trackers tend to be heavily loaded, and connections sometimes fail. The best thing to do is just be patient and leave the client open.

Problem connecting to tracker - HTTP Error 400: Not Authorized

This indicates that the administrators of this tracker are not allowing it to be used for this torrent. Some trackers will only track torrents that are also posted in their forums/website, for example. Usually this indicates a stale torrent -- try going to the web site associated with the tracker and see if you can find an updated torrent.

Problem connecting to tracker - HTTP Error 404: Not Found

Probably a stale torrent. Try to find a new link to the torrent.

Problem connecting to tracker - HTTP Error 407: Proxy Authentication Required

You may need to configure a username and password for your proxy server setting in order to contact the tracker.

torrent not registered with this tracker

Torrent does not excist on this tracker. Could be deleted or removed.

invalid port

Client tries to connect thru a port that isn't right. Set your port range wider or higher.

Unrecognized host (IP). Please go to URL to sign-up or login.

Your are not logt in to the site and the tracker can't find your account. Login and retry the torrent.

Not authorized (Xh) - READ THE RULES!

This is the time-ban taking effect. Read above how it works and read the rules to see how long you will have to wait

Not authorized - You may only connect to X torrent - READ THE RULES!

This is the connection restriction taking effect. Read above how it works and read the rules to see how long you will have to wait

Peer not found. Restart the torrent.

The tracker can not see if the torrent is started correctly. Restart your torrent.

Port XXX is blacklisted.

Some ports are banned to use with the tracker. See in this FAQ which ports are blacklisted. Widen your port range in your client.

Tracker error 2

The tracker as an mailfunction. Contact the site administrator to see if he can fix it

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.)

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.)

See the Why is my port listed as "---"  section.

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.

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.

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.

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.

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...