The Twingate Client needs to be installed and running on your device in order to access Resources protected by Twingate. The Twingate application is small (less than 10MB) and requires minimal system resources when running. Twingate makes use of the native VPN functionality on the host operating system in order to intercept traffic for protected Resources. Seeing a VPN connection activate on your device is expected.
Simply go to get.twingate.com and the Client will automatically download for your device’s platform.
See Download & Installation for more detailed information.
Twingate is compatible with most device management solutions. The Managed Devices section contains more detailed information.
The Twingate Client requires outbound connectivity on the following ports:
- Outbound initiated TCP Port:
443(basic communication with the Twingate Controller and Relay infrastructure)
- Outbound initiated TCP Ports:
30000-31000(opening connections with Twingate Relay infrastructure in case peer-to-peer is unavailable)
- Outbound initiated UDP and QUIC for HTTP/3 (see this guide for more information) Ports:
1-65535(allows for peer-to-peer connectivity for optimal performance)
The Client does not usually need any special firewall rules opened, but if issues with connectivity are observed use the list above to troubleshoot.
Last updated 24 days ago