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.
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 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.
When a plant's network, its remote access or one of its network devices stops answering, the plant's "Activity" page now shows "Park network offline", "Network device offline", or "Network device mass outage" when many go at once. Each clears itself when the connection returns. Plants receive this with their next agent update.
A WireGuard remote-access server created on a plant now has "Require a pre-shared key" on by default, and the connected site receives an extra generated key alongside its keypair, shown once right after creation. For an existing connection, "Include a pre-shared key" adds, renews or removes the key when its configuration is regenerated.
Starting a network scan on a plant's networking page now opens a dialog where "Scan range (optional)" limits the scan to part of the network and "Overwrite existing names" replaces device names with the latest analysis. Found devices appear in the table while the scan runs, filling in as they are identified.