Important general issues that affect Wowza Streaming Engine

This article describes important issues that may affect your deployment and management of Wowza Streaming Engine™ media server software. If available, workarounds for these issues are described. Check back often as this article will be updated as new developments occur.

Note: Where a third-party issue affects Wowza Streaming Engine software, it's the responsibility of the third-party to fix the problem. Wowza Media Systems works with these companies to help address the issue as soon as possible.

General known issues in Wowza Streaming Engine

Streaming to Facebook from Wowza Streaming Engine 4.7.8 doesn't work on some versions of CentOS

There is a problem with the Facebook stream target destination in Wowza Streaming Engine 4.7.8 that breaks the ability to send streams to Facebook when Wowza Streaming Engine is running on some versions of CentOS.


There is no fix available at this time, but you may be able to use the generic RTMP stream target destination type to send streams to Facebook. For more information, see Use RTMP to distribute live streams from Wowza Streaming Engine.

Removing the Wowza Streaming Engine 4.7.8 update results in the wrong version of Java

Previous versions of Wowza Streaming Engine media server software were built on Java 8. If you're updating an earlier installation of Wowza Streaming Engine to version 4.7.8 or later, you must install OpenJDK Java SE JRE 9.0.4 before running the Wowza Streaming Engine updater. However, because you must change to a more recent Java version to update to Wowza Streaming Engine 4.7.8, reverting to a previous version will result in having the wrong version of Java.


We recommend staying on the latest version of Wowza Streaming Engine. However, if you must revert to an earlier version, you'll need to manually change your Java version back to Java 8 (Java 8u91). For more information, see Manually install and troubleshoot Java on Wowza Streaming Engine.

Wowza Streaming Engine 4.7.7 can't be installed on macOS Catalina

New instances of Wowza Streaming Engine 4.7.7 or earlier can't be installed on macOS Catalina because the installer is a 32-bit executable. macOS Catalina requires 64-bit executables.


Wowza Streaming Engine 4.7.8 and later provides a 64-bit executable installer, making Wowza Streaming Engine installations compatible with macOS Catalina.

Erroneous log statements when accessing the Wowza Streaming Engine REST API over SSL

If you've enabled secure sockets layer (SSL) security for the Wowza Streaming Engine REST API, you may see the following warning statement in the logs even though the REST API queries are working properly:
WARNING: An error occurred during the communication with the remote HTTP server.


Disregard the erroneous log statements and use the Wowza Streaming Engine REST API as intended. No workaround is needed.

Publishing multicast streams with Wowza Streaming Engine generates unnecessary network traffic

In some versions of Wowza Streaming Engine software, when publishing a stream to a multicast group, an IGMP join group message was also sent. The IGMP message results in unnecessary traffic on the network and may result in packet loss issues as well.


This is fixed in Wowza Streaming Engine 4.7.6 and later.

Note: If, for some reason, you would like to continue sending IGMP join group messages with Wowza Streaming Engine and later, you can configure the sendIGMPJoinMsgWhenPublishing property To enable the behavior of previous Wowza Streaming Engine releases, do the following:

  1. In Wowza Streaming Engine Manager, click the Server tab and select Virtual Host Setup in the contents panel.
  2. In the details page, click the Properties tab, and then click Outgoing RTP Datagram in the Quick Links bar.
  3. In the Outgoing RTP Datagram section, click Edit.
  4. Change the sendIGMPJoinMsgWhenPublishing value to true and then click Save. (The default value is false.)
  5. Restart the server when prompted to apply the changes.

Wowza Transcoder doesn't work in some versions of Wowza Streaming Engine on CentOS 6

Wowza Streaming Engine 4.7.8

Wowza Streaming Engine 4.7.8 included changes to the minimum supported versions of some of the libraries used by Wowza Transcoder. For example, GNU C Library (glibc) 2.17 is now the minimum supported version.

Wowza Streaming Engine 4.7.5

Wowza Streaming Engine 4.7.5 included changes to some of the libraries used by Wowza Transcoder, including updating the GNU C Library (glibc) to version 2.14. However, CentOS 6.9 doesn't support glibc 2.14. This means Wowza Transcoder doesn't work on CentOS 6.9 with Wowza Streaming Engine 4.7.5. 


Wowza Streaming Engine 4.7.8

Update to a version of CentOS that supports glibc version 2.17 or later. Wowza Streaming Engine 4.7.8 doesn't support CentOS 6.

Wowza Streaming Engine 4.7.5

The best solution is to update to Wowza Streaming Engine versions - 4.7.7. 

Alternatively, you can update to CentOS 7, which supports glibc 2.14 and would enable you to use the fixes and new features in Wowza Streaming Engine 4.7.5.

If you can't update to CentOS 7 and need to use Wowza Transcoder, don't update to Wowza Streaming Engine version 4.7.5. Earlier versions of Wowza Streaming Engine media server software use glibc 2.12, which is supported by CentOS 6.9.

  • If you're installing Wowza Streaming Engine media server software for the first time, request a copy of the Wowza Streaming Engine 4.7.4 installer package.

  • If you've already updated to Wowza Streaming Engine 4.7.5, follow the instructions in Remove an update on Linux to remove the 4.7.5 update and revert to an earlier version of the media server software.

Wowza Streaming Engine 4.7.4 may experience problems sending streams to Wowza Streaming Cloud for transcoding

With Wowza Streaming Engine 4.7.4, the Stream Target functionality that enables you to send streams to Wowza Streaming Cloud for transcoding and delivery to users may not work. 

Note: This problem is limited to the Wowza Streaming Cloud target destination when configured for Wowza Streaming Cloud to transcode the stream. All other configurations of the Wowza Streaming Cloud and Wowza CDN stream targets work as expected in Wowza Streaming Engine 4.7.4.


Update to the latest version of Wowza Streaming Engine media server software. This problem is fixed in Wowza Streaming Engine 4.7.5. and later.

Checking for incorrect Java version when updating to Wowza Streaming Engine 4.7.3 or later

When updating Wowza Streaming Engine software to version 4.7.3 or later, it checks for Java version 1.6.0 or later. However, Java version 1.7.0 is the minimum required version.


With Wowza Streaming Engine 4.7.5 and later, the updater checks for Java version 1.7.0 or higher. 

Note: ​You still must use Java version 1.7.0 - 1.8.0_77 or use the Java version that is installed with Wowza Streaming Engine software (Oracle Java 1.8.0_77). Versions newer than 1.8.0_77 aren't supported. For more information, see Download and install Java.

Windows 10 may not start Wowza Streaming Engine services (Services error -1073741502)

The NSSM service manager can't open a console window when trying to start Wowza Streaming Engine services. This error may appear after a recent Windows 10 update.


Update your Wowza Streaming Engine installation to Wowza Streaming Engine 4.7.0. If you can't or don't want to update your media server software, do the following:

  1. Open an elevated Command Prompt window (press the Windows Logo+X keys, and then click Command Prompt (Admin) on the power user menu).
  2. In the Command Prompt window, navigate to a Wowza Streaming Engine installation bin folder that has an NSSM EXE file installed. There are two possible locations: [install-dir]/bin and [install-dir]/manager/bin.
  3. Run the following commands:
    nssm set [wowza-streaming-engine-service-name] AppNoConsole 1
    nssm set [wowza-streaming-engine-manager-service-name] AppNoConsole 1

You must use properly formatted service names in these commands. To get the service names, open the Services control panel (press the Windows Logo+R keys, and then type services.msc in the Run dialog box), right-click the Wowza Streaming Engine and Wowza Streaming Engine Manager services in the list, and then click Properties. The service name to use will be highlighted on the General tab in the Properties dialog box.

Example commands for Wowza Streaming Engine 4.6.0

nssm set WowzaStreamingEngine460 AppNoConsole 1
nssm set WowzaStreamingEngineManager460 AppNoConsole 1

Incorrect Wowza CPU statistics in Wowza Streaming Engine Manager (cloud deployments)

Note: Wowza Streaming Engine 4.7.0 and later includes Wowza CPU calculation improvements to address this issue. Get the latest Wowza Streaming Engine software.
If you deploy Wowza Streaming Engine media server software in the cloud, and then log into the web-based Wowza Streaming Engine Manager on the cloud-hosted virtual machine, the Usage graph in the manager may display a higher Wowza CPU value than the actual media server CPU usage. Refreshing the manager webpage may boost the Wowza CPU graph so that it's even more out-of-sync from actual CPU consumption.


To view Wowza CPU consumption:
  • Windows - Look at the running Java.exe processes in Windows Task Manager (be sure to Show processes from all users).
  • Linux - Run the following grep command to display running Java processes and filters for Java processes:
    PS - ef  | grep java*
    Then, to see the CPU usage for a particular Java process, run the top command using the Java process identifier (PID).

SHOUTCast and Icecast stream targets don't work (Wowza Streaming Engine 4.5.0)

Wowza Streaming Engine 4.5.0 software has an error that prevents the SHOUTcast and Icecast stream targets from working.


Install the latest updater for Wowza Streaming Engine software, which has a fix for this issue.

Misleading message when uninstalling Wowza Streaming Engine updaters (Wowza Streaming Engine 4.3.0 and later)

After you uninstall updater versions 4.3.0,,, 4.3.003, 4.4.0,, and 4.4.1, you may see a message that indicates your updater uninstall may have failed:
A required action of the update failed. The update did not complete successfully, see the wowzastreamingengine_update.log for details.


This message can be misleading. Check for the following message. If it's present, your updater uninstall completed successfully:
Restoration complete

Startup delays and hostname resolution problems on Azure Marketplace virtual machines

When running Wowza Streaming Engine virtual machines on Azure Marketplace, the Wowza Streaming Engine software may start after some delay. After startup, Wowza Streaming Engine Manager may display the virtual machine's private IP address, instead of the public IP address, on the Home, Sources (Live), and Test Players pages. These problems are caused by the way in which Azure Marketplace processes variable lookup metadata.


Future Azure Marketplace releases may optimize how variable lookup metadata is reported in the Azure platform. To permanently display the public IP address in Wowza Streaming Engine Manager, do the following:
  1. Connect to your virtual machine (Windows connection instructions | Linux connection instructions).
  2. Open the [install-dir]/conf/VHost.xml] file in a text editor and replace the <Manager>/<TestPlayer>/<IpAddress> value (${}) with your virtual machine's public IP address:
    		<IpAddress>[wowza-vm-public-ip-address]</IpAddress> <!--changed for default cloud install. -->
    	<!-- Properties defined are used by the Manager -->
  3. If you were signed in to Wowza Streaming Engine Manager, sign out, and then sign in again.
The Home, Sources (Live), and Test Players pages in the manager should display the virtual machine's public IP address.

Wowza Streaming Engine services don't start automatically on the latest Ubuntu 15.04

Wowza Streaming Engine services on the current Ubuntu server software release (15.04) fail as part of the installation and don't start automatically. This appears to be related to the recent move by Ubuntu from upstart to systemd (see SystemdForUpstartUsers).


Do ONE of the following:

Start Wowza Streaming Engine manually by running the following as root:
# /etc/init.d/WowzaStreamingEngine start

# /etc/init.d/WowzaStreamingEngineManager start

Reinstall the missing upstart functionality, which should ensure that Wowza Streaming Engine services are restarted on reboots:
# apt-get install upstart-sysv

Latest Linux updates prevent Wowza Streaming Engine from starting (init.d or systemd)

Wowza Streaming Engine services fail to start--either as legacy init.d scripts or as systemd services--after Linux is updated. We've observed this with Centos 7.2 updates.


Create the following service files:


ExecStart=/usr/local/WowzaStreamingEngine/bin/WowzaStreamingEngine start
ExecStop=/usr/local/WowzaStreamingEngine/bin/WowzaStreamingEngine start

# Give a reasonable amount of time for the server to start up/shut down


ExecStart=/usr/local/WowzaStreamingEngine/manager/bin/WowzaStreamingEngineManager start
ExecStop=/usr/local/WowzaStreamingEngine/manager/bin/WowzaStreamingEngineManager start

# Give a reasonable amount of time for the server to start up/shut down

Enable services
systemctl daemon-reload
systemctl enable WowzaStreamingEngine.service
systemctl enable WowzaStreamingEngineManager.service
Start new services
systemctl start WowzaStreamingEngine.service
systemctl start WowzaStreamingEngineManager.service

Antivirus tools falsely detect Luhe.Fiha.AN threat

Some antivirus tools report "Found Luhe.Fiha.AN" in Windows Installer (.msi) files for Wowza Media Server 3 and Wowza Streaming Engine software.


We believe this to be a false positive. Customers haven't reported any problems.

Issues with Java version 8u78 and greater

If you use your own Java Runtime Environment (JRE) with Wowza Streaming Engine (8u78 and greater), you may not be able to start Wowza Streaming Engine Manager.

You may also encounter an instability issue related to Java settings and see an error message similar to the following:

500 error is thrown: "Sorry there was an error getting to (server/performance/javasettings/edit.htm):
Internal Server Error:500"


If you use your own JRE, you can install an earlier JRE version that doesn't have these issues (see Manually install and troubleshoot Java on Wowza Streaming Engine) or you can run the latest Wowza Streaming Engine installer, which has an earlier version of the JRE. We'll monitor the Java updates and update this article with the latest findings.

Custom properties with leading and trailing blank spaces

If you use a text editor to add properties to Wowza Streaming Engine XML configuration files, you can't edit the property in Wowza Streaming Engine Manager if the property name or value has a leading (or trailing) blank space. For example, if you add the following property that has leading blank space in its name to an XML file:
	<Name>  myCustomProperty</Name>
When Wowza Streaming Engine Manager starts, it will load the XML file, and then remove the leading blank space from the property name that it displays in its user interface. (It does this because leading and trailing blank spaces are a common source of configuration errors.) For the example property above, the manager will display this as myCustomProperty in its UI.

If you try to edit myCustomProperty in the manager, the property will be saved as a new property to the XML file.
	<Name>  myCustomProperty</Name>


If your media server configuration requires a property with a leading or trailing blank space in its name or value, you must always edit this property in the configuration XML file using a text editor.

Updating to Wowza Streaming Engine 4.7.0 breaks existing configurations for HTTPS Manager connections

Updating to Wowza Streaming Engine 4.7.0 overwrites the startmgr.bat (Windows) or (Linux) file. This means that if you have configured Wowza Streaming Engine Manager to use a secure socket layer (SSL) certificate so that you can connect using HTTPS, that configuration is lost during the update.


After you have successfully updated to Wowza Streaming Engine 4.7.0, follow the instructions in How to connect to Wowza Streaming Engine Manager over HTTPS to reconfigure HTTPS connections.

More resources