A device's web interface opened through remote device access now appears under a header with the device's name, the time left on the second-factor confirmation, and controls for its stored login. The second-factor dialog appears in the page itself.
The plant's Site VPN cards now show a traffic panel per tunnel, with received and sent data on one scale and the connection state over it, following the page's time window. Up to three days shows a curve, up to ninety days a bar per day, and beyond that a bar per month.
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 to a plant can now be handed to an external technician as a link with its own password, without an account. The page behind the link provides the connection file, shows whether the connection is live, and lets the technician read the server's settings and log and test their own side.
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.
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.
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.
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.
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 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.
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.