Updating a node using the CLI
10st Okt 2023 – Radix Node v1.0.4 released
We renamed the binary filename from
When updating your node, care should be taken to ensure the update goes smoothly. These instructions use the
babylonnode CLI tool for an easy update process.
First, if you haven’t already done so, ensure that you have backed up your
node-keystore.ks key file. This key file contains the private key that determines your node’s unique address and (if you are running a validator node) validator ID. If anything goes wrong in the update process, if you have your key file, you can always reinstall the node from scratch and use it to recover access to your node.
Next, you may want to consider using a backup node to perform a switch to the updated node with minimal interruption (especially if running a validator node) – or to provide a quick recovery if something goes wrong during the update. See our recommendations for Maintaining Uptime for more.
To upgrade your node using CLI
babylonnode docker install --update
If upgrading to version 1.1.0, then install Java 17 either by running
Run below command to upgrade your node.
babylonnode systemd install -u
-uoption specifies that this launch of the node will be an update, causing
babylonnodeto create a backup of the current configuration file and ensure that the node has stopped before applying the changes.
Optional - The
-rspecifies the release of the node software you wish to install. If not provided it will use the latest release from https://github.com/radixdlt/babylon-node/releases.
Optional - The
-ioption is the external IP address of your server.
-toption is the IP address of a Radix node that you can use to join the network. On executing the command, the script will download the configuration file from the specified node and attempt to make a connection. Select any node IP from the closest region to your node from the list below: