The Parsec application communicates with our backend via TCP, with our STUN server via UDP, and peer-to-peer with other Parsec hosts via UDP. All TCP traffic is encrypted and uses port 443, STUN UDP traffic uses port 3478, and the encrypted peer-to-peer UDP traffic uses port ranges specified in Parsec Settings or the configuration file. A value of 0 for the port settings will cause Parsec to use psuedo-random defaults based on the computer's hostname. Parsec will use one port, incremented from the Host Start Port, per client connection. If you want to allow for collaboration, you should reserve 2 or 3 ports (for 2 or 3 people to connect at once) to each workstation. If your organization's firewall allows for UDP hole punching, Parsec will work without any additional configuration. If not, choose whatever works best with your security model to allow the peer-to-peer UDP traffic to the Parsec application.
Parsec API calls can be configured to work with your proxy if you'd like to put a proxy between the computer and the Parsec servers. Here's how you set up a proxy with Parsec.
You can also use the Parsec Gateway Server - a high performance on-prem relay server to manage traffic and your firewall. More details are available here. This is an add-on to Parsec for Teams.
If you'd like to force connections to happen within your VPN, please block the STUN server IP addresses in your firewall settings.
If whitelisting by domain name or IP is necessary, here is the full list:
|Domain / IP address||Purpose||Protocol and Port|
|Websocket API||TCP 443|
|builds.parsecgaming.com||Automatic Updates||TCP 443|
|images.parsec.app||Image CDN||TCP 443|
|IPv4 220.127.116.11||STUN Server||UDP 3478|
|IPv6 2600:1f18:63d9:c506:1337:1337:1337:1337||STUN Server||UDP 3478|