I have not seen that here so i give to you:

TABLE OF ERROR:

1. Problem connecting to tracker – url open error (10060, operation timed out)
2. Error - rejected by tracker - torrent not registered with this tracker
3. Piece (numer) failed hash check, re - downloading it
4. Error connecting to peers/seeds
5. Error [nazwa pliku] bad data from tracker
6. IO Error [Errno 13] Permission Denied
7. Rejected by tracker. Sorry, but this tracker has been locked. No new torrents allowed.
8. Problem connecting to tracker (7, 'getaddrinfo failed')
9. ERROR (11:35) - IO Error: [Errno 28] No space left on device
10. Problem connecting to tracker - HTTP Error 503: Service Unavailable
11. Error: Couldn't listen - (10048,'Adress already in use')
12. Maximum connection reached
13. Bad file descriptor
14. Download corrupted
15. ERROR: rejected by tracker. Client version is banned. Check with the tracker administrator.
16. ERROR: rejected by tracker: Your client does not support the compact tracker protocol
17. Offline (Connection limit exceeded! You may only leech from one location/ client at time
18. Offline (invalid repley: [2003]) dbcann: mysql connect Can't connect to MySQL
19. Offline (invalid info_hash (numer))
20. Offline FileNotFound
21. Rejected by tracker - This tracker requires new tracker protocol. Please check your client for updates. Latest Generic, uTorrent or Azureus client recommended.
22. Offline (unrecognized host (Twoje IP)) Please go to http://nazwastrony to sign up or login.23.reject by tracker - port 6881 is blacklisted24.Error :invalid passkey(numer passkey)
25. Invalid Peer_Id (0-)26. HTTP ERROR 40327. ERROR 12150

1.Problem connecting to tracker - url open error (10060, operation timed out)
Literally: An error occurred while connected to the tracker. The operation was ended, because of too long waiting time.

It means that the tracker is temporarily unavailable, please wait quietly. Clients will restore the connection until the tracker is not responding and then starts a client connects to the tracker again.

This error can have two different applications:



When downloading the file - then you can safely ignore this error is harmless. When we are already connected to the tracker and this error pops up, nothing happens, we are more connected, more phones, we see further seed `s and` s peer. Best we can not see the new peer'ów.

During start downloading when you just turned on the. Torrent - in this case do not give advice to connect to the tracker. Best left alone, and let the client attempts to connect to, at some point he should go, and then start downloading.

While the error occurred will continue to contact the administration of the tracker or ISP.

2.Error - rejected by tracker - torrent not registered with this tracker

or

Offline (Requested download is not authorized for use with this tracker)

Literally: Error - rejected by tracker - torrent not registered with this tracker. (The torrent does not exist on the page)

Some trackers work only for registered on this tracker. Torrents. Another did not take. If such a thing pops up, you have to redo. Torrent and give him another tracker. Another way to register. Torrent on the tracker. Currently, almost all trackers require registration.Is also possible that the torrent is removed from the site.

3. Piece (numer) failed hash check, re - downloading it
Literally: The part of the file (s) (number) was taken ill - the resumption of the download.

You can then stop the download, turn on again - the program starts downloading from the time from when the error occurred. Or, pull on, after downloading the rest of the program itself will download the damaged part, so do not be surprised if the downloading for example, 120 mega, and the file is 100 megs.

In fact, downloading this its 100 megs (or as much as you had to download) and the program will show mega-np 120. And that's because in those 20 mega several parts will be bad. The program brought bad part, but rejected them, so if you downloaded the counter will inflate.

4.Error connecting to peers / seeds

Literally: Error connecting to peers `s /` s seed.

Unable to connect with people who attract / provide the file. In this case, it is impossible to remedy this, it does not depend on us. The only way is to wait quietly.


5.Error [file name] Bad data from tracker

Literally: Tracker has sent bad information about the file is downloaded.

The information from the tracker for parts, seeds or peers `s` s were incorrectly sent to the client, which displays the error. The download can be continued, the error will disappear when the problem will disappear with ill sent data. You can also disable the client and try again.

6.IO Error [Errno 13] Permission Denied

Literally: Access denied.

If you want to fix it reboot your computer, it should solve the problem. If not - read on ...IOError means Input-Output Error, and it is a file system error, not a tracker \ a. It shows up when your client is for some reason does not have write access to files downloaded torrent. The most common reason for this is that while you have included 2 copies of the client simultaneously. A more uncommon occurrence is a corrupted FAT. A crash may damage the boards allokacji files, which in turn causes the data you downloaded are unsuitable for reading. In this case, run Scandisk \ and it should solve the problem

7.Rejected to tracker. Sorry, but this tracker has been locked. No new torrents allowed.

Literally: Tracker blocked, no access to. Torrents.

Error pops up when the tracker is turned off for some time. You can not releasować new torrents, all made to stop responding. A similar case was Torrent.org.pl page, for a time when the party did not work, and the tracker has been disabled.

8.Problem connecting to tracker (7, 'getaddrinfo failed')

Literally: Problem connecting to tracker.

Probably no connection to the Internet (firewall, turned off the modem). Make sure you have an Internet connection included.

9.ERROR (11:35) - IO Error: [Errno 28] No space left on device

Literally: Not available disk space

Error caused by incorrect file system. Using FAT32 it should be remembered that the size of a single file can be up to 4 GB. To cancel this problem should apply to NTFS

10.Problem connecting to tracker - HTTP Error 503: Service Unavailable

Literally: Problem connection to tracker - service unavailable.

Server service is temporarily unavailable due to what may be his arrest or overcharging.Please wait, or to connect again after some time.

11.Error: Could not listen - (10048, 'Address already in use')

Literally: You can not listen - Address in use

The same torrent is neglected and wants to use the same ports, or port range is narrowed so that the second torrent can not use them.

12.Maximum connection reached

Literally: Got too many links

Caused by too many processes allowed on a given tracker - check the number of slots which have the your rank. Sometimes the tracker "remembers" the old

Torrent - try to clear the ghosts / kill torrents when the tracker makes it possible for the profile.

13.Bad file descriptor

Literally: Bad saved file

Error pops up when a client at work or just reboot the computer hangs. Probably the wrong program ended a file to save the downloaded parts. In this case, if the error does not want to pass enough disk scandisc'iem FOR IN scan and remove what it detects an error in the file / files. Then activate the download from scratch.

14.Download corrupted

Literally: The download stopped due to system error.

This error occurs in two situations:

when you have damaged RAM - BitTorrent is very sensitive to bad RAM `u. On the program is Memtest86+ - Advanced Memory Diagnostic Tool - Memtest - to check memory. Errors of memory modules can also produce other errors

bad or non-standard library. dll - difficult to identify and irreparable

15.ERROR: rejected by tracker. Client Version is banned. Check with the tracker administrator.

Literally: Rejected by tracker. Customer banned.

Too old version of client you are using may not be taken by some trackers. Just change to a newer version and if does not help, move to an alternative version of the client.

16.ERROR: rejected by tracker: Your client does not support the compact tracker protocol

Literally: Rejected by tracker. Your client does not support the tracker protocol

An error occurs, like the above, if you have too old version. Then the client may not be able to handle the (new) protocol tracker. Should be changed to a later version, or try a completely different customer

17.offline (Connection limit exceeded! You May only leech from one location / client at time

Literally: connections limit exceeded. You can only use one space / client at a time.

Already exceeded the limit of active connections - this is a protection against leecherami who download a few dozen items at any one time, I can not handle the constraints are given by the tracker.

This error sometimes appears when you run several consecutive BT customers

18.Offline (repley invalid: [2003]) dbcann: mysql connect Can not connect to MySQL

Literally: Incorrect answer. Unable to connect to a MySQL database. Your client does not support the tracker protocol.

Transient error in MySQL. This happens when the admin (torrent sites with registration) plays database `em or code at a time when there is in you refresh the results. Then there w / in error.

19.Offline (invalid info_hash (number))

Literally: Invalid hash information

Probably the file was downloaded faulty, or studded with someone else share ratio.User hash / key is not yours.


20.Offline FileNotFound

Literally: Damaged, File not found.

This message can be seen after downloading torrent files (when the torrent has been downloaded and is now released) and the shared files were deleted or moved.


21.Rejected by tracker - This tracker requires new tracker protocol. Please check your client for updates. Latest Generic uTorrent or Azureus client recommended.

Literally: Rejected by tracker. Check for newer versions of your client. Recommended clients are uTorrent or Azureus.

Your client version is too old and has a very old protocol to connect to the tracker. You have to use another program to download files, I would recommend uTorrent or Azureus it.

22.Offline (unrecognized host (Your IP)) Please go to this http://nazwastrony sign up or login.

Literally: Unrecognized host. Go to (address) and sign in or create an account.

The problem applies to pages where you have to register to start downloading. When this error pops up it should be put out torrent, then visit a page that is specified in the address, or http://nazwastrony - enter by typing the exact address and log in to your account. After these steps, turn torrent again and start the download. Of course, if someone does not have an account on the site must register.

23.reject by tracker - Port 6881 is blacklisted

Literally: Rejected by tracker - Port 6881 is blacklisted

Your client is reporting this error because you are using for incoming calls one of the default bittorrent ports (6881-6889) or a different default port used by the popular P2P programs. BtGigs.org not allow clients to use ports commonly associated with p2p protocols. The reason is the Internet Service Providers (ISPs) block the ports which in practice has significant effects on reducing the bandwidth, access to pages, etc.

Change the settings for different listening port eg 7012

24.Error: invalid passkey (passkey number)

Literally: wrong passkey.

It means the torrent file is saved wrong passkey to get rid of this error, download the file from the torrent again and start again or resume the file download download the new torrent file. If the error shows up when you insert a file on the page, it means that probably what started seeding the torrent file you inserted in the created and inserted on the page and not the part to get rid of the error remove the task from the client download from the torrent file and its start seeding. You can also try to reset the passkey if this option allows the tracker (in profile).

25th Invalid Peer_Id (0 -)

Literally: Incorrect ID_peera

Causes for this error may be a lot - most often this error tracker / client due to overcharging.

In most cases, helps to:
1st Restart the client and download torrents of new
2nd Deleting temporary files (temp), cookies, etc. (I recommend CCleaner)
3rd Computer Restarting the computer
4th Change Passkey
5th reset your modem / router

26th HTTP ERROR 403

Literally: HTTP Protocol Error number 403

Page does not work / server crashed. If this is not the cause of this usually means only one thing - our IP was blocked on the page. If you have no reason to believe that this happened - it is worth sontaktować to administer our website.

If nothing helps you give up - ask your crew tracker or try to reinstall the system (helped some).

27th ERROR 12150

Many people have this problem - the solution is simple do not download torrents with SSL / HTTPS. Cause problems (especially as someone has a shell). The shift in the profile to plain tracker or unchecking SSL and download torrents from scratch will solve the problem. If, however, insist on the SSL you need to contact the crew to explain the causes of the error.

based on the source text by zaq