Skip to content

HTTPS/SSL Settings

Setting Up HTTPS (SSL) for Studio, MediaHub, and CreativeHub

Erizos Studio Server, MediaHub, and CreativeHub support running over both HTTP and HTTPS. To enable HTTPS, you need to provide two specific files:

  • cert.pem – the SSL certificate
  • key.pem – the private key

Important

These files can be stored anywhere on the local disk, as long as you select them in the Studio settings. You do not have to place them in a specific default directory.

How to Enable HTTPS

For Studio

  1. Open Erizos Studio.
  2. Go to Settings → General.
  3. Scroll to the bottom and locate the HTTPS section.
  4. Toggle the HTTPS switch to turn it on.
  5. Click the folder icon next to Certificate and select your .crt or .pem certificate file.
  6. Click the folder icon next to Key and select your .key or .pem private key file.
  7. Press Save Settings.

HTTPS in Studio

For MediaHub

  1. Open MediaHub.
  2. Go to Settings → Settings.
  3. Repeat steps 3–7 from the Studio instructions.

For CreativeHub

  1. Open CreativeHub.
  2. Go to Admin → Settings.
  3. Repeat steps 3–7 from the Studio instructions.

Once set, the server will load these files at startup and serve over HTTPS using the provided certificate and key.

Encrypted Private Keys and the Passphrase Field

If your private key (key.pem) is encrypted (protected with a password or passphrase), the server will not be able to use it automatically unless the passphrase is provided.
If the passphrase is not entered, the Studio may fail to start or not serve over HTTPS, and the browser will not accept the certificate properly.
Why this happens:
Encrypted keys require a passphrase to unlock them. Without it, the server can't read the key, and the browser cannot establish a secure HTTPS connection.
If your key is encrypted:

  1. Type the passphrase into the Passphrase field.
  2. Press Save Settings.

HTTPS in Studio

This will allow the Studio to successfully load the encrypted key and serve HTTPS correctly.

Troubleshooting Tips

  • Make sure the certificate and key files match (they should be generated as a pair).
  • Check if the private key is encrypted. You can open the file in a text editor:
    • If it starts with -----BEGIN ENCRYPTED PRIVATE KEY-----, it's encrypted.
  • If you get browser errors or the Studio doesn’t load:
    • Verify that the key is not encrypted or
    • Make sure you entered the correct passphrase in Studio.
  • Also, check your browser settings — especially if you're using self-signed certificates. You may need to allow insecure content or import the certificate manually.