Skip to content

Changes in Release 1.124 (2026/08/16)

Admin Console

  • New: An exit node now has an Exceptions tab for destinations that should bypass it and go out over the client's own internet connection. Pick maintained vendor presets — Teams, Exchange Online, SharePoint and OneDrive, Microsoft 365, Google Meet, Zoom and Webex — or add custom networks. This mainly helps meeting traffic, which is routed to a nearby front door and loses that advantage when it is tunnelled through a distant exit node.
  • New: Subnets have the same Exceptions tab, for destinations inside the routed range that should be reached over the client's own connection instead of through the subnet's gateway asset.
  • Changed: Access Diagnosis now shows the status, security posture and domain or management state of the selected client, along with details of the chosen destination.
  • Fixed: The antivirus and firewall selection of a macOS OS condition offered the Windows product list by mistake.
  • Fixed: The minimap could move the view off the diagram on the policy and Access Diagnosis canvases.

Agents

  • Fixed: On Windows, a client that started before the taskbar was ready after logon failed to register its tray icon and came up as a blank window that could neither be used nor closed.
  • Fixed: On macOS, routes left behind by an agent that did not shut down cleanly could keep the client from connecting on a different network, and could remove that network's default route.
  • Fixed: With an exit node active, a client could lose contact with the Admin Console and appear offline, because not all XplicitTrust service addresses were kept on the local connection.
  • Fixed: A client or asset connected through a relay could lose its tunnel repeatedly while still being shown as online, and afterwards stayed on the slower relay path for up to an hour.