This release contains minor bug fixes.

• Resolved a rare crash when authentication headers would be malformed.

This release contains minor bug fixes.

• Updated the Connector AMI image to patch CVEs and stop alerts from being thrown.

This release contains minor bug fixes and improvements.

• Analytics logs now output to stdout instead of stderr.

• Resolved a memory leak that occurred during Relay discovery.

This release resolves issues that prevented the Connector from working as expected.

• Resolved an issue where the Connector wouldn’t start after reboot on minimal Linux distributions, like Raspbian, that directly set nameservers in /etc/resolv.conf instead of using a stub resolver. The Connector now detects changes to /etc/resolv.conf for better compatibility with these distributions.

• Resolved a memory leak that occurred during Relay discovery.

This release resolves an issue specific to Fedora.

• Resolved an issue preventing the Twingate Connector from being installed on Fedora running on ARM64. Previously, the package's architecture was arm64 instead of the expected aarch64.

This release contains minor bug fixes.

• Resolved various minor bugs.

This release contains minor bug fixes.

• Resolved various minor bugs.

This release contains minor improvements.

• Added support for ARM64 via the AWS AMI.

This release contains minor bug fixes and improvements.

• Resolved various minor bugs.

This release contains minor bug fixes and improvements.

• Resolved a rare issue where a small subset of network events wouldn't be logged.

This release contains minor bug fixes and improvements.

• Added support for running compliance tools and running the Connecter in a K8s pod under the "restricted" security standard. This is also updated for the Helm Chart and K8s Operator.

This release contains minor bug fixes and improvements.

• Resolved an issue where peer-to-peer connections to publicly accessible Connectors would fail when the Client is behind NAT.

• Resolved a rare crash when a nameserver would go down.

• Resolved various minor bugs.

This release contains minor bug fixes and improvements.

• Minor performance improvements.

This release contains minor bug fixes and improvements.

• Minor performance improvements related to ephemeral access.

This release contains fixes that impacted Connector functionality.

• Resolved an issue that would sometimes result in a large amount of memory being used for Relay connections.

• Resolved an issue that would sometimes result in data transfer being throttled during peer-to-peer connections.

• Added support for non-A/AAAA DNS-over-TCP requests that are forwarded to Connectors to be resolved in Remote Networks. Requires an updated Client.

• Resolved an issue that could cause a crash under certain circumstances.

• Various minor bug fixes.

• Resolved various minor bugs.

• Resolved an issue that prevented Connectors from being deployed.

• Removed support for Ubuntu 18.04.

• Resolved an issue where Resource aliases for UDP and ICMP traffic would only resolve for peer-to-peer established connections.

• Resolved an issue where DNS-over-HTTPS queries would fail for TCP-transported DNS requests.

• Various minor bug fixes.

• Improved log readability

• Resolved an issue that could result in subsequent connections to the same resource on different ports instead being routed to the initial port.

• Resolved an issue that prevented freeing up resources for user connections during certain resouce configuration changes.

• Resolved an issue where Connectors on the same AMI image would have the same machine ID.

• Improved the behavior when switching flows between Connectors, resulting in much shorter Connector failover times.

• Improvements to reduce overall system resource usage.

• Resolved various minor bugs.

• Resolved various minor bugs.

• Resolved various minor bugs.

• Improved the recovery behavior when a Connector becomes unreachable, significantly reducing reconnect time to an alternate Connector.

• Resolved a minor issue with Network Analytics to eliminate reporting ambiguity for multiple matching Resource rules.

• Updated the base AWS AMI image to Ubuntu 22.04 LTS.

• Resolved various minor bugs.

• Improved reconnection behavior when network availability is transient.

• Improved debug logging clarity and verbosity.

• Resolved an issue that could cause a crash under certain circumstances.

• Resolved various minor bugs.

• Resolved an issue impacting users assigned a large number of Resources.

• Resolved various minor bugs.

• Added missing AMI images for the previous 1.46.0 release. There is no functional difference between 1.46.0 and 1.47.0.

• Resolved an issue that prevented certain DNS responses from being forwarded from the Remote Network back to the Client machine. Traffic on port 53/UDP (in the Twingate Resource configuration) must be allowed for DNS queries to succeed. Learn more.

• Improved the recovery behavior for peer-to-peer connections on address and network changes.

• Improved connection resilience when the Controller is unavailable.

• Resolved various minor bugs.

• Resolved an issue that could result in the Connector incorrectly reporting relay availability.

• Resolved various minor bugs.

• Reduced the overall data payload size for communication with the controller.

• Introduced support for future metadata reporting capabilities.

• Resolved various minor bugs.

• Disabled randomized case DNS lookups to improve compatibility.

• Improved logging clarity by prefixing lines with log source and level.

• Resolved various minor bugs.

• Improved the selection and fallback logic used for Relay selection across multiple regions and zones.

• Resolved various minor bugs.

• Resolved an issue where sessions would not be revoked immediately under certain circumstances.

• Resolved an issue involving certain types of DNS responses.

• Resolved an issue with analytics data reporting impacting relay metadata.

• Resolved an issue with analytics data reporting impacting clients running in headless mode.

• Resolved various minor bugs.

Note: There is no functional difference between 1.38.0 and 1.40.0, and there is no need to upgrade if you are currently on 1.38.0.

• Improved the resiliency of the connector to temporary controller unavailability.

• Resolved an issue where peer-to-peer connections could timeout prematurely.

• Resolved an issue that could cause the connector to crash under certain circumstances when running as a systemd service.

• Extended the period of time that the Connector attempts to reconnect to our service without manual intervention due to any type of network or service interruption.

• Added jitter to reconnection logic to avoid the “thundering herd” effect during service interruptions.

• Enhanced the Connector heartbeat behavior to provide greater resiliency during service interruptions.

• Resolved an issue where peer-to-peer connections were denied when an unusually large number of Resources is configured.

• The Connector now includes compatibility for Linux-based systems running on ARM silicon architectures armv7 and arm64. This covers all Raspberry Pi devices, many IoT applications, and NAS devices from vendors such as Synology and QNAP.

• Connectors will now connect to multiple relay nodes within a given region for additional resiliency to hardware and network failures.

• Resolved an issue where the connection to the controller could prematurely timeout over unreliable networks.

• Improved the reliability of status heartbeat messages in circumstances where the relay node IP address remained static.

• Improved the security of token storage while the connector is running.

• Added support for peer-to-peer connections via NAT traversal. If a Client also supports peer-to-peer connections, NAT traversal will always be prioritized before falling back to a Relay mode connection.

• Slightly expanded token validity window in situations where clock synchronization on the host device is imprecise.

• Resolved an issue where certain network and DNS errors were incorrectly treated as unrecoverable.

• Reduced the latency required to switch transports to another relay node in the case of failover.

• Additional small fixes, including resolving a minor memory leak and clarifying log messages.

• Added some additional leeway to account for clock synchronization issues on the host environment.

• Resolved a timeout issue that could require a restart under certain circumstances.

• Added support for service accounts and headless clients. Connectors must be upgraded to 1.30.0 or later in order to assign resources to service accounts.

Note: There is no functional difference between 1.26.0 and 1.27.0, and there is no need to upgrade if you are currently on 1.26.0.

• Fixes an issue where ICMP ping requests were incorrectly timing out on some client platforms.

• This release resolves an issue where multiple matching resource rules (for example, a wildcard rule and a FQDN) with different port restrictions could cause an incorrect denial of access for the user’s network connection.

• Connectors now support local real-time output of network analytics to stdout, allowing direct log collection from deployed Connectors. See Connector real-time logs for schema and configuration information.

• Twingate now supports restricting ports for defined Resources.

• Miscellaneous connectivity and analytics bug fixes.

• Improvements to ensure the Connector is always connected to its optimal Relay for performance.

• Fixed a bug in Healthcheck that caused it to always appear unhealthy.

• Support for logging client IP in Network Analytics.

• Latency optimizations for realtime traffic.

• Analytics bug fixes.

• You can now check if the Connector is functioning properly by running a health check.

• Improved Connector logging for debugging purposes.

• Performance and stability fixes.

• Added support for pinging protected Resources.

• Network Analytics bug fixes.

• Fixed an issue where version information was not reported correctly.

• Network Analytics bug fixes.

• Initial Network Analytics release. Prior versions report no network analytics.

• Improved the deployment process in Docker.