Subscribe

UiPath Automation Suite

The UiPath Automation Suite Guide

Configuring the FQDN post-installation

To update the FQDN of Automation Suite, you need to run the installer again and make the following changes in the cluster_config.json file for all the nodes in the cluster.

  • fqdn - update this field with new FQDN that you need to access the cluster.
  • fixed_rke_address - if this value is identical to the fqdn field in cluster_config.json, then you need to update this value as well to reflect the new FQDN.

📘

Note:

Changing the FQDN also requires new server certificates. If a new certificate is available, you have two options: either continue with the new self-signed certificate configured by the installer automatically, or stop the installation and bring in a new certificate.

You can configure the certificate via the server_certificate field in cluster_config.json.

Updating the FQDN in single-node mode


To update the FQDN in single-node mode, take the following steps:

  1. Navigate to the UiPathAutomationSuite folder (the location of the installer bundle).
  2. Run the following command to update the FQDN:

Online

sudo ./install-uipath.sh -i ./cluster_config.json -o output.json -a --accept-license-agreement

Offline

Run the following command to update the FQDN for the infrastructure:

sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --accept-license-agreement

Run the following command to update the FQDN for the fabric and services:

sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -f -s --install-type offline --accept-license-agreement

📘

Note:

The installer warns you of the consequences of updating the FQDN. It asks for confirmation before proceeding further. The installer also warns you if there is no new valid certificate related to the FQDN.

Updating the FQDN in multi-node mode


To update the FQDN in multi-node mode, take the following steps:

  1. Run the installer on all the machines (server and agent nodes). Note that the order of execution is very important. You first need to run the installer on all the servers, and then on all remaining agent nodes as well as the Task Mining node.

First server node

  1. Navigate to the UiPathAutomationSuite folder (the location of the installer bundle).
  2. Run the following command to update the FQDN:

Online

sudo ./install-uipath.sh -i cluster_config.json -o output.json -a --accept-license-agreement

Offline

Run the following command to update FQDN for the infrastructure:

sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --accept-license-agreement

Run the following command to update FQDN for the fabric and services:

sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -f -s --install-type offline --accept-license-agreement

📘

Note:

The installer warns you of the consequences of updating FQDN. It asks for confirmation before proceeding further. The installer also warns you if there is no new valid certificate related to the FQDN.

Subsequent server nodes

  1. Navigate to the UiPathAutomationSuite folder (the location of the installer bundle).
  2. Run the following command to update the FQDN:

Online

sudo ./install-uipath.sh -i cluster_config.json -o output.json -k -j server --accept-license-agreement

Offline

sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j server --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --accept-license-agreement

📘

Note:

The differences between the command run on the first server node and the one used for the subsequent server nodes are as follows:

  • the -a option - replaced with -k to prevent running the fabric and service installer on any other nodes, which is only necessary for the first server machine.
  • the -j server option - used to differentiate between server and agent node.

Additional agent nodes and Task Mining node

  1. Navigate to the UiPathAutomationSuite folder (the location of the installer bundle).
  2. Run the following command to update the FQDN:

Online

sudo ./install-uipath.sh -i cluster_config.json -o output.json -k -j agent --accept-license-agreement

Offline

sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j agent --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --accept-license-agreement

Updated about a month ago


Configuring the FQDN post-installation


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.