6. Prepare Red5 Pro Node droplet

  1. From the left-hand navigation of the Digital Ocean dashboard, under the Manage section, choose Droplets
  2. Click on Create
  3. Choose Droplets from pull-down
  4. Choose an image: Ubuntu 16.04.6 (LTS) x64
  5. Choose a plan: CPU-Optimized; 4GB/2 CPUs c-2(this is the minimum suggested for running Red5 Pro) NOTE you will want to use the same instance type in your launch configuration policy. The cpu-optimized droplets are all c plus the number of CPUs (c-2, c-4, etc), Memory optimzed droplets are m plus the number of CPUs (m-2, m-4, etc).
  6. Choose a datacenter region
  7. Additional options are optional
  8. Authentication: choose SSH keys (select the key(s) you want to include
  9. Finalize and create: Choose a hostname; Select a Project; click on Create Droplet
  10. Click on Tags and add the following: sm-nodes
  11. Go the firewall that you set up for SM/nodes above, and click on Add Droplets. Type in sm-nodes and save. This will ensure that all nodes created by the stream manager get added to this firewall.


Install Red5 Pro on the Instance:

  • Connect to your instance over ssh as the root account.
  • Follow the Installing Red5Pro on a Linux Server instructions.
  • Make sure that Red5 Pro service is set to auto-start on launch.
  • Red5 Pro Clustering does not work without a license. You will need to purchase a Red5 Pro Professional license from Red5 Pro. Add a file named LICENSE.KEY with your Pro license key (16 characters, plus dashes, like: YOUR-LIC-ENSE-KEY1) to the root of the Red5 Pro Server installation ({red5prohome}/LICENSE.KEY).

Configure Autoscaling on the Instance:

Navigate to the location where you extracted the Red5 Pro files, and edit the file {red5prohome}/conf/autoscale.xml

<bean name="config"class="com.red5pro.clustering.autoscale.Configuration">
   <property name="active" value="false"/>
   <property name="cloudWatchHost" value=""/>
  • Change the active value from “false” to “true
  • Replace with the static ip of the Stream Manager
  • Save and close the file

Set a Unique Cluster Password:

Edit the file {red5prohome}/conf/cluster.xml and replace the default <!-- edge/origin link cluster password --> password from changeme to sometime unique. Make a note of this password, to be used in the Stream Manager red5.properties file.

NOTE: The cluster password can not contain any CAPITAL LETTERS at this time

Enable Red5 Pro Server API and Set Management Password:

Configure the Server API per this document. Modify the security.accessToken value in {red5pro/webapps/api/WEB-INF/red5-web.properties, and make a note of it. You will need this value for your Stream Manager.


Add the Stream Manager's Floating IP address to the {red5pro}/webapps/api/WEB-INF/security/hosts.txt file (or add * to make the API accessible from anywhere).


Remove Unnecessary Webapps:

To ensure a faster startup time for your server, we suggest deleting any webapps that you will not be using from the {red5prohome}/webapps directory (for example: secondscreen, template, vod, streammanager). For ease of setup for the Stream Manager, leave a zipped copy of the server distribution on the server. If you are running a custom webapp, then you would want to include that on your node servers.

Verifying Red5 Pro on Instance:

Start Red5 Pro service

sudo systemctl start red5pro

Once you have started the Red5 Pro Server, you can verify that it is running and available by opening a web browser and navigating to http://<server-ip>:5080, where is the Public address value of your Red5 Pro server.