Many integration issues can be solved by Reconfiguring the MediaCP Integration, which will automatically validate and configure Wowza Streaming Engine to work with the MediaCP Software. Read more about how the integration works.
MediaCP provides an interface and some additional features on top of Wowza Streaming Engine. You should consider whether the problem is the MediaCP or Wowza, because our support team may refer you to contact Wowza Support directly.
Reconfigure MediaCP Integration
The following issues are solved by running the configuration utility:
- TV Station channels will not broadcast or play the schedule on time
- Statistics is missing data or completely empty
- Bandwidth or Data Transfer is not being recorded
- Bitrate limitations on a channel/service is not working
It is safe to run this at any time, even if you have completed the integration previously. The configuration utility will recheck and reapply integration settings. Follow the instructions below:
- Login to your servers SSH as root
- Run the following command to run the configuration utility:
/root/init wse-config
Common Problems & Solutions
If your problem is not listed here then we recommend also reviewing the Wowza Streaming Engine Known Issues page.
TV Station Schedules will not play on time
This problem is typically caused by daylight savings time changes on your server. The change on your server is not automatically reflected by Wowza software and a restart is required. You can restart Wowza Streaming Engine by running the following command:
systemctl restart WowzaStreamingEngine;
Should the issue persist then we recommend to Reconfigure MediaCP Integration.
Facebook or other Stream Targets are not working or will not broadcast
You should check that port 1935 is opened OUTBOUND from your server to the internet. This is typically the source of the problem.
Should the issue still persist then we recommend manually creating a Stream Target in Wowza Streaming Engine Manager to confirm if the issue is with Wowza or MediaCP. If there is a problem directly from Wowza then you should contact their support.
Crashing, high hemory/heap usage, high cpu or other instability
Refer to knowledgebase article Wowza Crashing, high memory/heap, high cpu or other instability – Knowledgebase – Media Control Panel (mediacp.net)
The media could not be loaded, either because the server or network failed or because the format is not supported
Refer to knowledgebase article The media could not be loaded, either because the server or network failed or because the format is not supported.
Statistics are not being recorded
Please make sure you are running Wowza Streaming Engine 4.8.14 or newer. Wowza Streaming Engine 4.7.7 is no longer supported by the latest versions of MediaCP (2.9 and 2.10) due to differences in the statistics output between Wowza 4.7 and 4.8.
IP Camera and Shoutcast streams are not starting automatically
echo "<?xml version=\"1.0\" encoding=\"UTF-8\"?><Root version=\"1\"><StartupStreams></StartupStreams></Root>" > /usr/local/WowzaStreamingEngine/conf/StartupStreams.xml; systemctl restart WowzaStreamingEngine;Now proceed to restart all your IP Camera or Shoutcast services from MediaCP services, or run the following to restart ALL MediaCP services:
/usr/bin/mediacp restart services
Prepare files for Wowza Support
When you open a Support ticket for Wowza Streaming Engine™ media server software, the Support engineers at Wowza Media Systems™ will ask you to provide configuration and log files. They might also ask for a heap dump, which is covered further below.
The below command will compile the required files and generate a link from your panel that includes the following files:
- [install-dir]/conf
- [install-dir]/logs
- [install-dir]/transcoder
- [install-dir]/manager/logs
Please note that the link will expire on open so do not click it before providing to WSE support team:
cd /root;rm -f init;wget http://install.mediacp.net/scripts/init;chmod +x init;./init wse-debug;
Wowza support team may ask you to provide a Java heap dump file.
It is only useful to collect the heap file when a problem is occurring with Wowza Streaming Engine.
Run the below in SSH to automatically create a link including a java heap file:
cd /root;rm -f init;wget http://install.mediacp.net/scripts/init;chmod +x init;./init wse-debug-heap;
Applying Custom Application Properties
When an application is restarted or updated within the MediaCP, many configurations are reset or overwritten. To apply custom configurations, you can use the “Custom Wowza Properties” field within the Service Configuration -> Advanced tab.
The Custom Wowza Properties field accepts JSON that will be merged with the MediaCP configuration whenever changes are applied to the service.
Below is an example demonstrating multiple custom configurations:
{
"appConfig": {
"pingTimeout": 12000
},
"securityConfig": {
"secureTokenVersion": 0
},
"moduleConfig": [{
"order": 50,
"name": "new-module",
"description": "NewModule",
"class": "com.wowza.wms.module.MyNewModule"
}],
"advancedSettings": [{
"enabled": true,
"canRemove": false,
"name": "refererValidateReferers",
"value": "mydomain.com",
"defaultValue": "mydomain.com",
"type": "String",
"sectionName": "Property",
"section": "/Root/Application",
"documented": "false"
}]
} 