Torrent health
Health[edit]
Each torrent gets assigned a health status showing its status using colors. The health reflects the connection status of that torrent. Typically, all your torrents will have the same status after a while, but that may depend on the swarm size etc. The important part is that the "best" status you reach tells you most about the correctness of your network settings. The goal is to reach green health 
.
The "smiley" icon can be seen e.g. in Library, in My torrents, in torrent details etc. If you do not have the smiley visible by default, you can add the Health column to the table by using Column setup.
My Library view in Vuze interface:
The explanations for different colors shown for the smileys can be found through "About Health" command in Help menu:
If you get light/dark red error smileys, you should check the torrent's details for possible error messages, which might help you in solving the possible problem.
| Health | What Azureus says | Side effects | How to fix | Notes |
|---|---|---|---|---|
| Grey
| The torrent is not running. It is either "queued" or "stopped" | No upload or download for that torrent | See: Torrents queued | Don't try to run more torrents than your bandwidth can cater for. See Good settings |
| Red
| You are not connected to any other peers or seeds | No upload or download for that torrent | See Red Health and also check the torrent details for possible error messages (See below) | None |
| Blue
| While downloading, this means the tracker is down. While uploading, it means you are not connected to any peers | Slow downloads / No upload | There is little you can do if the tracker is down.
| None |
| Yellow
| This means you are connecting to some peers/seeds. However, if torrents are always yellow (as opposed to green), you may have a NAT problem which is stopping you from getting 'Remote' connections. | Slow downloads | See: Port forwarding | Your ISP may also be blocking:
|
| Green
| This means you have both local and remote connections, the tracker is up and life is good. | None | No need as the torrent is fine. Yay! | None |
| Dark red
| Something is seriously wrong with the torrent. Vuze can't keep it active. | No download or upload | Check the error messages. (See below) | None |
Note: Some small torrents will never attain green status, simply because there are no remote connections to connect to. For example, if there is only one active peer in addition to you, and you manage to connect to him first, then there is nobody to contact you, and the status will remain yellow.
Note: If you have more than one network interface, make sure that you have forwarded the one interface that Vuze uses as the primary interface. You might need to use the "Bind to local ip address or interface" option in the Advanced Network Settings options (visible to Advanced users).
Possible errors[edit]
Invalid passkey[edit]
One of the most typical errors you may receive is that of "Invalid passkey" or "Unauthorized torrent". You may receive them, if you try to use such .torrent files, which use a private tracker. If you have not received the .torrent file directly from the private tracker web site, it is possible that the private tracker will reject your connection attempt as it is not your personalised copy of that torrent. (The torrent has been created for somebody else, who has then shared it with you either directly or by uploading it to an index site where you have then found it.)
Data missing[edit]
You have maybe moved files outside Vuze, or transferred existing settings to a new computer, or something like that. In any case, Vuze does not find the torrent's data files where it expects.
It gives you angry dark red health icon and the Error message in "Error: Data Missing <directory name>". Vuze should offer you the option to "Change Data Directory" in the torrent's context menu. Use it to point the torrent to the correct place for the data files.
Invalid port[edit]
If the tracker status of a torrent is "error (invalid port)" then you need to go to Tools > Options > Connection > Proxy options and uncheck "inform tracker of limitation". This may only happen when the proxy is enabled?
It has been reported that turning on Cryptoport may also cause this error. Try going to Tools > Options > Connection > Transport Encryption and uncheck 'Use the "cryptoport" tracker extension to prevent plain incoming connection attempts. Some tracker don't accept this and fail with errors such as "Invalid Port" or "Illegal Argument"'.
Some private trackers expect to hear the listening port announcement. Try going to Tools > Options > Tracker > Client and uncheck 'Do not announce the listening port to the tracker (this does not affect pex, dht)'.
-
-
-