Help Center/ Cloud Bastion Host/ User Guide/ Resource/ Managing Application Resources/ Installing an Application Server/ Upgrading the RemoteApp or app_publisher Program
Updated on 2026-07-30 GMT+08:00
View PDF
Share

Upgrading the RemoteApp or app_publisher Program

After a bastion host instance is upgraded, you need to upgrade RemoteApp on Windows application servers or app_publisher on Linux application servers to the new version. Otherwise, the application publishing function cannot work properly. This section describes how to upgrade RemoteApp and app_publisher.

The procedure for upgrading RemoteApp and app_publisher is as follows: Uninstall the old version and then install the new version.

Prerequisites

Upgrading RemoteApp (for Windows Application Publishing Servers)

  1. Log in to the Windows application publishing server, choose Control Panel > Programs > Programs and Features, and uninstall the earlier version RemoteApp.

    Log in to the bastion host instance and choose Resources > Application > AppServer to view the Windows application server address.

  2. After the uninstallation, upload and decompress the new version RemoteApp installation package.
  3. Double-click setup.exe in the decompressed package to start the installation and complete the installation.

Upgrading app_publisher (for Linux Application Servers)

  1. Log in to the Linux application publishing server, upload the app_publisher installation package of the new version, and decompress it.

    tar -zxvf app_publisher_V1.xxxxxxxxxx.tar.gz

    Log in to the bastion host instance and choose Resources > Application > AppServer to view the Linux application server address.

  2. Run the following commands to uninstall the Docker image of the earlier version: 

    docker rmi 127.0.0.1:5000/psm-kingbase:1.0 127.0.0.1:5000/psm-gbase8a:1.0 127.0.0.1:5000/psm-dameng:1.0 127.0.0.1:5000/psm-firefox:1.0

    An error message that may occur during uninstallation:

    Error response from daemon: conflict: unable to remove repository reference "127.0.0.1:5000/psm-firefox:1.0" (must force) - container xxxxxx is using its referenced image xxxxxxxx

    If this error message is displayed during uninstallation, there is a container session related to the image. Run the following command to delete the container session: You need to delete all container sessions related to the image before uninstalling the image.

    docker rm -f Container ID or container name

    In the preceding command, the container ID or container name is the value of xxxxxx following container in the error message. Use the actual value in your command.

  3. Run the following command to check whether the Docker image is uninstalled: 

    docker images
    • If the command output is empty, as shown in Figure 1, the uninstallation is complete.
      Figure 1 Docker image uninstalled
    • If client information is displayed, as shown in Figure 2, go to 2 and uninstall the Docker image again.
      Figure 2 Docker image uninstallation not completed

  4. After the uninstallation is complete, run the following commands to install the installation package and image in the app_publisher directory of the new version: 

    1
2
    		 
    cd app_publisher_V1.xxxxxxx
./install.sh

  1. (Optional) Update the authentication credential of the application server if your bastion host and application publisher are upgraded to V3.3.68.0 or later (The Authentication Credential field is required for application servers in V3.3.68.0 and later):

    1. Log in to the Linux server as user root.
    2. Run the following command to generate an authentication credential: 
      bash /etc/docker/gen_cert.sh
    3. Run the following command to obtain the authentication credential: 
      bash /etc/docker/get_auth_code.sh
    4. Log in to your bastion host system and choose Resource > Application > AppServer.
    5. In the Operation column of the target application server, click Manage to go to the details page.
    6. In the Basic Info area, click Edit on the right. On the displayed page, update the authentication credential to the one obtained in 5.c.