1. SynergyXR Knowledge Base
  2. SynergyXR Security and Connectivity

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.

Hostname/IP Protocol Port Description
cdne-sxr-synergysharedstorage.azureedge.net TCP 443 HTTPS
synergysharedstorage.blob.core.windows.net TCP 443 HTTPS
stsxrtips.z6.web.core.windows.net TCP 443 HTTPS
stcachecontainer.blob.core.windows.net TCP 443 HTTPS

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 

Hostname/IP Protocol Port Description
login.synergyxr.com TCP 443 HTTPS
storage.synergyxr.com TCP 443 HTTPS
portal.synergyxr.com TCP 443 HTTPS

Photon Engine

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

Hostname/IP IP Protocol Port Description
pi_unitystudios-eu-ns.exitgames.com 52.157.184.50 TCP 4533 Client to Nameserver
azeu704-master.exitgames.com 52.157.78.135 TCP 4530 Client to Master Server
azeu704-game.exitgames.com 52.157.74.166 TCP 4531 Client to Game Server
  52.157.184.42 TCP 4531 IP of VM