This guide will assist you with upgrading MediaCP on CentOS or Debian linux operating systems.
2. Login as Root
It is required that you login to the server as root user to upgrade the Media Control Panel.
3. Update System Packages
Before upgrading the MediaCP software, you should ensure your system has all the latest updates.
apt update && apt upgrade
You should backup your MediaCP software and store the backup off-site before every upgrade.
A software upgrade can fail for several reasons such as disk failure, sudden power-off, network connectivity loss and more. The upgrade can be an intensive operation as it may need to compile software or process database changes, this can be a common reason for issues with your servers disks, memory or other problems to be exposed.
5. Update Media Control Panel
su -c "$(curl -sSL http://install.mediacp.net) upgrade"If upgrading between major versions (i.e., 2.10 to 2.11) then we recommend restarting all services.
mediacp restart services
6. Update Mediacp Without Updating Wowza.
By default the MediaCP is tightly coupled with Wowza and does automatically manage the version.
If the currently supported version of Wowza is 4.8.18+1 and MediaCP will not upgrade beyond this version.
To prevent MediaCP from automatically updating Wowza Streaming Engine then you can make sure that our version file at /usr/local/mediacp/versions/WowzaStreamingEngine contains the current version number exactly as is, in this example the current version is 4.8.18+1. This means that when editing the version file you will need to enter exactly “4.8.18+1”.
Installation/Upgrade failed during prerequisites stage: This may occur if there is a problem with the yum or apt updates utility. If the install or upgrade gets stuck during this step you will need to contact your server provider to repair yum or apt, once repaired reattempt the upgrade or installation.