Skip to content

August 2026

Changes released in August 2026.

Open in the full timeline

Web appFeatureNetwork & remote access

An organization's VPN can now be moved to another host

An organization's VPN row now has a "Move to another host" action. Before the move is confirmed, it shows where the VPN would land, how many plants restart on site and lose data briefly, which plants get a new VPN address, and which routers keep the old one and stay disconnected until restarted.

mirox 2.15.376 – 2.15.393
Read more in the documentationDirect VPN
Web appFeatureNetwork & remote access

A plant's VPN tab now shows when remote access is not running

Each remote-access connection on a plant's VPN tab now shows whether it is really working, rechecked while the tab is open. One that is set up but not running is marked red, with the next step to take, and one that is running while the remote site has not connected is marked amber.

mirox 2.15.330 – 2.15.339
Read more in the documentationDirect VPN
Web appImprovements and fixesNetwork & remote access

Remote-access connections a plant dials out to now show as much as the ones it accepts.

  • A remote-access connection the plant dials out to now shows its remote site under the name it was given, with a throughput chart.
  • When a VPN is added, an IPsec configuration file can now be uploaded and its values filled in.
  • A plant's OpenVPN remote access offered over IPv6 now accepts connections from IPv6 clients.
  • Connected clients on a plant's VPN tab are now named after their protocol, instead of a guess at the device at the far end.
  • Long lines in a VPN log now scroll sideways inside the window instead of running off the edge.
mirox 2.15.330 – 2.15.339
Read more in the documentationDirect VPN
Web appFeatureMajorNetwork & remote access

IPsec remote access now shows whether the site is connected

Remote access over IPsec (IKEv2), for site routers that speak nothing else, now shows whether the remote site is connected, with its availability and traffic, instead of an unknown state. A site set up but never connected stays in the list, and "Add peer" attaches a second router.

mirox 2.15.291 – 2.15.295
Read more in the documentationDirect VPN
Web appImprovements and fixesNetwork & remote access

Remote access to a plant now survives a move of its on-site agent. For connections Mirox hosts, OpenVPN is now suggested instead of WireGuard.

  • Remote access to a plant survives a move of its on-site agent: the address stays the same and the agent reconnects by itself.
  • For plants whose remote access Mirox hosts, OpenVPN is now suggested instead of WireGuard, and each option explains the reason.
  • A half-finished VPN wizard is now kept as a draft and restored when it reopens for the same plant.
  • A site connection can now be given its own name when it is added or edited, instead of the suggested one.
mirox 2.15.279 – 2.15.290
Read more in the documentationDirect VPN
Web appFeatureMajorNetwork & remote access

Remote access can now be set up over IPsec (IKEv2)

The "Add a VPN connection" wizard now offers "IPsec (IKEv2)" beside WireGuard and OpenVPN, for industrial routers that speak nothing else. Mirox can host the tunnel for the plant or connect to a router that hosts it, with a pre-shared key that is generated or pasted.

mirox 2.15.274 – 2.15.278
Read more in the documentationDirect VPN
Web appBreaking changeMajorNetwork & remote access

The "VPN auto-heal" wizard is replaced by "Start AI diagnosis"

The "VPN auto-heal" wizard can no longer be started, while a run started earlier still opens. A plant's VPN connection is now diagnosed from "Inspect VPN connection" on the plant, where "Start AI diagnosis" takes the router on site and what is needed and lets the assistant read the configuration and the logs itself.

Action required: Anyone who used the "VPN auto-heal" wizard: start the diagnosis from the plant instead. Open the plant's networking page, choose "Inspect VPN connection" on the VPN, go to its diagnosis step, name the router on site and what you need, and carry on with the assistant in the tab it opens. Starting a new auto-heal run is refused from this release; runs you started before it stay readable.

mirox 2.15.253 – 2.15.260
Web appImprovements and fixesNetwork & remote access

The personal VPN now follows the technical role held on each plant. Plants with no AC limit configured now get a 5-day forecast.

  • Every plant on which a technical role is held now appears under "Reachable subnets" in the profile, including one shared by a partner.
  • An "Asset Manager (Commercial)" no longer reaches plant equipment: no subnets on their VPN, and no changes to a device's "Web Targets".
  • A meter's own reading now counts for today and for a plant's first days, instead of looking like a data logger fault.
  • Plants with no AC limit configured now get a 5-day forecast and expected values — uncapped estimates, flagged as such under "Expectation comparison".
  • Editing a network device from its details no longer leaves the page unclickable until it is reloaded.
  • The creator or assignee of a ticket now receives its notifications even while the plant is muted, unless the ticket itself is muted.
mirox 2.15.166 – 2.15.172
Read more in the documentationVPNProxyNotifications
Web appFeatureNetwork & remote access

The assistant explains and diagnoses a plant's remote access

The assistant now answers a question about a plant's remote access with every connection: its role, protocol, the sites it connects, the networks it routes, and each one's last known status. Where something looks wrong, it names a likely cause.

mirox 2.15.134 – 2.15.143
Read more in the documentationDirect VPNVPN service
Web appFeatureMajorNetwork & remote access

Remote access now shows live status, diagnosis and network tools

Three tabs beside the logs — "Live status", "Diagnose" and "Debug" — show whether a plant's remote access is working. "Live status" shows each connection's address, throughput and how long ago it last checked in, updated once a second.

mirox 2.15.130 – 2.15.133