RunCloud is a cloud server management tool that helps you manage your web applications and servers easily. However, sometimes RunCloud may not be able to update your server automatically due to a few reasons, such as network issues, firewall settings, or package conflicts.

If your server is not running the latest version, you will see a warning message on your RunCloud dashboard that says “Server not running latest agent”.

This warning means that your server is running an outdated version of the RunCloud agent. Running an outdated agent may cause some features to not work properly, or some security vulnerabilities to remain unfixed. To fix this issue, you need to update the RunCloud agent manually by using SSH.

Updating the RunCloud Agent

To update the RunCloud agent manually, follow these steps:

  1. Log in to the server connected to your RunCloud account via SSH.
  2. Once you are connected to your server, run the following command to update your system packages:
apt update && unattended-upgrade -d

This command will check for any available updates and install them automatically without prompting you for confirmation.

  1. Next, you need to run one of the following commands to update the RunCloud agent depending upon your server choice.

For Nginx servers, you need to run the following command:

apt upgrade runcloud-agent -y

This command will upgrade the RunCloud agent to the latest version.

If you are running OpenLiteSpeed as your web server, you need to use a different command to update the RunCloud agent. The command is:

apt upgrade runcloud-agent-lsws -y

For Docker servers on RunCloud, you need to run the following command to update the agent:

apt upgrade runcloud-agent-docker -y
  1. Finally, run the following command to restart the RunCloud agent:
service runcloud-agent restart

This command will restart the RunCloud agent so that it can apply the changes and sync with the RunCloud API.

Troubleshooting

You might face an error on older versions of Ubuntu when trying to update the package lists. The error messages indicate that the system is attempting to access outdated or moved repositories. This results in a failure to fetch the necessary data, as the specified repositories no longer have a release file available.

To resolve the issue with the MariaDB repository on Ubuntu, you can follow these steps:

  1. Use your preferred text editor to open the sources list. For example, you can use nano: sudo nano /etc/apt/sources.list
  2. Locate the lines that contain repository URLs that are causing the error. They will look something like this: deb [arch=amd64,arm64,ppc64el] http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.2/ubuntu bionic main
  1. Comment out these lines by adding a # at the beginning of each line. It should look like this after the change:
    # deb [arch=amd64,arm64,ppc64el] http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.2/ubuntu bionic main
  2. Save the file and exit the text editor. If you’re using nano, you can save by pressing Ctrl + O and exit by pressing Ctrl + X.
  3. Update the package list with the new repository settings: sudo apt update

After performing the above steps, you can go back and update your RunCloud agent again. Once you have successfully updated the RunCloud agent, you can enjoy the full benefits of RunCloud and manage your web applications and servers with ease.

If you have any other questions or need help – please feel free to get in touch with our 24/7 support team. We’re here to help!