Skip to content

Changes in Release 1.129 (2026/09/20)

Partner Portal

  • New: A Subscription Expansion Quote can be billed from a past date, so users added weeks ago can still be quoted and invoiced from the day they joined.
  • Changed: A quote is binding for six weeks instead of two, and ordering it bills exactly what it quoted — an order is no longer refused because discounts or seat counts have moved on since.
  • Changed: Several quotes can be open on one subscription at the same time, and ordering one no longer withdraws the others.
  • Changed: The tenant panel and the Subscriptions table now show billed seats — users with a device seen in the last 30 days — instead of every user account on record.

Admin Console

  • Changed: On a single-column Dashboard, cards stack at their own height instead of leaving gaps, and the News card can be shrunk to half width.
  • Changed: The Dashboard compares seats in use against licensed seats using the billed user count, so it agrees with the subscription.
  • Fixed: The first destination added to a policy did not reach the policy's clients until a second destination was added.

Agents

  • Changed: A UDP relay session now survives occasional packet loss instead of being torn down and rebuilt, and relays use far less CPU per packet, so relayed connections through a busy relay are markedly more stable.
  • Fixed: On macOS, an agent update could leave the Mac without the client user interface until the next logout or restart.
  • Fixed: Switching to an account in another environment could leave the agent inactive, with only a service restart bringing it back.
  • Fixed: Two devices behind the same public IP address could stay permanently relayed instead of connecting directly.
  • Fixed: A relay could stop handing out UDP relay sessions altogether until it was restarted, leaving every client on the slower HTTPS relay.
  • Fixed: A device whose UDP path to a relay was blocked stayed on the HTTPS relay for as long as the client ran, even once the block was lifted.
  • Fixed: The LANCOM add-in could block every firewall in a project from receiving any configuration, and the agent it rolled out could end up with no network access.