Using OpenMeetings with RTMPS and HTTPS

There are 3 ways the client communicates with the server:

  • The flash-client uses RTMP protocol to transfer Audio/Video and to send and receive the user data (login et cetera) to the server and back
  • The browser uses HTTP protocol to load the SWF and to upload and download the files (documents, pdfs, images) to the server and back.
  • The screensharing client uses RTMP protocol to transfer screen data and remote control to the server and back


  • You need OpenMeetings 1.9.x or later for this, OpenMeetings 1.8.x does not have those options.
  • Install OpenMeetings according to the install instructions and check that it runs without problems
  • Rename the existing keystore file red5/conf/keystore.jmx to red5/conf/keystore.bak
  • Rename the existing truststore file red5/conf/truststore.jmx to red5/conf/truststore.bak

Configuring RTMPS for the Flash Client

  1. Create a new keystore and key, use the same password for both:

    keytool -keysize 2048 -genkey -alias red5 -keyalg RSA -keystore red5/conf/keystore
    Enter keystore password:
    Re-enter new password:
    What is your first and last name?
    [Unknown]:  <your hostname, e.g>
    What is the name of your organizational unit?
    [Unknown]:  Dev
    What is the name of your organization?
    [Unknown]:  OpenMeetings
    What is the name of your City or Locality?
    [Unknown]:  Henderson
    What is the name of your State or Province?
    [Unknown]:  Nevada
    What is the two-letter country code for this unit?
    [Unknown]:  US
    Is, OU=Dev, O=OpenMeetings, L=Henderson, ST=Nevada, C=US correct?
    [no]:  yes
    Enter key password for <red5>
  2. Generate a CSR:
    keytool -certreq -keyalg RSA -alias red5 -file red5.csr -keystore red5/conf/keystore
  3. Submit CSR to your CA of choice and receive a signed certificate
  4. Import your chosen CA's root certificate into the keystore (may need to download it from their site - make sure to get the root CA and not the intermediate one):
    keytool -import -alias root -keystore red5/conf/keystore -trustcacerts -file root.crt
    (note: you may receive a warning that the certificate already exists in the system wide keystore - import anyway)
  5. Import the intermediate certificate(s) you normally receive with the certificate:
    keytool -import -alias intermed -keystore red5/conf/keystore -trustcacerts -file intermediate.crt
  6. Import the certificate you received:
    keytool -import -alias red5 -keystore red5/conf/keystore -trustcacerts -file
  7. Please NOTE according to this guide you can split keystore and truststore (OPTIONAL you might just copy keystore to truststore)
  8. Create additional certificate as described above. Add this certificate to the following keystores: red5/conf/keystore.screen and red5/conf/keystore. (This step is required to be able to use screen-sharing web application, you can copy "main" keystore while testing)

SSL for the web interface

Please perform following steps if you want to use SSL for the web interface. This is mainly to secure the server against MITM attacks, additionally some other features like file uploads also use a plain HTTP connection if this is not done. The following instructions assume that you have already set up RTMPS successfully.

  1. Edit red5/conf/jee-container.xml file:
    Comment Tomcat without SSL enabled section
    UNComment Tomcat with SSL enabled section
  2. Edit red5/webapps/openmeetings/public/config.xml and set
  3. Restart red5 and try to connect to https://your.server:5443 - you should be redirected to the OpenMeetings app and all access should be via HTTPS and/or RTMPS (close port 5080 to be sure).

Set up RTMPS

Tunneling RTMPS

  1. HTTPS need to be enabled otherwise tunneling will not work (it can be set up using frontend nginx/apache as well)
  2. Edit red5/webapps/openmeetings/public/config.xml and set

  3. Please NOTE rtmpsslport port set in red5/webapps/openmeetings/public/config.xml should match https port set in red5/conf/
  4. Restart red5 and try to connect - your connection should now be made via RTMPS (close port 1935 to be sure)

Native RTMPS

  1. Default RTMPS port is 8443, you can change it by editing red5/conf/ and change the port here: rtmps.port=8443
    Please set rtmps.keystorepass=password and rtmps.truststorepass=password (password = password you set on your new keystore(s))
    Additionally you need to set rtmps.screen.keystorepass=screenpassword (screenpassword = password you set on your keystore for screen-sharing application)
  2. Edit red5/conf/red5-core.xml file:
    UNComment RTMPS section
  3. Edit red5/webapps/openmeetings/public/config.xml and set

  4. Please NOTE rtmps port set in red5/conf/ should be in sync with the rtmpsslport set in red5/webapps/openmeetings/public/config.xml
  5. Restart red5 and try to connect - your connection should now be made via RTMPS (close port 1935 to be sure)


Credits goto: Nexus and Holger Rabbach for their help and contribution and configuration documention!