The Twingate Linux Client currently supports the following Linux distributions for x86/AMD64 and ARM64-based devices:
- Ubuntu (18.04 LTS or later)
- Debian (9 or later)
- Fedora (35 or later)
- CentOS (Stream 8 or later)
Additionally, the following are supported for x64/AMD64-based devices:
- Arch Linux
If you use a different distribution or have feedback, please contact us.
- The Linux Client requires either
systemd-resolvedservice to be enabled/running or
NetworkManagerservice to be configured and enabled/running as the client DNS service.
- A notification service is required for interactive user authentication. If a notification service is not available, the Client will provide instructions for receiving a console-based notification feed.
Installation and Setup
The following command will download and install the Linux Client on any supported Linux distribution.
curl -s https://binaries.twingate.com/client/linux/install.sh | sudo bash
Once installation completes, you need to configure the Linux Client by running the following command:
sudo twingate setup
We recommend that you start the Linux Client from a terminal window within a desktop environment so that you can respond to authentication notifications. The Linux Client does not have a graphical interface, and is operated with the basic CLI commands below.
|Interactively configure the Twingate Client.|
|Start the Twingate Client.|
|Output Twingate Client status.|
|Stop the Twingate Client.|
|Show available Resources for the authenticated user.|
|Show usage information.|
User permissions when starting Twingate
It’s important that you start the Linux Client without elevated permissions—ie.
twingate start—in order to receive
desktop notifications required for authentication. Desktop notifications are using to alert the user when
authentication is required to access protected Resources. Running
sudo twingate start will result in these
notifications being hidden from the logged in user.
Advanced CLI commands are also available depending on the configuration or usage needs.
|To manually change a Client configuration setting, use twingate config [setting][value] . Example settings that can be configured: network , autostart , save-auth-data , log-level|
|Start desktop notifications for Twingate authentication requests.|
|Authenticate Twingate Client without desktop notifications. Note: Copy the URL returned and paste into a browser to authenticate the Twingate Client.|
Manual Client installation via package management
If you wish to add the Twingate Linux Client repositories manually, follow the steps below.
Early release channel
An early release version of the Twingate Linux client can be found in the
twingate-latest package. This package has the newest features, at the cost of it potentially being less stable than the
twingate package. The
install.sh script will default to the stable distribution.
twingate-latest conflicts with
twingate as they both install the
twingate binary. Only one package from either release channel can be installed at a time.
echo "deb [trusted=yes] https://packages.twingate.com/apt/ /" | tee /etc/apt/sources.list.d/twingate.list apt update -yq apt install -yq twingate # or twingate-latest # After installation, configure the client by running: sudo twingate setup
dnf install -y 'dnf-command(config-manager)' dnf config-manager --add-repo https://packages.twingate.com/rpm/ dnf config-manager --save --setopt=packages.twingate.com_rpm_.gpgcheck=0 dnf install -y twingate # or twingate-latest # After installation, configure the client by running: sudo twingate setup
Pacman (Arch Linux)
curl https://binaries.twingate.com/client/linux/ARCH/x86_64/stable/twingate-amd64.pkg.tar.zst --output twingate.pkg.tar.zst # for twingate-latest: curl https://binaries.twingate.com/client/linux/ARCH/x86_64/latest/twingate-amd64.pkg.tar.zst --output twingate.pkg.tar.zst pacman -Syy pacman -U --noconfirm twingate.pkg.tar.zst # After installation, configure the client by running: sudo twingate setup
Last updated 2 hours ago