DocumentationAPI ReferenceChangelog

Firewall Settings

Ensuring your firewall and anti-virus software give access to TelemetryTV

Suggest Edits

Firewall Configuration

TelemetryTV operates on dynamic cloud-based server IP addresses. For seamless functionality and to keep pace with our evolving capabilities, we don't recommend putting in place strict outbound firewall rules.

However, if you need to configure your firewall for outbound connectivity, here's what you need to know:

  1. Basic Connectivity: Ensure the following URLs have access through TCP port 443:

    • https://*.telemetrytv.com
    • https://s3.ca-central-1.amazonaws.com/linux.telemetrytv.com
    • https://*.bugsnag.com
    • https://*.googleapis.com
    • https://fonts.gstatic.com

  2. Google Apps Connectivity: If you're utilizing Google apps, add access for the following URLs on port 443 (Please note Google's URLs might change):

    • https://youtube.com
    • https://youtu.be
    • https://calendar.google.com
    • https://apis.google.com
    • https://www.gstatic.com
    • https://docs.google.com
    • https://ssl.gstatic.com
    • https://*.googleusercontent.com
    • https://googleusercontent.com
    • https://fonts.googleapis.com

  3. Website Apps Connectivity: Ensure you unblock any specific URLs you utilize within website apps.

  4. TelemetryOS Specific Connectivity: Make sure the following URLs are accessible:

    • https://archive.ubuntu.com
    • https://security.ubuntu.com

    Additionally, TelemetryOS requires standard internet services like DNS, NTP, and more. Do not block the Network Time Protocol (NTP) outbound. NTP configurations can be set via the DHCP server, or manually within TelemetryOS.

🚧

TelemetryTV's Dynamic Cloud Services

TelemetryTV's architecture is based on dynamic cloud services and Content Delivery Networks. Therefore, we don't support specific IP addresses or ranges. Always keep an eye out for new hostnames we might introduce.

Anti-Virus Configuration

For the Desktop/Player applications to communicate effectively, ensure your anti-virus software whitelists the URLs listed above.

Working with WebSockets

TelemetryTV utilizes HTTPS that subsequently upgrades to a WebSocket for continuous data streaming. If you encounter challenges, especially a 400 error mentioning "Error during WebSocket handshake," it could be due to WebSocket restrictions.

To address this:

  1. Confirm that web sockets are enabled on your network.
  2. Ensure your proxy supports the use of web sockets.
  3. Open TCP Port 443 to both:
    • wss://*.telemetrytv.com
    • https://*.telemetrytv.com

🚧

Proxying Web Socket Connections

We advise against proxying the web sockets connection due to potential connectivity disruptions.

Support

Please note that due to the endless complexities of network configurations that are out of TelemetryTV's control, TelemetryTV does not include troubleshooting these issues as part of the core support plan.

For issues that are not covered by TTV but require immediate attention, TTV will charge $200 USD/hour for support or configuration services as a professional services engagement upon request. For help, use the live chat button in the bottom right of your account screen to be connected to support.

Updated 7 months ago