Twingate Connectors can either be run in a Docker container or as a systemd service on the host.

  • Docker containers are the most flexible in terms of support for any Linux distribution but involve some additional management overhead.
  • Our systemd-compatible service is supported on Ubuntu (18.04 LTS and later), CentOS, and Fedora Linux distributions. Running as a native system service is the most robust option with lower management overhead.

Docker Container

If you are running a Connector on a Linux host or VM, there are just two steps to follow to deploy a container-based Twingate Connector:

  1. Ensure that Docker is installed and running. Detailed steps for Ubuntu, Debian, Fedora, and CentOS are available from Docker, or you can use the following convenience script, which works on any Linux platform:
curl -fsSL -o
sudo sh

# Verify Docker is installed and running
sudo docker run hello-world
  1. Follow the Twingate Connector deployment instructions to deploy a new Connector on your Linux host.


We only recommend installing Docker via the official distribution channel by following the instructions above. Different channels may have out of date versions of Docker that are not compatible with the Connector image requirements.

For Amazon Linux, we recommend following the Twingate Connector deployment instructions to deploy a pre-built AMI, which has the systemd Connector service pre-installed.

Systemd Service

Supported distributions

Currently the following distributions are supported:

  • Ubuntu (18.04 LTS and later)
  • Fedora
  • CentOS (8 and later)
  • Amazon Linux

The Connector service may run on other Linux distributions, but we cannot offer support for additional distributions at this time. If you have a distribution that you would like official support for, please contact us.

First-time Installation

Installation of the systemd Connector service can be performed in a single command with the necessary environment variables set.

  1. Follow the Twingate Connector deployment instructions to provision a new Connector. Copy the ACCESS_TOKEN and REFRESH_TOKEN values for the connector. You will use these in the installation step below.

  2. Run the following command, adding your own values for the environment variables.

  • TWINGATE_URL should be the URL for your Twingate account, eg.
  • TWINGATE_ACCESS_TOKEN and TWINGATE_REFRESH_TOKEN values should be copied from the Connector provisioning command in the previous step.
  1. Verify that the Connector service is running.
sudo systemctl status twingate-connector


Connector configuration

You can find the Connector configuration file in /etc/twingate/connector.conf. The three environment variables in the run command above must be set in the configuration file in order for the Connector service to start and run.

Configuration and management

Connector configuration can be found in /etc/twingate/connector.conf. For the Connector to run, three settings must be present with valid values. For example, if you Twingate account is, your configuration file should look like this:


Connector token values can be generated in the Twingate Admin console by provisioning or re-provisioning a Connector.


Connector tokens

Note that Connector tokens are unique to each individual Connector and they cannot be shared between Connectors.

The following standard commands can be run to manage the systemd Connector service.

# Connector status
sudo systemctl status twingate-connector

# Stop the Connector service
sudo systemctl stop twingate-connector

# Start the Connector service
sudo systemctl start twingate-connector

# Restart the Connector service (eg. for configuration file reload)
sudo systemctl restart twingate-connector

# Start the Connector service automatically at boot
sudo systemctl enable twingate-connector

# Stop the Connector service from starting automatically at boot
sudo systemctl disable twingate-connector

Updated about a month ago


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.