Background / Context

For a proper creation of the peering network in eCDN mode, our Peering Manager component requires the local IP address of each participant from the stream’s audience.

This can be achieved in two ways:

  • Place a Peering Manager instance within the local network

  • Disable mDNS for specific URLs in the client’s browser

This article will describe the first mentioned variant.

Server Requirements

Maximum concurrent Users

Up to 1000

Up to 10000

Up to 25000

CPU requirements

2 cores

4 cores

8 cores

RAM requirements

4 GB

8 GB

16 GB

Operating system requirements

Supported operating systems:

  • RHEL (version 7+)

  • CentOS (version 7+)

  • Debian

  • Ubuntu

Other OS might take additional setup and testing effort with additional cost.

Network requirements

Full HTTPS (port 443) connectivity from Peering Manager to:

  • *

  • *

Support internal connections from clients to the Peering Manager via WSS/HTTPS

If wildcard whitelisting is not supported, we can provide you with specified domains or IP addresses.

Server authentication requirements

  • SSL certificate for HTTPS

  • Internal DNS entry

OPTIONAL: Application log requirements

Full HTTPS (port 443) connectivity from Peering Manager to:


This feature allows the StriveCast team to view the application log remotely which helps us trobuleshooting.

User Requirements

  • SSH access to the server

  • sudo rights or root access to the server

Who should use this document?

System- and network administrators, responsible for the server architecture, SSL certification and Firewall settings of the organization aiming to use StriveCast eCDN.


Your Technical Account Manager will provide you with the latest installation package based on your OS. Upload the .deb or .rpm package to the server and install the package with the distribution’s default package manager.

  • Debian/Ubuntu

sudo apt-get install /path/to/strivecast-p2pdn-tracker_$Version_linux_amd64.deb
  • RHEL/CentOS

sudo yum install strivecast-p2pdn-tracker_$Version_linux_amd64.rpm

Do not use the dpkg or rpm tools directly as they will not ensure all required dependencies are installed automatically.


After you have finished the installation successfully, the service will be enabled but not active/started. Future reboots will start the service automatically. Before the initial start, you need to adjust some configuration files

SSL Certificate

The Peering Manager only supports secured connections from clients which are ensured by usage of a valid SSL certificate.

If your certificate requires a chain, ensure to have the full chain in the certificate file you place on the server.

If your organization has its own certificate authority, you can use a self-signed certificate. In this case you need to ensure that the clients trust the certificate.

Option 1: Exchange the dummy files

During the installation, the package will generate two files located in /opt/strivecast/:

  • cert.pem

  • private.key

These are dummy files that you can replace with the actual certificate and corresponding key. In this case, you must not adjust the path to the certificate and key in /opt/strivecast/config.yaml

Option 2: Adjust the path in the configuration file

Alternatively, if the certificate is already on the server or you want to use a different directory, you can do this as well. Is this case, you must adjust the path to the certificate and key in /opt/strivecast/config.yaml

The Peering Manager service will run as the system user strivecast that is created during the installation. Please ensure that the user has at least read rights for the certificate and key.

Configuring the web proxy

If the peering manager needs to connect to the internet through a web proxy, you need to edit the file p2pdn-tracker located in /etc/default/. Uncomment one of the two variables (or both), depending on what kind of proxy server is used, and add the proxy IP address or DNS name. Changes in this file at a later point in time require a restart of the service to take effect.

Starting the service

Once you have done finished all configuration steps, you can start the service with systemctl start p2pdn-tracker. To verify that the service is running, run systemctl status p2pdn-tracker.

To get more detailed application logs, you can run sudo journalctl -u p2pdn-tracker.

Additional features

You have the possibility to configure the peering manager, that the application log is pushed to cloud storage that is accessible to StriveCast. This helps us to support you with troubleshooting, in case the service is not working as intended. To get more details on how to achieve this, please visit Activate local Peering Manager remote logging.

Frequently asked questions

  • Why does the service need to connect to the internet?
    Although the service is set up to allow local clients to connect, it pulls the SDK configuration from the internet.

  • The service is up and running but clients cannot connect.
    Please make sure that any local firewall running on the system itself allows access to port 443 (if the service is configured to use its standard).

  • Which format is required for the SSL certificate?
    The application only accepts certificate files in PEM format. PKCS 12, PFX or other formats are not supported.

  • Is the order of the chain important if I need to combine my certificate with an intermediate one?
    Yes, it is! Your / the server certificate always has to be the first one on top of the file, followed by the intermediate certificate, followed by the root CA certificate (in case it is not a public CA).

Contact us

For any further questions or problems, please open a ticket at the StriveCast Help Center.