Upgrade Appsmith Versions

This page explains how to update your self-hosted Appsmith instance to the latest version.

Prerequisites

Before you update, make sure that:

1. You have at least 2 GB of free storage for the backup and update.
2. Your embedded or external MongoDB server runs version 5.0 or later. To upgrade MongoDB, check the supported platforms and follow the MongoDB replica set upgrade guide.
3. You have a backup of your Appsmith instance. To create one, follow the Backup instance guide.

Update Appsmith

Select your platform and follow the steps to update Appsmith to the latest version:

Docker

These instructions apply to Docker-based platforms, such as Docker standalone and AWS AMI.

Important

Some versions are checkpoints that you must install before you upgrade further:

• If your current version is earlier than v1.9.2, follow the Upgrade to Checkpoint Version (v1.9.2) guide before you update to the latest release.
• If your current version is later than v1.9.2 but earlier than v1.96, upgrade to a version between v1.96 and v1.99 before you upgrade to v2.0 or later.

1. Find your Appsmith installation directory:

   docker inspect -f '{{ (index .Mounts 0).Source }}' <APPSMITH_CONTAINER_ID>

2. Choose the Appsmith version you want to run.

   Find its release tag on GitHub.

3. Open docker-compose.yml in that directory and set the image for the Appsmith service to a pinned tag, for example:

   image: index.docker.io/appsmith/appsmith-ee:<version>

   If you use the Community Edition, replace appsmith-ee with appsmith-ce and keep the same :<version> suffix.

4. Pull the image and restart the container. The new container runs the version set in docker-compose.yml.

   docker-compose pull && docker-compose rm -fsv appsmith && docker-compose up -d

Kubernetes

Important

If your current version is earlier than v1.9.2, follow the Upgrade to Checkpoint Version (v1.9.2) guide before you update to the latest release.

Note: These instructions assume you followed the Kubernetes installation guide exactly. If you changed any defaults, such as the Helm release name or namespace, adjust the commands to match.

1. Choose the latest Appsmith version.

   Find the latest release tag on GitHub.

2. Locate your Helm values.yaml file.

   • If you still have the values.yaml file from your initial installation, go to its directory:

     cd /path/to/your/values-file
   • If you no longer have the file, retrieve it from your cluster:

     helm get values appsmith-ee -n appsmith-ee | grep -v "USER-SUPPLIED" > values.yaml

3. Update the image tag in values.yaml.

   • If you have yq installed:

     APPSMITH_VERSION=<version>
     yq -i ".image.tag = \"$APPSMITH_VERSION\"" values.yaml
   • If you don’t have yq, open values.yaml in a text editor and set the new version:

     image:
       tag: <version>

4. Apply the upgrade with Helm.

   Run the following command:

   helm upgrade appsmith-ee -n appsmith-ee -f values.yaml

AWS ECS on EC2

1. Sign in to your AWS account and open the Amazon ECS console.
2. Select the cluster that contains the container instance you want to update.
3. Stop the task. ECS automatically deploys a new task.
4. Verify that the updated version is running.

Azure Container Instance

1. In the Azure portal, find the Azure Container Instance that runs Appsmith.
2. Click Restart to restart the container.

DigitalOcean

Important

If your current version is earlier than v1.9.2, follow the Upgrade to Checkpoint Version (v1.9.2) guide before you update to the latest release.

1. Connect to your Droplet over SSH and go to the Appsmith installation directory:

   cd /root/appsmith

2. Choose the Appsmith version you want to run.

   Find its release tag on GitHub.

3. Open docker-compose.yml and set the image for the Appsmith service to a pinned tag, for example:

   image: index.docker.io/appsmith/appsmith-ee:<version>

   If you use the Community Edition, replace appsmith-ee with appsmith-ce and keep the same :<version> suffix.

4. Pull the image and restart the installation. The new container runs the version set in docker-compose.yml.

   docker-compose pull && docker-compose rm -fsv appsmith && docker-compose up -d

Troubleshooting

If the update fails, roll back to the previous version by following the Restore instance guide. If the problem persists, contact support using the chat widget in the bottom-right corner of this page.

See also

• Upgrade checkpoints: Learn about releases that you must install and run before you can upgrade past them, and what to do if the server does not start after an upgrade.
• Schedule automatic updates for Appsmith installation: Learn how to schedule automatic updates to keep your installation up to date.