Video Feeds Issues: Firewall & Proxy Requirements

It's possible that restricted networks, usually in a corporate setting, can hinder video feed performance. In this article, we'll show you firewall requirements and proxy requirements. Note that this info is best shared with your IT department if you're experiencing issues.

Firewall Requirements

Greenroom requires access to specific ports. At a minimum the following requirements must be met:

  • Open TCP port 443
  • Whitelist the following domains:
    • *.brand.live
    • *.brandlive.com
    • *.brnd.live
    • *.tokbox.com
    • *.opentok.com
    • http://brandlive-upload.s3-us-west-2.amazonaws.com/

Along with the minimum requirements, opening UDP Port 3478 will give you a better experience. UDP is highly recommended over TCP for better quality audio and video. The protocol favors timeliness over reliability which is consistent with the human perceptive preferences; where we can fill in gaps but are sensitive to time-based delays.

This port only accepts inbound traffic after an outbound request is sent. The connection is bidirectional but is always initiated from the corporate network/client so it is not possible for an external entity to send malicious traffic in the opposite direction. For the best possible experience, we recommend opening UDP ports 1025 - 65535.

Whitelist the following HTTPS verification servers for our HTTPS certificate. Not doing so may cause console warnings, but should not affect the session.

  • ocsp.godaddy.com
  • crl.godaddy.com

Proxy Requirements

As a general rule, using the latest version of Chrome will produce the best results. If the only way to access the Internet from your network is through a proxy, then it must be a transparent proxy or it must be configured in the browser for HTTPS connections. WebRTC does not work with proxies requiring authentication. Along with these requirements, clients may have the following rules:

  • Chrome
    • Although not every option has been tested, recent versions have full support for authentication.
    • Pre-58 versions support NTLM authentication.
    • We've found a forwarding proxy setup with Kerberos does not work.
Top