TelemetryOS 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, firewall configuration for outbound connectivity requires the following information:

Basic Connectivity: Ensure the following URLs have access through TCP port 443:
- https://*.telemetryos.com
- https://s3.ca-central-1.amazonaws.com/linux.telemetryos.com
- https://*.bugsnag.com
- https://*.googleapis.com
- https://fonts.gstatic.com
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
Website Apps Connectivity: Unblock any specific URLs utilized within website apps.
TelemetryOS Edge Specific Connectivity: Make sure the following URLs are accessible:
- https://archive.ubuntu.com
- https://security.ubuntu.com
Additionally, TelemetryOS Edge 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 Edge.

🚧
TelemetryOS's Dynamic Cloud Services
TelemetryOS'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 anti-virus software whitelists the URLs listed above.

Working with WebSockets

TelemetryOS utilizes HTTPS that subsequently upgrades to a WebSocket for continuous data streaming. 400 errors mentioning "Error during WebSocket handshake" typically indicate WebSocket restrictions at the network level.

WebSocket handshake failures resolve through network configuration adjustments:

WebSocket Protocol Support: Network infrastructure must permit WebSocket protocol traffic (not just standard HTTP/HTTPS).
Proxy Compatibility: Proxy servers must support WebSocket upgrade requests and maintain persistent connections.
Port Accessibility: TCP Port 443 requires bidirectional access to both:
- wss://*.telemetryosos.com
- https://*.telemetryos.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 TelemetryOS's control, TelemetryOS does not include troubleshooting these issues as part of the core support plan.

For issues that are not covered by TOS but require immediate attention, TOS 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 the account screen to be connected to support.