Firewall and network settings for Physitrack

If a firewall only allows internet traffic to certain URLs or IP addresses, it uses the so-called whitelisting approach. Are you using Physitrack or Telehealth behind such a firewall? If so, make sure the following ports and URLs are whitelisted for our platform to work correctly.

Required for Physitrack to run properly

• XX.physitrack.com:443
• XX.physiapp.com:443
• search-XX.physitrack.com:443

Universal

• assets.physitrack.com:443
• cdn.physitrack.com:443
• physitrackuploads.s3.amazonaws.com:443
• *.firebaseio.com:443 (WebSocket Secure & HTTPS)
• identitytoolkit.googleapis.com:443
• media.physitrack.com:443

• s3.eu-central-1.amazonaws.com:443

  (we can provide a list of subpaths if this is too wide)

• s3.eu-west-1.amazonaws.com:443

  (we can provide a list of subpaths if this is too wide)

• s3.us-east-1.amazonaws.com:443

  (we can provide a list of subpaths if this is too wide)

• *.zoom.us:443 (both HTTPS & WebSockets)

Telemetry and monitoring

Tools that helps us troubleshoot any issues you might encounter

• *.ingest.sentry.io:443

Tracking

Tools that we use to understand how users interact with our platform so we can improve our product

• *.fullstory.com:443

Support tools

Customer Support tools integrated with the application for seamless experience and easy contact with our Support team

• beacon-v2.helpscout.net:443

Test your settings

You can test if you configured the firewall settings correctly by running in-app test video call.

See Google's documentation for presence detection (Google Firebase).