Select port for Vuze

From VuzeWiki
(Redirected from Port is blacklisted)
Jump to: navigation, search


Which port should I use for Vuze?[edit]

Ports are just logical addresses inside your computer's TCP/IP networking functionality. From technological perspective there is no difference between ports, so you can select any port which is not already used by something else and then you need to configure your firewall and router accordingly.

  1. Vuze needs only one port for the main data transfer functionality. Choose a port from the 49160–65534 range. If you really need to choose a port within the range 1024–49151 make sure you pick an "unassigned" port listed at the IANA port list and which is not already in use by some other application in your computer.
    • Go to Options > Connection and input the new TCP and UDP listening port that you have chosen.
    • Save the changed options.
  2. Go into your software firewall configuration and make sure that Vuze is allowed outgoing and incoming connections (and if there is such an option, enable Vuze to act as a server). Possibly the firewall is only configured for applications, but it might also require port-specific configuration.
  3. Go into your router configuration, if any, and forward the port you have chosen using the methods as described in NAT problem and Port forwarding. Remember to forward that port not only for TCP but also for UDP protocol, DHT needs that! (If your router is using UPnP, it should update automatically.

Note: When using a port above 49152, you always run to a risk that some other program has randomly grabbed that port before you start Vuze. For example, with Vista and Windows7 the operating system itself usually grabs ports 49152-49158 at boot, so you can't use those ports. For Windows 8.1, the operating system seems to grab ports throughout the entire numerical range.

In Windows environment, you can check which ports are currently in use (already reserved by some program) from CMD commandline prompt with the command NETSTAT -A . Or use the command NETSTAT -A > FILE. This will produce a text file of the results, saved in the directory from which the command prompt is operating. The text file might be much more convenient to use, as without it, the screen results may just scroll by.

Select randomly some port number, which is not shown in the list. The command should output the currently used ports with results like:

C:\Users\myusername>netstat -a
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 P35HN:0 LISTENING
TCP 0.0.0.0:445 P35HN:0 LISTENING
TCP 0.0.0.0:5357 P35HN:0 LISTENING
TCP 0.0.0.0:12110 P35HN:0 LISTENING
TCP 0.0.0.0:49152 P35HN:0 LISTENING

So, lots of free ports to choose from as only a few ports are already taken...

Once again, the NETSTAT -A command shows ports that you can't use. Select randomly a port, which is not shown in the list.

Which ports does Vuze use by default?[edit]

When you first install Vuze, it selects the "main port" for torrent downloading/uploding usage by random. As described previously, you can change that to something else if you like.

Vuze also uses some ports for internal use and/or as defaults for some functionality:

  • 1900 UDP: Used for UPnP?
  • 6880 TCP: Vuze uses this port for internal communication. When you launch Vuze, it always checks that port for an older instance of Vuze being already active. If there is an active Vuze, then the new Vuze instance passes the possible torrent name as parameter to the old instance already running and then dies. (This happens e.g. when you click a "download torrent" link on a web page. A new second Vuze instance gets launched by the browser, but it dies after passing the argument to the old Vuze.) If there was no active old Vuze, then the new Vuze reserves that TCP port and starts "listening" there.
  • 6969 TCP: If you enable internal HTTP tracker, this is the default port used. You need to port-forward this port in router for full connectivity.
  • 7000 TCP: Default port for HTTPS tracker. (usually not in use)
  • 16680 UDP: Used for the 'LAN peer finder' functionality.
  • 45100 TCP: Used for magnet URI handling.
  • 49001 UDP: Used for Mainline DHT (if that plugin is installed). You need to port-forward this port in router for full connectivity.

Why are ports blocked/blacklisted and what can I do about it?[edit]

ISPs have been increasingly reducing the available bandwidth for P2P users on the standard file-sharing port ranges. You may find you need to keep changing your port on a regular basis. This is normal, and a port change should sort you out if this is indeed what is happening. And please keep in mind that after any port change, and stopping and restarting any torrent, it may take up to half an hour or more for the benefits to become noticeable. So please try not to panic when things do not improve immediately. This is normal. :)

If you suspect that your ISP is blocking/throttling bittorrent traffic, you might check the Bad ISPs list and consider ways to avoid traffic shaping e.g. by encryption.

Why is port 6881 (or whatever) blocked/blacklisted?[edit]

To avoid a decreasing Average Swarm Speed, some tracker administrators are banning these often throttled standard ports. This includes the standard port range of 6881–6999, which ports were used by the "original" Bittorrent client program a few years ago.

So what happens is, those trackers reject connections from bittorrent clients who are listening on any of the ports within those ranges, and some of those trackers may blacklist those IPs for 48 hours. So the torrents will show red health smileysKo.gif, and even if you change your listening port, you are unable to connect because of the 48 hour ban. This kind of ban will often be reported under the "Tracker Status" of a torrent in its Details screen, with the blacklisted information.

The same goes for ISPs, who recognize the port 6881 to be used mostly for bittorrent traffic, and it might be the first port to be blocked if the ISP starts to block/throttle/shape bittorrent traffic. If you mostly receive blue health smileysNo tracker.gif, you might suspect that to be the reason.

The best advice is to never use ports from the range 6881-6999.

So what can I do about it if I'm already blacklisted?[edit]

  1. Choose a new TCP listening port for Vuze. The best range to choose a new port from is: 49160–65534 If you really need to choose a port within the range 1024–49151 make sure you pick an "unassigned" port listed at the IANA port list. Remember that Vuze needs one listening port only, so please choose one port from the above range.
    • Go to Options > Connection and input the new TCP and UDP listening port that you have chosen.
    • Click "Save" at the bottom left side of the screen.
  2. Go into your router and/or firewall, if any, and forward the port you have chosen using the methods as described in Port forwarding and NAT problem. Remember to forward that port not only for TCP but also for UDP protocol, DHT needs that! (If your router is using UPnP, it should update automatically.) The "Port xxxx is blacklisted" message from the tracker should disappear and the torrent will start. If not, check your router and firewall, then go on to step 5.
  3. Stop all your actively running torrents. (This is temporary, just until you get the port sorted out. Vuze will remember all the peers you were connected to when you start the torrents up again, even if the tracker is offline. No need to panic. Please ring a friend if you need any extra support during this trying experience.) :-)
  4. Quit Vuze.
  5. Wait a few minutes.
  6. Run Vuze
  7. Go to Help -> NAT/Firewall Test and do the port test. You will see a port tester with your selected port entered in it by default. Change the port number, if necessary, and click "test". You will then get any one of three results from this:
    1. "This port can not be tested because it is already in use" If you get this message, repeat steps 4–8
    2. "NAT Error" If you get this message, please see the Port forwarding and NAT problem pages.
    3. "OK!" If you get this message, then you have just done everything right, all is groovy, and the world should appear a much rosier place to live in. :-)



Read the Azureus FAQ