WebRTC Installation

You can provide WebRTC application for your customers from your own server. To do that you need to select Your own servers (servers_own) feature and fill in the domain on which you want to serve your webRTC application (webrtc_domain) in the Whitelabel options . After the application builds, you will find a tarball (.tar.gz file) among the files produced by the build.

This file contains a directory dist which contains the files you need to deploy to your web server. The content must be accessible over HTTPS due to Web Browser’s security policy. We recommend redirecting plain HTTP to HTTPS version and using appropriate HSTS headers.


Anytime a new version of your app is made live, there will be a new tar.gz file and you should update the server hosting webrtc with it.

Set up your HTTP server in the following way:

  • the files should be available in the root of the server
  • if a requested file exists, it should be returned.
  • if the root is requested, content of index.html should be returned.
  • if the requested file does not exist, redirect to root (/) should be returned with the requested url placed after # sign.

Example configuration file for nginx:

server {
  listen 443 ssl;

  ssl_certificate /path/to/cert.pem;
  ssl_certificate_key /path/to/key.pem;

  server_name your-webrtc-domain.example.com;
  root /path/to/dist;

  location ~ "^/$" {
    try_files "${request_uri}index.html" @redirect;

  location / {
    try_files $uri @redirect;

  location @redirect {
    return 302 "https://$host/#$request_uri";