Agent updates

MoorNest never updates agents on its own. When a new agent release is available, you decide when each server takes it: one server, one client or all of them at once. The agent installs the update only when it is idle, checks the update's signature first, and rolls itself back if the new version does not connect.

See which servers can update

• A server that can take a newer agent shows Update available next to its status.
• The Agent column on Servers shows each server's version, with Update available, Updating or the result of its last update.
• Home says how many servers can take a newer agent.
• Server details shows Agent version, Latest release and Last update.

Only administrators can update agents. Each update asks for a fresh code from your authenticator app.

Update one server

1. Open the server and click Update agent.
2. Confirm, then enter a fresh code.

The server page then says the update is authorised and installs when the server is idle. When the agent has updated, Last update shows Installed.

Update all servers

On Servers, click Update all agents. The button shows how many servers can take the update. If you picked one client in the client switcher at the top, only that client's servers are updated. Confirm, then enter a fresh code.

Servers whose agent rolled back or refused this version are left out.

How an update is installed

• Authorising an update opens a 24-hour window for the version on offer. A server that is off or offline takes it if it reconnects within those 24 hours.
• The agent checks for an update every 5 minutes, and only while no backup or restore is running. It never updates in the middle of a job.
• It downloads the new program and checks it before installing: on Windows, a valid Authenticode signature from DevSmooth Software Inc.; on Linux, an Ed25519 signature from the MoorNest release key.
• It keeps the current program, swaps in the new one and restarts the service.

To stop an update that has not been installed yet, click Cancel update on the server page.

Automatic rollback

The new version must connect to MoorNest within 5 minutes, in at most 3 starts. If it does not, the agent puts the previous program back and reports Rolled back. Last update shows the reason.

An agent that rolled back or refused a version does not try that version again. The next release can be offered to it as usual.

You can also roll back by hand on the server. Run this as administrator on Windows, or with sudo on Linux:

& "C:\Program Files\MoorNest\moornest-agent.exe" rollback

sudo /opt/moornest/moornest-agent rollback

It restores the program the last update replaced and restarts the service. The removed version is not installed again until a different one is offered.

Update by hand

If a server cannot take an update from the console, run the latest download on it. Server details > Update by hand shows the commands. On a server that already has the agent, the installer updates it in place and keeps its registration, so no install code is needed.

On Windows, in PowerShell:

[Net.ServicePointManager]::SecurityProtocol='Tls12'; iwr -UseBasicParsing https://app.moornest.com/downloads/moornest-agent-windows-amd64.exe -OutFile moornest-agent.exe; .\moornest-agent.exe install

On Linux:

curl -fsSLO https://app.moornest.com/downloads/moornest-agent-linux-amd64 && sudo sh -c 'chmod +x moornest-agent-linux-amd64 && ./moornest-agent-linux-amd64 install'

Things to know

• Updates do not go backwards: you cannot move a server to an older agent from the console.
• A server whose agent was installed the older way shows Installed the older way under Agent version. It cannot update itself: use Reinstall the agent to switch it to the current installer. See Add a server.