Prerequisites
- Java 21 (Red5 Pro 14.0.0+) or Java 11 (Red5 Pro 9.0.0–13.x)
- A valid Red5 Pro license key from account.red5.net
- A 64-bit operating system
unzipavailable on the system path
Install Red5 Pro
- Linux (Ubuntu)
- macOS
- Windows
Install dependencies
Ubuntu 22.04 is the recommended platform for production deployments. Install Java 21 and the required native libraries:If you are hosting on AWS, choose the Ubuntu 22.04 AMI rather than the Amazon Linux AMI. Amazon Linux may be missing libraries that Red5 Pro depends on.
red5pro/red5.sh and set JAVA_HOME="/usr/lib/jvm/jre-21".Download and unzip
1
Download Red5 Pro
Log in to account.red5.net and download the server ZIP distribution.
2
Transfer to your server
Copy the ZIP to your server. A common approach is SFTP into the
/tmp directory:3
Create the installation directory
4
Unzip the distribution
5
Add your license key
Your If you need to replace it, copy your key file to the same location and restart the server.
LICENSE.KEY file is included in the root of the ZIP. It is automatically placed at /usr/local/red5pro/LICENSE.KEY. Verify it is present:6
Start Red5 Pro
7
Verify the server is running
Open a browser and navigate to
http://localhost:5080. You should see the Red5 Pro landing page.Run as a systemd service
Running Red5 Pro as asystemd service ensures it starts automatically on reboot. This requires jsvc, which was installed in the dependencies step above.1
Copy the service file
The The service file uses these defaults:If your
red5pro.service file is included in the root of the server distribution:JAVA_HOME or RED5_HOME paths differ from the defaults, edit the file before proceeding.2
Set permissions and reload
3
Enable and start the service
4
Check status
When running as a systemd service, console output is suppressed. Server logs are written to
/usr/local/red5pro/log/red5.log. To tail logs after starting:OpenSSL compatibility workaround
If you encounter OpenSSL orlibcrypto compatibility errors at startup, open conf/network.properties and uncomment this line:License key
Red5 Pro will not start without a valid license key. YourLICENSE.KEY file is bundled in the server ZIP and is automatically placed in the root of the installation directory. You can also view and download your key from the account overview page.
If you replace the license key file, restart Red5 Pro for the new key to take effect.
In an autoscaling deployment, the
LICENSE.KEY file must be baked into the AMI or image used for node provisioning. See the Stream Manager documentation for details.Upgrade from a previous version
1
Copy the new distribution to your server
Upload the new ZIP to
/tmp or another staging directory.2
Unzip to a separate directory
3
Copy custom web applications
If you have custom apps in
red5pro/webapps/, copy them from the old installation to the new one.4
Re-apply configuration changes
Do not copy configuration files wholesale. Instead, open each modified config in the old installation and apply the same changes to the corresponding file in the new distribution. Common files to check:
conf/red5.properties— SSL settings, port overridesconf/red5-common.xml— FLV-to-MP4 and S3 storageconf/cluster.xml— clusteringconf/webrtc-plugin.properties— WebRTC settingsconf/simple-auth-plugin.propertiesandsimple-auth-plugin.credentialswebapps/live/WEB-INF/red5-web.xmlwebapps/api/WEB-INF/red5-web.properties
5
Stop the old server
6
Swap directories
7
Update Java if upgrading to v14+
If you are upgrading to v14.0.0 or later and were previously on v13.x, update
JAVA_HOME in the service file to point to Java 21:8
Start and verify
http://your-server-ip:5080 and confirm the new version number appears in the top-left corner.