Font size

Private Cloud: Update

This guide applies to Private Cloud versions 2.4.0 and 2.3.3. If you have the older version, contact our support team at for an upgrade.
To check your Cloud version, go to <https://your Private Cloud instance address>/build.txt in your preferred web browser. To check the version of the installation script, see <the folder containing the installation script>/templates/preload_frontend_build.json.
For version differences, see the release notes.

Upon the release of a new version of Private Cloud, execute the installation script in the update mode to get an upgrade of service components and gain access to all new features.

To update your Private Cloud instance

  1. Open the web browser.
  2. Go to <your instance address>/build.txt.
  3. Check the version listed at the end of the text file, for example:
    Wed Nov 7 12:15:44 2020 +0000 - nnnnnnnnn ; build nnnnnnnn-nnnnnn v2.2.8
  4. Create a backup of your instance.
  5. Download the newest installation script of a Private Cloud edition you are interested in by executing the following command in the Linux terminal on the machine that serves the controller component:
    sudo wget, or
    sudo wget, or
    Request a shipment of Private Cloud Enterprise from our support team
  6. Run the freshly downloaded installation script under superuser, in the update mode:
    sudo ./ update
    By default, the script does not require any arguments, since it gathers all the required information from the /etc/altab file and Private Cloud configuration files. In certain cases (for example, when HTTPS support is enabled via the Elastic Load Balancer proxy), it can be necessary to specify some installer options.

After that, your instance should be updated to the newest version.

In case an issue occurs, then to identify the reason for an issue you have encountered, consult Docker logs, logs of individual components, and installer logs.
To obtain the list of running Docker containers, execute the following command:

sudo docker ps
To collect Docker logs from an individual container running a specific Private Cloud component, you can execute the following command:
docker logs %component name%
If the command output is too extensive, try trimming it to the last 100 rows:
docker logs %component name% --tail 100
The installation script logs are located in /tmp/alc_installer.log by default.
If a problem occurs with the Private Cloud instance and none of the options described below helps, please contact our support team at and provide them with the list of running containers and their logs to find a solution.
If a problem occurs with the installation script, provide the list of running containers, and the logs of the controller component and installation script.

How can we improve this article?