Updates
Release, support period and how MuteCloud updates itself, with signature checks and a way back.
Release and support
MuteCloud is available since October 2026 and receives active support at least until October 2027: bug fixes, security fixes, updates for new Minecraft and server versions and help when something does not work. The support period will be extended, not shortened.
Support happens on Discord. Every server that runs on MuteCloud is motivation to keep going, so feel free to drop by and show your network, even without a problem. Feedback helps, and feature requests are always welcome: they are all read, and many of them get built.
Keep MuteCloud up to date
Install new versions promptly. Updates carry bug fixes and security fixes, and support always
starts from the current release: if a problem comes up, the first step is update install,
since the issue is often already fixed. Reports from outdated versions can only be looked at
once the network runs the current one.
Checking and installing
update look for a newer version
update install fetch it and put it in place
update rollback go back to the previous binaryThe cloud checks on its own as well:
[update]
channel = "stable"
check = true
interval_hours = 24A new version raises the update-available alert. Nothing is installed without being
asked. Once a day the cloud also sends usage statistics: version, system, the number of nodes,
groups and servers, and player counts (online now, peak and distinct players over the last 24
hours and 7 days). The server's IP address is stored along with them. Player names, UUIDs,
passwords and settings are never sent. telemetry shows exactly what is sent, telemetry off
turns it off.
Every download comes with a signature that is verified against the built-in public key before anything is written. A download that fails the check is discarded.
What happens on disk
The new binary is written next to the current one as mutecloud.new. On commit the
current one is renamed to mutecloud.old and the new one takes its place. That is why
exactly one previous version is available for a rollback, the one you were running
before.
Installing does not restart anything by itself. The cloud tells you that the node has to be restarted, and you pick the moment:
sudo systemctl restart mutecloudThe game servers keep running while the cloud restarts. They are separate processes, their bridge reconnects afterwards, and players stay online.
Going back
update rollback
sudo systemctl restart mutecloudIf there is no previous version on disk the command says so and changes nothing.
In a cluster
Update the leader first, then the workers, and do not leave them apart longer than the update takes. Leader and worker speak the same protocol version; a wide gap between them is the classic cause of a network that looks healthy and does nothing.