Updating version on AWS

[buoyant barn]

Need help with updating my Appsmith version on my EC2 instance on AWS. I have found the page:

https://docs.appsmith.com/getting-started/setup/instance-management/update-appsmith#update-on-aws-ecs-ec2

But I don't know how to navigate to clusters/tasks that it (and other pages) refer to. I can stop and start my instance, but I don't see an option to "deploy a new task automatically". I guess I need more detailed instructions on how to update the version when running in an EC2 instance.

Thank you,

Randy

[scarlet heart]

To update your Appsmith version on an EC2 instance using AWS ECS, follow these steps:

1. Log in to AWS: Access your AWS account and navigate to the Amazon ECS console.

2. Select Your Cluster: Choose the cluster that contains the container instance you want to update.

3. Access Tasks: Click on the "Tasks" tab within your selected cluster.

4. Stop the Task: Select the task you wish to update and click the "Stop" button. This will stop the current task and trigger the automatic deployment of a new task with the updated Appsmith version.

5. Verify Deployment: Once the new task is deployed, verify that the updated version of your application is running as expected.

If you are unable to find the "deploy a new task automatically" option, ensure that your ECS service is configured to automatically replace stopped tasks. This is typically managed through the service's deployment settings, where you can enable "Force new deployment" to ensure that a new task is launched with the updated configuration.

If you encounter any issues or need further assistance, please feel free to ask!

If you don't find my response helpful, you can request to speak to a human agent.

[buoyant barn]

When I log into my AWS account and navigate to the ECS console and select Clusters, is says there are no clusters.

[scarlet heart]

It seems like you might not have set up an ECS cluster yet, or you might be using a different service to manage your Appsmith deployment on AWS. Here are a few steps you can take:

1. Verify Deployment Method: Ensure that you are indeed using Amazon ECS for your Appsmith deployment. If you are using a different method, such as directly deploying on an EC2 instance without ECS, the update process will be different.

2. Check EC2 Instances: If you are managing Appsmith directly on an EC2 instance without ECS, you will need to update the Appsmith version manually on the instance. This typically involves connecting to the instance via SSH and pulling the latest Appsmith Docker image or updating the application files directly.

3. Create an ECS Cluster: If you intended to use ECS but haven't set up a cluster yet, you will need to create one. You can do this by:

• Navigating to the ECS console.
• Clicking on "Create Cluster".
• Following the prompts to set up a new cluster and deploy your Appsmith application.

4. Consult AWS Documentation: If you're unsure about the setup, consulting the AWS documentation on ECS and EC2 might provide additional clarity on how to proceed based on your specific setup.

If you need further assistance with a specific deployment method, please let me know!

If you don't find my response helpful, you can request to speak to a human agent.

[buoyant barn]

I am managing directly on an EC2 instance without ECS. How do I update using SSH?

[scarlet heart]

To update Appsmith on an EC2 instance using SSH, follow these steps:

1. Connect to Your EC2 Instance:

• Use an SSH client to connect to your EC2 instance. You will need the instance's public IP address and your SSH key pair.

bash
ssh -i /path/to/your-key.pem ec2-user@your-ec2-public-ip

2. Navigate to Appsmith Directory:

• Once connected, navigate to the directory where Appsmith is installed. This is typically where your Docker Compose file is located.

3. Pull the Latest Docker Image:

• Run the following command to pull the latest Appsmith Docker image:

bash
docker-compose pull

4. Restart the Appsmith Containers:

• After pulling the latest image, restart the containers to apply the update:

bash
docker-compose down
docker-compose up -d

5. Verify the Update:

• Once the containers are up and running, verify that the update was successful by accessing your Appsmith application in a web browser.

These steps will update your Appsmith instance to the latest version available in the Docker repository. If you encounter any issues during the update process, feel free to ask for further assistance!

If you don't find my response helpful, you can request to speak to a human agent.

[buoyant barn]

after doing the above, my version is still reporting Appsmith Community v1.17

[scarlet heart]

If your Appsmith version is still showing as v1.17 after following the update steps, here are a few things you can check:

1. Ensure Latest Image is Pulled:

• Double-check that the latest Docker image was pulled successfully. You can list the images to verify:

bash
docker images

Look for the Appsmith image and ensure it has the latest tag.

2. Remove Old Containers:

• Make sure the old containers are completely removed before starting new ones:

bash
docker-compose down --rmi all

This command will remove all containers and images, ensuring that the new image is used.

3. Clear Docker Cache:

• Sometimes, Docker might use a cached version of the image. Clear the cache and try pulling again:

bash
docker system prune -a
docker-compose pull

4. Check Docker Compose File:

• Ensure that your docker-compose.yml file is pointing to the correct image tag for the latest version. It should not be hardcoded to a specific version unless intended.

5. Restart Docker Service:

• Restart the Docker service to ensure all changes are applied:

bash
sudo systemctl restart docker

6. Verify Network and Proxy Settings:

• Ensure there are no network or proxy settings that might be preventing the latest image from being pulled.

After performing these steps, try starting the containers again and check the version. If the issue persists, please let me know!

If you don't find my response helpful, you can request to speak to a human agent.

[buoyant barn]

what should I see when I run docker images?

[scarlet heart]

When you run the docker images command, you should see a list of all Docker images currently available on your system. The output will include several columns, but the key ones to look for are:

• REPOSITORY: This is the name of the image repository. For Appsmith, it should be something like appsmith/appsmith-ce or similar, depending on the exact image you are using.

• TAG: This indicates the version of the image. For the latest version, this should be latest unless you are using a specific version tag.

• IMAGE ID: A unique identifier for the image.

• CREATED: The time when the image was created.

• SIZE: The size of the image.

Here's an example of what the output might look like:

REPOSITORY TAG IMAGE ID CREATED SIZE
appsmith/appsmith-ce latest abcdef123456 2 days ago 500MB

Ensure that the TAG column shows latest or the specific version you are trying to update to. If it doesn't, you may need to pull the latest image again.

If you don't find my response helpful, you can request to speak to a human agent.

[buoyant barn]

How do I know if I have the latest docker image? The one I have was created 12 months ago, even though I just did a docker-compose pull.

[scarlet heart]

If the Docker image you have was created 12 months ago, it indicates that the latest image might not have been pulled successfully. Here are steps to ensure you have the latest image:

1. Check for Latest Tag:

• Run the following command to pull the latest image explicitly:

bash
docker pull appsmith/appsmith-ce:latest

Replace appsmith/appsmith-ce with the correct repository name if it's different.

2. Verify Image Update:

• After pulling, run docker images again to check the CREATED column for the appsmith/appsmith-ce:latest image. It should show a recent creation date.

3. Remove Old Images:

• If the old image persists, remove it to avoid conflicts:

bash
docker rmi

[buoyant barn]

after doing docker pull appsmith/appsmith-ce:latest, when I try to log in, I'm getting : Unauthorized Redirecting to login page. Why would this be happening?

[scarlet heart]

The "Unauthorized Redirecting to login page" issue typically occurs due to authentication or session problems. Here are some steps to troubleshoot and resolve this:

1. Clear Browser Cache and Cookies:

• Sometimes, old session cookies can cause issues. Clear your browser's cache and cookies and try logging in again.

2. Check Environment Variables:

• Ensure that your environment variables, especially those related to authentication and session management, are correctly set in your docker-compose.yml or .env file.

3. Verify Backend Connectivity:

• Ensure that the backend services are running correctly and are accessible. You can check the logs for any errors:

bash
docker-compose logs

4. Check Appsmith Configuration:

• Verify that the Appsmith configuration files have not been altered in a way that affects authentication. This includes checking any OAuth or SSO settings if you are using them.

5. Restart the Application:

• Sometimes, simply restarting the application can resolve transient issues:

bash
docker-compose down
docker-compose up -d

6. Inspect Network and Proxy Settings:

• If you are using a reverse proxy or load balancer, ensure that it is correctly configured to handle authentication headers and sessions.

If the issue persists after these steps, please let me know, and we can explore further troubleshooting options!

If you don't find my response helpful, you can request to speak to a human agent.

[buoyant barn]

My docker-compose.yml file contains: version: "3"

services:
appsmith:
image: index.docker.io/appsmith/appsmith-ce
container_name: appsmith
ports:
- "80:80"
- "443:443"
volumes:
- ./stacks:/appsmith-stacks
restart: unless-stopped
# Uncomment the lines below to enable auto-update
#labels:
# com.centurylinklabs.watchtower.enable: "true"

#auto_update:

image: containrrr/watchtower

volumes:

- /var/run/docker.sock:/var/run/docker.sock

# Update check interval in seconds.

command: --schedule "0 0 * ? * *" --label-enable --cleanup

restart: unless-stopped

depends_on:

- appsmith

environment:

what might be missing?

[scarlet heart]

Based on the docker-compose.yml file you provided, here are a few things to check and potentially adjust:

1. Environment Variables:

• Ensure that all necessary environment variables for Appsmith are set. These might include database configurations, authentication settings, and any other required variables. Typically, these would be set under the environment section for the appsmith service.

2. Network Configuration:

• If you are using a reverse proxy or have specific network requirements, ensure that the network settings are correctly configured.

3. Volume Permissions:

• Ensure that the ./stacks directory has the correct permissions and ownership so that the Appsmith container can read and write to it.

4. Watchtower Configuration:

• If you are using Watchtower for auto-updates, ensure that it is correctly configured. The depends_on and volumes settings look correct, but make sure Watchtower has the necessary permissions to manage the Appsmith container.

5. Check for Errors in Logs:

• After starting the containers, check the logs for any errors that might indicate what is going wrong:

bash
docker-compose logs appsmith

6. Update Docker Compose File:

• Ensure that the docker-compose.yml file is up to date with any new configurations or settings required by the latest Appsmith version.

If you've verified these settings and the issue persists, it might be helpful to consult the Appsmith documentation for any additional configuration options or reach out for further support. Let me know if you need more specific guidance!

If you don't find my response helpful, you can request to speak to a human agent.

[buoyant barn]

None of the above has helped. I still can not log in. I'm still getting "Unauthorized. Redirecting to login page...

[scarlet heart]

Someone from our team will reach out to you on this thread. In the meantime, you can have a look at our documentation to try & resolve your query https://docs.appsmith.com?utm=bot

[scarlet heart]

Hello!
Please share the following information to help us debug this issue:

1. Please enter your instance URL and append '/info' in your browser and send us the output.
2. Send us a loom.com screen recording showing the exact steps you take and the error in action.
3. Send us the full server logs by following the steps from this guide on how to get the logs.

[buoyant barn]

/info is as follows:commitSha "4a142af9e612d8ea5bd549541cb682c8842ca3db"
commitUrl "https://github.com/appsmithorg/appsmith/commit/4a142af9e612d8ea5bd549541cb682c8842ca3db"
githubRef "refs/tags/v1.65"
githubRunUrl "https://github.com/appsmithorg/appsmith/actions/runs/14126245621/attempts/1"
version "v1.65"
imageBuiltAt "2025-03-28T09:55:57+00:00"
isCI true

2. I'm just trying to log in.

3. I couldn't figure out how to do this. However, the following is a snipet from my docker-compose logs

appsmith | backend stdout | [2025-03-31 08:37:29,964] [lettuce-epollEventLoop-10-1] requestId= userEmail= traceId= spanId= - Login succeeded for user: User(name=Rxxxxxxxx, [email protected], hashedEmail=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, passwordResetInitiated=false, source=FORM, state=ACTIVATED, isEnabled=true, emailVerificationRequired=false, emailVerified=null, workspaceIds=null, examplesWorkspaceId=null, inviteToken=null, isAnonymous=false, tenantId=xxxxxxxxxxxxxxxxxxxxxx, organizationId=xxxxxxxxxxxxxxxxxxxxxxxxxxx, isSystemGenerated=null, lastActiveAt=null)
appsmith | editor stderr | {"level":"debug","ts":1743410249.988587,"logger":"http.handlers.reverse_proxy","msg":"upstream roundtrip","upstream":"127.0.0.1:8080","duration":0.157346291,"request":{"remote_ip":"xxxxxxxxx","remote_port":"51693","client_ip":"xxxxxxxx","proto":"HTTP/1.1","method":"POST","host":"xxxxxxx","uri":"/api/v1/login?redirectUrl=http%3A%2F%2Fxxxxxxxxxxx%2Fapplications","headers":{"Priority":["u=0, i"],"Cookie":["REDACTED"],"X-Request-Id":["invalid_request_id"],"User-Agent":["Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:136.0) Gecko/20100101 Firefox/136.0"],"Accept-Language":["en-US,en;q=0.5"],"Content-Length":["95"],"X-Forwarded-Host":["xxxx"],"Origin":["http://xxx"],"X-Appsmith-Request-Id":["7c6e3ff1-386c-4aca-999d-e68f2f1ddc76"],"X-Forwarded-Proto":["http"],"Accept-Encoding":["gzip, deflate"],"Upgrade-Insecure-Requests":["1"],"Accept":["text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8"],"Content-Type":["application/x-www-form-urlencoded"],"X-Forwarded-For":["xxxxxxx"],"Referer":["http://xxx/user/login?error=true&redirectUrl=http://xxx/applications"]}},"headers":{"Expires":["0"],"X-Xss-Protection":["0"],"Referrer-Policy":["no-referrer"],"Set-Cookie":["REDACTED"],"Content-Length":["0"],"Location":["http://xxxx/applications"],"Cache-Control":["no-cache, no-store, max-age=0, must-revalidate"],"Pragma":["no-cache"]},"status":302}

Any help you can provide to get us back on line will be appreciated.

[scarlet heart]

Could you please send us the full server logs by following the steps from this guide?

[buoyant barn]

I have managed to download the logs. Where do I send the logs to?

[buoyant barn]

I found another thread where someone is having the same issue. You had them send the logs to [email protected], so that's what I did as well. I put this thread title in the subject field.

[scarlet heart]

Hello! Are you using HTTP or HTTPS?
If you are facing this issue with HTTP, then we will provide a fix for it in v1.66.
In the meantime, you can get it fixed by setting up an SSL certificate.

[buoyant barn]

I was not able to work on this until today. I am using HTTP. I was able to download version 1.66, and it appears to have fixed our issues. I am able to log in and I see my apps, and they seem to be working. Thank you for the quick update to fix the issue.