Updating UHost

The server's Updates section says which release you run and whether there is a newer one. A release is shown either as a newer release or as a release that fixes something, which is the distinction worth acting on: the second kind is a security release and should not wait for a convenient afternoon.

Alongside it are the date the release was Published and when this server Last checked. A server that has never asked says so plainly rather than implying it is up to date.

Every installation is offered every release, whatever plan it is on and whether it has a licence key at all. A server on the free plan is offered the same security release as a Business one, on the same day. Gating a security fix behind a payment would make the unpatched servers somebody else's problem as much as their owner's.

1. You press Install. Nothing installs on a timer, and no release installs itself.
2. The archive is checked against UHost's signature and refused if it does not match. An archive that arrived from anywhere else, or was altered on the way, does not install.
3. The panel snapshots its own state before it changes anything.
4. If the update fails, it tries to put the snapshot back rather than leaving a half-updated panel.

Websites keep serving throughout. Updating the panel is not the same as restarting what it hosts.

Asking whether there is a newer release sends this installation's own identifier, the version it runs, and whether it is an amd64 or arm64 machine. That last one decides which archive you are offered, because a release is built for one kind of machine and the wrong one would download in full and then be refused.

No licence key is sent, deliberately: asking about a release needs no licence, which is what makes the previous section true. The panel's own Updates page lists these fields as well, and a build check keeps that list matching the code.

How the panel is put together, and why an update can be trusted at all, is on the security page.