Skip to main content

Updating Devices

You can update the Meshr agent on any online device straight from the dashboard — no need to SSH in and run the upgrade by hand. The agent applies the update and restarts into the new version, and the dashboard confirms the version it actually landed on.

Updating from the dashboard​

  1. Open Peers, then click the device you want to update to open its panel.
  2. Scroll to the Maintenance section.
  3. Click Check & update.

There's a single button for the whole flow:

  • If the device is behind the latest version, the button reads Update to vX and queues the update.
  • If the device is already current, the button reads Check & update and confirms it's up to date without changing anything.

The device picks the action up on its next check-in (about a minute), applies it, and restarts. The Maintenance panel refreshes on its own — you don't need to reload the page.

What the statuses mean​

The Maintenance panel walks through the update lifecycle so you always know where things stand:

StatusWhat it means
Update queuedThe action is queued. The agent picks it up on its next check-in (~1 min).
Applying updateThe agent received the action and is downloading and installing the new binary.
RestartingThe new binary is installed; the agent is restarting into it. The panel confirms once it reports the new version.
Updated to vXDone — the device restarted into the target version and confirmed it.
Agent is up to dateThe device was already on the latest version; nothing changed.
Update stuckThe agent hasn't confirmed the new version after about 10 minutes.
Update didn't complete / failedThe update couldn't finish; the device is still on its previous version.

The "Updated to vX" confirmation reflects the version the agent actually reports after restarting — not just that the request was sent — so you can trust it without checking twice.

If an update gets stuck​

If a device sits in Update stuck (no confirmation after ~10 minutes), the agent hasn't reported the new version. Click Cancel in the Maintenance panel to clear the queued action, then check the device and try again. Cancelling doesn't roll anything back — it just stops waiting on an action the agent never confirmed.

If an update fails​

When an update can't complete, the panel shows a clear failure and the device stays on its previous version (your connectivity isn't affected). To dig in:

  1. Open the device's Logs tab to see what the agent reported around the update attempt.
  2. Make sure the device is online and reachable.
  3. Click Check & update again to retry.

If retries keep failing, see Troubleshooting or update the agent directly on the device with the package manager you installed it with.

Updating on the device itself​

You can always update locally instead of from the dashboard:

meshr update

This is the same operation the dashboard triggers — the agent applies the update and restarts into the new version.

Updating with your package manager works too and behaves the same way:

sudo apt update && sudo apt upgrade meshr

Your mesh connection during updates​

Updating the agent no longer drops your mesh. When a new version is applied, the agent hands the network over to itself in place and updates around the live tunnel — in-flight connections keep flowing while the new binary takes over. An SSH session, a file transfer, or a tunnel running through the device stays up across the upgrade instead of blinking out.

Seamless upgrades start from v0.7.85

The upgrade you run to reach v0.7.85 may still cause a brief blip, because the older version being replaced doesn't yet know how to hand off the tunnel. Every upgrade from v0.7.85 onward is seamless — once a device is on v0.7.85 or later, future updates keep the mesh connection up. So the first hop into this behavior can flicker; every hop after it won't.

  • Troubleshooting — diagnose connection and agent issues
  • CLI reference — every meshr command, including meshr update
  • Peers — the device list and per-device panel