Network Access Requirements


To establish cloud connections, computers and devices running VNC Connect must be able to communicate with RealVNC’s cloud service at the locations in the tables below. If a proxy or firewall is blocking outgoing communications, cloud connections cannot be established.

You don’t need to comply with these requirements if you only establish direct connections.

Note on SSL/TLS Proxies

Strict certificate signature checking is used in VNC Connect clients (VNC Viewer and VNC Server) - SSL/TLS proxies that intercept SSL/TLS connections and mint new certificates will cause connections to fail. If SSL/TLS proxies or endpoint security software with SSL/TLS inspection are used in your organization, please ensure the IP addresses detailed below are whitelisted/bypassed.

If you are sure endpoints have network access but you still cannot establish cloud connections, check our service status page.

IP Addresses

IPv4 address TCP port UDP port Role

443 n/a Update notification service (optional)
443 n/a API gateway service

443 n/a Cloud team management services 443 n/a 443 n/a 443 n/a 443 n/a 443 n/a 443 n/a Cloud bootstrap services 443 n/a 443 n/a 443 3478

Cloud connectivity services 443 3478

11000-20000* 443 3478


* required for High Speed Streaming and Audio


If your network proxy or endpoint security software requires hostname/DNS entries instead of IPs, such as zScaler, or restrict DNS lookups on your network, you must allow the following domains:

Domain Role VNC Connect Single Installer (optional)
* VNC Connect cloud services
Was this article helpful?
62 out of 100 found this helpful



Article is closed for comments.