What firewall whitelisting requirements are there?

This article shows which following IP/ports must be accessible to run SynergyXR.

Network Specification

The following IP/ports must be accessible to run SynergyXR – either through proxy settings or firewall whitelisting.

Hostnames and IPs

We don’t always use dedicated IPs. For some scenarios we know the hostnames, and they are always the same not subject to change like “login.synergyxr.com” and “portal.synergyxr.com” but the IPs may be dynamic.

Fundamentals (DNS)

The client will need to be able to make DNS queries to function properly (UDP and TCP port 53).

SynergyXR Backend Hosted by Microsoft Azure

Outbound traffic needs to be allowed for the following types of network traffic as listed here. As this is regular HTTPS traffic it should be possible to do this via proxy.

CDN and Azure Blob Storage

Outbound traffic needs to be allowed for the following types of network traffic as listed here. As this is regular HTTPS traffic it should be possible to do this via proxy.

Photon Engine

Outbound traffic needs to be allowed for the following types of network traffic as listed here.

We are currently migrating to new servers, where the following must be whitelisted.

You should have received a separate e-mail about the migrations - please follow the steps described in the e-mail for a smooth migration. 

Tools and Assets Download (non-essential)

Outbound traffic needs to be allowed for the following types of network traffic as listed here. As this is regular HTTPS traffic it should be possible to do this via proxy.

This endpoint is non-essential for the use of the SynergyXR platform, but is used to host DRM-free training assets and tools like the Environment Builder.