Twingate Connectors run either within a Docker containers or as a Linux systemd service. Upgrading Connectors varies depending on the platform they are deployed on, but the same principles apply in all cases:
Upgrade one Connector at a time in a redundant pair. Because updating a Connector involves bringing it down, to avoid downtime for users, at least two Connectors should be deployed in each Remote network in your Twingate configuration. Multiple Connectors deployed within the same Remote network are automatically clustered for load balancing and redundancy. When upgrading, update one Connector at a time.
Maintain the same access and refresh tokens when upgrading a Connector. Connectors are uniquely identified by the tokens individually assigned to them. When upgrading a Connector, ensure that these tokens are retained during the upgrade process, otherwise new tokens will need to be provisioned.
Updated 11 days ago