Note: The updated firewall rules can be found here.
For minimum functionality with VSee, the firewall should allow connections to the hosts listed below. Note that hosts will be added to this list as demand for VSee grows.
VSee XMPP Servers
Allow connections over HTTPS (TCP/5222 is preferred, but performance impact is minimal).
- talk.vsee.com (points to one or the hosts below)
VSee Relay Servers
Allow connections over UDP 6000 for best performance. Allow connections via HTTPS or HTTP for lesser performance.
- cl-relay.vsee.com (points to one or the hosts below)
Note: if you employ VSee Messenger within US only, you may restrict media traffic to within US by opting to whitelist usw*-rel.vsee.com and use*-rel.vsee.com only
VSee STUN Servers
Allow connections over UDP 6000 or 3478 to these servers to allow VSee clients to make direct UDP connections.
VSee Application Servers
Allow connections to these servers over HTTP and HTTPS. These servers perform account management functions for VSee.
- client.vsee.com (for Feature Control, strictly required)
- my.vsee.com (for Profile Management, optional)
- assets.vsee.com (for Chat File Transfer)
- ironmq.vsee.com (for Messenger diagnostics)
- *.pubnub.com (for API clients only)
- cloudfront.vsee.com (for Messenger updates)
- vsee-activeapi.firebaseio.com (for API clients only)
- s3.amazonaws.com (for Cloud Recording clients only, optional)
VSee Bandwidth Measurement Servers
Allow connections to this hostname over HTTP and HTTPS. The IP addresses of the servers for this hostname can change frequently.
For optimal performance: To allow for VSee clients to directly communicate with each other, inbound and outbound UDP on ports 6000 – 6254 should be allowed to all hosts. This will further improve A/V performance and reduce load on firewalls and web proxies.
Performance Impact of Web Proxies: The VSee client can connect to all the above hosts via a Web Proxy. However, A/V performance will be dependent on the Web Proxy’s capacity. Some factors that might affect performance through a proxy are:
- load on the Web Proxy
- prioritization of persistent HTTP(S) connections through the proxy. For best VSee performance, the Web Proxy should allow persistent HTTP(S) connections.
If at all possible, the Web Proxy should be configured to allow traffic to the VSee Relay Servers to proceed directly.
Testing VSee Connectivity
You may test your connectivity with several key resources from VSee Network Test Page. This tests your connectivity with VSee XMPP Servers, VSee Relay Servers over HTTPS only (not preferred) and VSee Application Servers.