Skip to content

Changelog

Every change to Mirox, grouped by month. Filter by group or by kind of change.

Clear filters

November 20261

October 20262

September 20265

Web appFixNetwork & remote access

Remote-access shares now stay open until the chosen expiry

A remote-access (VPN) share no longer closes by itself one hour after the technician's connection comes up. It stays available until the expiry chosen when sharing, or until it is revoked.

mirox 2.15.533
Web appImprovements and fixesNetwork & remote access

Remote-access routes are now listed in the order they are used. Each column can be filtered, each subnet shows its name and tags, and a conflict names the other plant it is with.

  • One plant can be made the winner of every subnet conflict it is in, in a single step.
  • On the "Metrics" tab, "Revert" in the chat undoes a figure the assistant put into the editor.
  • One of an organization's own figures can be averaged across a plant's components, with "By peak power" offered as a ready-made option.
  • Opening a page while the app is moving to a new version now waits for it to finish instead of showing an error.
mirox 2.15.497 – 2.15.503
Read more in the documentationDirect VPNMy metrics

August 20265

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 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 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

July 20261

June 20264

May 202613

April 20266

March 20264