- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to Troubleshoot Services During Installation
- How to Uninstall the Cluster
- How to clean up offline artifacts to improve disk space
- How to disable TLS 1.0 and 1.1
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bucket
- How to debug failed Automation Suite installations
- How to disable TX checksum offloading
- Unable to run an offline installation on RHEL 8.4 OS
- Error in Downloading the Bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- SQL connection string validation error
- Failure After Certificate Update
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Cannot Log in After Migration
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Kinit: Cannot Find KDC for Realm <AD Domain> While Getting Initial Credentials
- Kinit: Keytab Contains No Suitable Keys for *** While Getting Initial Credentials
- GSSAPI Operation Failed With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis Probe Failure
- RKE2 Server Fails to Start
- Secret Not Found in UiPath Namespace
- ArgoCD goes into progressing state after first installation
- Unexpected Inconsistency; Run Fsck Manually
- Missing Self-heal-operator and Sf-k8-utils Repo
- Degraded MongoDB or Business Applications After Cluster Restore
- Unhealthy Services After Cluster Restore or Rollback
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs

Automation Suite Installation Guide
Configuring the FQDN post-installation
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 thefqdn
field incluster_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 theserver_certificate
field incluster_config.json
.
To update the FQDN in single-node evaluation mode, take the following steps:
- Navigate to the
UiPathAutomationSuite
folder (the location of the installer bundle). - Run the following command to update the FQDN:
Online
sudo ./install-uipath.sh -i ./cluster_config.json -o output.json -a --accept-license-agreement
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
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
sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -f -s --install-type offline --accept-license-agreement
To update the FQDN in multi-node HA-ready production mode, take the following steps:
There are some variations between the commands you run on the first server node, those you execute on the subsequent server nodes, and those you use on agent nodes, as follows:
- The
-a
option is exclusively for commands executed on the first server node. This is where you must run the fabric and service installer. - The
-k
option specifically applies to commands run on the following server nodes, and it skips the execution of the fabric and service installer. - The
-j server
option is used to distinguish between server nodes and agent nodes.