The following describes the steps in setting up a new Google Cloud Virtual Machine instance. This document assumes that you have already set up Google Cloud compute and the associated SDK for management (https://cloud.google.com/sdk/). We recommend running Red5 Pro on linux.
Create a network profile that contains a firewall rule to make the following ports accessible from anywhere:
|5080||default web access of Red5 Pro/Websockets for WebRTC||TCP|
|443||modified https access of Red5 Pro; secure websockets for WebRTC||TCP|
|1935||default Red5 Pro RTMP port||TCP|
|8554||default RTSP port||TCP|
|6262||websockets for HLS||TCP|
|8081||websockets for WebRTC (severs earlier than 5.4.0)||TCP|
|40000-65535||TURN/STUN/ICE port range for WebRTC||UDP|
* If you are running a version of Red5 Pro earlier than 5.4.0, then you must add the websocket ports (8081/8083).
* As of release 5.4.0,
websockets automatically use the same ports as http/https as defined in
tcp:5080; tcp:443; tcp:1935; tcp:8554; tcp:8081; tcp:8083; tcp:6262; udp:40000-65535
From Compute Engine, VM, create an Ubuntu 16.04 instance (recommended for the small footprint of the OS, and the stability of this release), using the network you created.
IMPORTANT NOTE: choose Standard Persistent Disk type, instead of the default SSD . We have observed issues with Red5 Pro services starting up on the SSD disk images and with Google's Ubuntu 15 image.
For basic RTMP and RTSP testing, the n1-standard-1 machine type should be sufficient (or n1-standard-2 if you have multiple beta users or are mostly using WebRTC). More details on Google's machine types here
Once the instance has spun up, use the Google Cloud SDK to copy the latest version of Red5 Pro server to the instance:
gcloud compute scp red5pro-server*.zip red5pro-image-01:/tmp/
SSH into the server and install java and unzip so that you can set up the server:
gcloud compute ssh red5pro-image-01
Follow directions for installing Red5 Pro server on linux