- 1 Release 184.108.40.206 Issues
- 2 Release 220.127.116.11 Issues
- 3 Release 18.104.22.168 Issues
- 4 Release 22.214.171.124 Issues
- 5 Release 126.96.36.199 Issues
- 6 Release 188.8.131.52 Issues
- 7 Release 184.108.40.206 Issues
- 8 General Issues
- 8.1 Windows
- 8.2 Linux
- 8.3 Mac OSX
- 8.4 Other
- 8.4.1 ESET Smart Security version 8: High CPU in Vuze
- 8.4.2 SSL handshake errors
- 8.4.3 SunCertPathBuilderException
- 8.4.4 java.security.NoSuchAlgorithmException
- 8.4.5 javax.net.ssl.SSLException: Received fatal alert: internal_error
- 8.4.6 Torrent download fails with 'Server returned HTTP response code: 503'
- 8.5 iTunes Integration Problems
- 9 Non Issues
Release 220.127.116.11 Issues
No outgoing connections
If you have configured an unlimited torrent connection limit (Tools->Options->Transfer: per-torrent or global peer limits) then there is a bug that prevents outgoing connections from being attempted (incoming will be accepted). You can fix this by configuring a large limit (e.g. 1000) instead of using '0' to denote 'unlimited'
Release 18.104.22.168 Issues
Windows installer/runtime error on upgrade
After running the update installer and subsequently starting Vuze you may receive the following error message:
No JVM could be found on your system. Please define EXE4J_JAVA_HOME to point to an installed 64bit JDK orJRE.
The solution is to run the installer from http://www.vuze.com/download - don't uninstall Vuze just re-install.
This issue is fixed for new updaters.
Vuze crashes on start
Although not definitely tied to the release itself some users are experiencing a crash when starting Vuze. See Vuze_disappears#SWT_Browser_Issues for an overview of the problem and a workaround. Normally you would join the Beta_Program to install the latest updates but if Vuze crashes on startup you won't be able to do this - please manually install the update from http://dev.vuze.com/
Once on the latest beta Vuze should automatically disable the internal browser and hopefully run successfully. If not please try manually disabling the browser by creating some Configuration Presets. You will need to enter the following into the presets file:
Not an issue, but if you really can't get used to the new context menu then you can enable the old menu by deselecting Tools->Options->Interface->Table: Library: Show fancy menu.
Note that the existing top level Torrents menu (enabled via Tools->Options->Interface->Display: Various: Show the Torrents menu) also uses the older menu style.
Occasional ding sound when running Vuze
The new Chat feature plays a sound when a new message is received and you don't have that chat window open. You can disable this - see Decentralized_Chat#Notifications
- The default has been switched by patch for 22.214.171.124 users so you will need to turn the notification on if you want it
Unfortunately the ability to switch back to the old-style menu was broken in 126.96.36.199. This is corrected in 5601 B03 and above so if you need to switch then please join the Beta_Program
- This issue has been patched for 188.8.131.52 users so you should now be able to switch menus successfully...
Release 184.108.40.206 Issues
Linux UI Issues
- UI components fail to draw correctly
5500 required an update to SWT to version 4508 to function properly. There are two versions of GTK at large, the older GTK2 (which Vuze has worked with for a long time) and the newer GTK3. Unfortunately there are major issues with GTK3 and Vuze at the moment (the sidebar doesn't draw correctly, SWT Group items don't render, the 'open-torrent-dialog' is a mess). So for the moment at least we force GTK2 via a new directive in the startup script:
If you are having issues please ensure that your SWT is version 4508 (check Help->About) and that your startup script has this entry (this should automatically be added on upgrade)
This has resolved problems for some users but there are outstanding problems with CentOS 6.6 + metacity
- Vuze crashes when opening dialogs (such as the open-torrent dialog)
If you are using 'Oxygen GTK' see http://forum.vuze.com/Thread-Vuze-5-5-0-0-crashin-when-adding-torrent-file for a work around.
Release 220.127.116.11 Issues
Torrents reporting 'Network not enabled'
After updating some users are finding some of their torrents report 'Network not enabled' against the torrents' tracker status. This is for public trackers (http(s) or udp ones).
This has most likely been caused by the fixing of a bug that was causing the network enabled state to not be checked correctly - when the torrent was originally added the 'Public' network was disabled, either because the default networks had been changed under Tools->Options->Connection (see near the bottom of this page), or by manually disabling it by right-clicking on the torrent, selecting Advanced->Networks and deselecting 'Public'. Note that since 5400 the networks can also be selected in the 'torrent options' dialog when adding the torrent.
If you have changed the default then go to Tools->Options->Connection and re-enable the Public network. This will NOT fix existing torrents though as they remember their enabled networks in force when added (or later changed). To fix this you will need to (multi)select the torrents you want to change, right-click on them and use the Advanced->Networks menu to enable the Public network.
You will also need to stop and start the torrents for them to pick up the change.
There is some more discussion on the forum: http://forum.vuze.com/Thread-Connection-error-re-enable-Public-network
Release 18.104.22.168 Issues
Swing Web UI plugin broken
The 'Swing Web UI' plugin (http://plugins.vuze.com/plugin_details.php?plugin=webui) is broken and unfortunately needs an update to the core to work - please update to 5301_B02 or higher and make sure you have the updated plugin installed.
Release 22.214.171.124 Issues
- Vuze 5200 Windows installer, executable crash when ALSR is on; See Vuze forums Vuze 5200 Windows installer, executable crash when ALSR is on
Release 126.96.36.199 Issues
There is a bug in the way torrent links are handled when passed to Vuze from another process (for example, when clicking on a torrent/magnet link in a browser) that results in Vuze being activated but the torrent not being added to Vuze.
This is caused by an error in the code that prompts the user for the location to save the torrent file in.
It only happens when no default save location for torrents has been configured (by default this is configured to be a folder called 'torrents' in your Vuze configuration folder, so an explicit configuration change by the user is required to trigger this)
Work around is to define a default torrent save location: Tools->Options->Files->Torrents
Fix is in 188.8.131.52_B03 - see the Beta Program to access this.
Vuze Won't Start
- Java Versions Mismatch
This is most often caused by a mismatch between the type of Vuze installation you have and the type of your Java install. Both Vuze and Java come in two types, 32-bit and 64-bit. For things to work the two must agree - 32-bit Vuze needs a 32-bit Java and 64-bit Vuze needs a 64-bit Java. When you run the standard Vuze Windows installer you are actually running a 'stub' installer that works out which 32/64 bit 'real' installer you need and then downloads and runs it.
Sometimes things get confused and you end up with a mismatch of Vuze/Java types and things don't work.
If you can't figure things out then follow the instructions to remove all versions of Vuze and Java and then re-install Vuze.
- Hola VPN conflict
By default Vuze uses TCP port 6880 to communicate with itself - once Vuze is running any other attempts to start Vuze (e.g. clicking on a .torrent file) will cause Vuze to send instructions (e.g. 'open this torrent') to itself via this port.
Unfortunately, sometime in early/mid 2015, Hola selected the same port to use in its software. So when Hola's service is running it grabs control of the port. This confuses Vuze into thinking it is already running and prevents startup.
You can fix this by uninstalling Hola or by telling Vuze to use a different port - see Command Line Options for an example of how to do this by editing the Azureus.exe.vmoptions file.
Multiple Copies Of Vuze Running
If another application (e.g. Hola, see above) has taken control of the port that Vuze uses for internal communications then this can result in multiple copies of Vuze starting. To fix this issue either locate the application responsible ('Resource Monitor' is a good tool for this) or change the port that Vuze uses (again, see above for the Hola fix)
Linux Unity Global Menu Issue
With Vuze 5600 and Ubuntu 14.04 (and no doubt others) Vuze will crash when using the global 'View' menu. This is caused by a bug in the SWT library that Vuze uses when handing 'radio button' menu items (used to display the simple/detailed library view state in the menu).
You can work around this by disabling global menus - edit the Vuze start up script to add
before starting Vuze - alternatively manually enter this into a terminal before launching.
There are various other ways of disabling the global menu within Ubuntu - see their documentation.
From Vuze 5600_B27 and onwards the menu has been changed to use check buttons which don't trigger the crash.
Linux Oxygen Theme Issues
Vuze crashes with the following when going to various views that use List widgets (e.g. the Logging section in Options)
/builddir/build/BUILD/oxygen-gtk2-1.4.5/src/animations/oxygencomboboxdata.cpp:87: void Oxygen::ComboBoxData::setButton(GtkWidget*): Assertion `!_button._widget' failed.
This is fixed in version 1.4.6 of oxygen-gtk2 (e.g. see https://launchpad.net/ubuntu/vivid/+package/gtk2-engines-oxygen)
Linux Browser Views Blank
Internally Vuze uses an embedded web browser to display some views - for example search results. If these views are blank you may have success by installing webkit:
sudo apt-get install libwebkitgtk-1.0-0
On Ubuntu this works up to a point - last time it was tested the search results page caused a crash in libwebkit... :(
OSX 10.10 (Yosemite) Issues
As usual there is the issue with OSX upgrades removing previously installed versions of Java.
If you have an issue with Vuze not running after the upgrade we recommend you run the Java 1.7 installer from here:
OSX 10.9 (Mavericks) Issues
Occasionally an upgrade to 10.9 (also seems to apply to updates to Mavericks, such as going from 10.9.1 -> 10.9.2) will leave Vuze in a broken state - launching it does nothing, not even a bounce in the dock. This is caused by Mavericks not correctly determining that the upgrade has removed Java from the system and it needs to be re-installed.
Unless you previously manually installed Java 1.7 from java.com, and installed the Java 1.7 version from Vuze from sourceforge (http://sourceforge.net/projects/azureus/files/), you will need to install Apple's version of Java 1.6.
At time of writing this is available here: http://support.apple.com/kb/DL1572 (Java for OS X 2013-005)
If you did install Java 1.7 then the latest version is here: http://www.java.com/
- We have also had reports that a reboot of Mavericks can sometimes solve the issue where attempting to launch Vuze with no Java installed does not cause Mavericks to auto-prompt you to install a Java runtime
OSX 10.5 PPC Issues
- Missing application menus
- There are two SWT user interface libraries that are/were supported by Vuze on OSX - carbon (which was last updated in August 2010) and cocoa. PPC is also an old platform that can't be upgraded beyond OSX 10.5.
- While the more recent releases of Vuze still run on OSX 10.5 PPC there is an issue with the cocoa SWT library that causes Vuze's menus to be displayed incorrectly. They are still there - click on the Vuze menu to open it and then move your mouse to the right along the menu bar area - the missing menus will expand (for example the Tools menu and the Help menu). If this is too annoying you can switch to the (old, less supported) carbon SWT library. Open Vuze's options (either use the menu trick above to get to the tools menu or use the shortcut 'apple-key+,' (press the apple key and the comma together). Then go to the Interface section and select Display - look for the drop-down that shows 'cocoa' and change this to 'carbon'. Save the config and restart Vuze. The carbon SWT library should download and install and then request a restart, after which things should be working.
- You can tell which SWT library is in use by going to 'About Vuze' and looking in the 'System' box at the bottom right.
ESET Smart Security version 8: High CPU in Vuze
It seems that this version causes somewhat high CPU usage to be indicated against Vuze. This can be seen by checking the thread_1.log (or thread_2.log) files in the Vuze configuration folder's 'logs' folder - the most active thread will often be flagged as 'PRUDPPacketHandler:sender'. This is normally a low resource thread that is responsible for dispatching UDP packets. It would appear that ESET's in-procress interception and analysis of such UDP data is inefficient and causes high CPU usage.
Adding Vuze to the ESET exceptions apparently fixes this.
SSL handshake errors
Some sites are moving to using 256 bit AES crypto only. By default Java does not support this level of encryption, you will need to manually install the 'unlimited jurisdiction policy files'. See http://forum.vuze.com/Thread-handshake-failure-SSL-error
Some users are experiencing an SSL related exception of the form:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
If the problem persists then go to Tools->Options->Security and hit the 'Reset certificate store' button and restart Vuze
If the problem still persists then it may be caused by Vuze failing to auto-install a server certificate after following an HTTP redirect (in all versions up to 184.108.40.206). For one site where this is know to occur the issue can be fixed by manually opening the following (non-existent) torrent in Vuze
and waiting for the process to complete. Once this is done the SSL certificate will have been installed and other torrents that follow a redirect will subsequently work.
Alternatively install the latest beta (5721_B11+ - see Beta Program) to get an updated version which resolves this issue.
If you see the following exception when downloading resources over HTTPS such as torrents and subscriptions
java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
then you can try to fix this by either joining the beta program and installing 5721_B20+ (see see Beta Program) or by manually resetting your certificate store by going to Tools->Options->Security, hitting the 'Reset certificate store' button and restarting Vuze.
javax.net.ssl.SSLException: Received fatal alert: internal_error
This can be reported when you are running an old version of Java and/or Vuze - first make sure you are fully updated to the latest version of Vuze. Then check that your Java version is at least 1.8. You can see your current version in the 'About Vuze' window. Java can be updated by going to http://www.java.com/. If after updating the problem persists double check the Java version again. It is possible that Vuze is using a non-system version of Java. This is a particular issue on Mac where Apple's own legacy version of Java is version 1.6 and won't ever be updated. If this is the case you need to switch to the Oracle version by using the correct installer from https://sourceforge.net/projects/azureus/files/vuze/
Torrent download fails with 'Server returned HTTP response code: 503'
To work around this manually enter the torrent download URL in a web browser, download the torrent, then add it to Vuze directly.
Here's an example error message that shows the issue:
To work around this open your web browser and paste in the download URL (http://some.web.site/download/12345/). Then locate the .torrent file that has been downloaded and drag/drop it onto Vuze. Alternatvely use the 'Open Torrents' button at the top-left of Vuze, select the 'Add Files' button and browse to the .torrent file.
5741_B10 has a work around for this issue for the case where a torrent hash is available - when the initial download fails it will be retried as a magnet download. In the search results view this requires you to switch to the 'Native' results view using the button at the top of the results area. See the Beta_Program for details on how to get this.
iTunes Integration Problems
Although not specific to a particular release a number of users are reporting that the iTunes icon in their sidebar shows a yellow warning triangle with a tool-tip indicating that there are integration problems. See iTunes Tips for a potential solution to this on Windows.
Side Bar has Vanished!
The sidebar is the 'tree' view normally present on the left-hand-side of Vuze, the top entry is 'My Torrents' and under this 'Library' etc. Within the Vuze UI this can naturally be hidden/restored by pressing F7 (or using the View menu's 'Side Bar' option) - it is replaced by two small UI components; one restores the sidebar when clicked, the other gives a menu view of the sidebar components.
There is also a separate Vuze user interface known as the 'Classic UI' or 'Azureus Experience'. This does not have a sidebar view at all.
Users occasionally switch between the regular Vuze view and the Classic UI by accident and then wonder where their side bar has gone. This can be remedied by
Internal Browser Is Disabled
Vuze uses an embedded browser component to display web content within the application itself (via the SWT UI framework). On Windows this uses Internet Explorer (on OSX Safari and on Linux Firefox if configured correctly). Unfortunately, a crash in the browser code causes Vuze itself to crash. This is a particular issue on Windows, there seems to be some users with an Internet Explorer configuration that triggers frequent crashes (exact cause unknown, perhaps browser extensions that these users have installed?).
To improve the stability of Vuze, from version 5600 onward, Vuze will look for evidence of previous crashes caused by the browser component and automatically disable its use. When this happens you will see a message to this effect within Vuze when navigating to views that use the component.
To re-enable the browser you need to
- ensure that your 'mode' is set to 'advanced' under Tools->Options->Mode
- enable the browser by unchecking the 'disable all use of internal browser' under Tools->Options->Interface->Display: Internal Browser
- restart Vuze