Updating a node using the CLI

27th Jun 2022Radix Node 1.3.3 released

Use the radixnode CLI to update your node or install a new node from scratch – or refer to the update instructions for Docker or systemd install methods.


When updating your node, care should be taken to ensure the update goes smoothly. These instructions use the radixnode CLI tool for an easy update process.

1. Prepare to update

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.

2. Update your node

  • docker mode

  • systemd mode

To upgrade your node using CLI 1.3.2 or later versions, it is required to create a config file.

You may have this already if you installed or updated using CLI 1.3.2 or above, else you’ll need to create it using the config command in DETAILED mode, by following the CLI install node documentation.

Once you the config file created, run the setup command as below, with the --update flag.

The configuration file includes a version number. If the CLI is updated to use a new configuration version, it may prompt you to manually migrate the configuration file to the new version. Instructions to perform this manual migration will live in the release notes of the CLI.

radixnode docker install --update
  1. Optional - Use parameter -f <path to config.yaml> if the config file is different from the /home/ubunu/node-config/config.yaml.

  2. Optional - Use paramter -a or --autoapprove to run this command without any prompts. It is only recommended for automation purpose.

  3. Use parameter -u or --update to deploy latest versions of software.

If upgrading to version 1.1.0, then install Java 17 either by running sudo apt install -y openjdk-17-jdk or run cli command radixnode configure systemd

Run below command to upgrade your node.

radixnode systemd install  \
     -u \     (1)
     -n fullnode \      (2)
     -r 1.3.3 \   (3)
     -i \    (4)
     -t radix://rn1qgf0tug4nmxfa7su8zsu8pejzq48eeglvxf8le09cuy0nsghzg44weacz2q@    (5)
1 The -u option specifies that this launch of the node will be an update, causing radixnode to create a backup of the current configuration file and ensure that the node has stopped before applying the changes.
2 The -n option sets the node type and supported value is fullnode. archivenode is no more supported from versions 1.1.0 onwards for node software
3 The -r option is optional and specifies the release of the node software you wish to install. If not provided it will use the latest release from https://github.com/radixdlt/radixdlt/releases.
4 The -i option is the external IP address of your server.
5 t 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:
  • Mainnet Seed Nodes

  • Stokenet Seed Nodes

EU (west)
US (east)
EU (west)
US (east)
AP (south)