I have not been able to access appsmith for around 1 hour

[digital patio]

There seems to have been an update to Appsmith but for one hour or so, I have not had access
I am a bit weary about taking the docker container offline and then re-deploying in case it causing further problems

[tropic glacier]

Hey There,

We've registered your query, and our team will get back to you soon.

Regards,
Pranav

[digital patio]

@tropic glacier I took appsmith offline and then re-deployed the container and the message displayed in the pic has been up constandtly and keeps refreshing to the same message

it has come back online but back to the same screen as ther initial issue

my deployed apps give the screen shown in the pic

[digital patio]

@tropic glacier I am now around 2 hours offline
Is it only me that has been effected?

[digital patio]

@tropic glacier I have reverted back to v1.9.37.
It is working but obviously not ideal as I cannot use the latest version - v1.9.38

[next yarrow]

Same here on selfhosted version

Seems to be an mongodb problem

[tropic glacier]

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

1. What deployment method are you using?
2. Is your instance not accessible at all after updating to the latest version?
3. Please send us the full server logs by following the steps from this guide
   on how to get the
   logs.

[next yarrow]

1. docker-compose
2. Yes

Now i get the log

[marble fable]

I have the same issue on digital ocean self deployed

[next yarrow]

I could send you long on DM?

log

[tropic glacier]

Please send the logs via email to [email protected] and add the link to this
thread as reference.

[digital patio]

I am using Docker Compose
Appsmith runs but is not useable as per above pics

I will get logs

[next yarrow]

Sent!

[next yarrow]

How do you rollback?

[digital patio]

@tropic glacier Do you want logs from all of the folders?
Who is the best person to DM them to?

[next yarrow]

I've sent all folders to [email protected]

[digital patio]

to roll back, change the YAML file from image: index.docker.io/appsmith/appsmith-ce to image: index.docker.io/appsmith/appsmith-ce:v1.9.37 or if you have business edition it might be image: index.docker.io/appsmith/appsmith-ee:v1.9.37

[tropic glacier]

I am not able to reproduce this issue. Please also answer the following
questions:

1. Which Operating System are you deploying Appsmith on?
2. Are you using a reverse proxy, firewall, or load balancer?
3. Are you using an external Mongo/Redis setup?

@digital patio Please send us the logs via email to [email protected]
and add the link to this thread as a reference.

[next yarrow]

It works! Thank you

[next yarrow]

1. Ubuntu 20.04.4 LTS
2. Yes, reverse proxy and firewall. No config changes
3. No, internal

[digital patio]

@tropic glacier

1. My docker container is hosted on an Ubuntu 20.04.6 :LTS server
2. I have a firewall running but the Appsmith ports should be open. Im not sure about reverse proxy or load balancer
3. I am using MariaDB hosted on my server but this should only effect the app itself, should not stop the editor running

@tropic glacier I have emailed the server logs

@tropic glacier both me and @next yarrow are on Ubuntu could the issue be related to the updated appsmith versions compatability with ubuntu?

[tropic glacier]

@digital patio Could you please send the logs again? We did not receive
them.

Our team is investigating the issue. We'll get back as soon as we have updates.
Thank you for your patience.

[digital patio]

@tropic glacier I have resent the logs

[tropic glacier]

@next yarrow @digital patio Just to confirm, both of you were
previously on v1.9.37, before updating to v1.9.38, right?
Please also send us the output of this command: docker-compose exec appsmith mongod --version

[marble fable]

yes, we were on 1.9.37 with auto-update

meanwhile I've rolled back to 1.9.37 and it's working fine.

I've disabled the autoupdate for now

[tropic glacier]

Please also send us the output of this command: docker-compose exec appsmith mongod --version

[marble fable]

we're using a DO droplet with the standard mongo/redis

[deft ibex]

@marble fable can you share your logs with us and the above command?

[deft ibex]

@marble fable @next yarrow

We've found the issue and working to fix it. We'll update this thread with the steps to recover from the issue.

We're very sorry for the mishap on our end. And we appreciate your patience and cooperation.

[marble fable]

that‘s great to hear and no worries - so far we‘ve never had an issue with the autoupdate and the rollback worked nicely.

[tropic glacier]

I sincerely regret the unfortunate mishap that led to your instance going down.
Please know that we’ve pinpointed the issue and you can now restore your
instances using the following instructions:

docker-compose pull
docker-compose up -d --force-recreate appsmith

We greatly appreciate your kind patience and cooperation.

[short frost]

Is the issue resolved, I'm also facing this issue.

[next yarrow]

Thank you very much. On monday i will try. Have a nice weekend

[tropic glacier]

Hello! Were you able to try this @next yarrow?

[next yarrow]

Yes! It works! Thank you