#502 Bad Gateway

1 messages · Page 1 of 1 (latest)

plush niche
#

My appsmith instance became unresponsive.once I refreshed the page I got a 502 Bad Gateway error.
I went on to my SSH client and navigated to the docker file instance .

I tried both docker-compose down and docker-compose up -d`

With both commands, I got the same message ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information. If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

I have tested on other containers and they are working fine, I ran both docker commands on them and the containers came down and went back up with out a problem.

Looking at portainer, it shows the containers as still being up

light yarrowBOT
#

Hey There,

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

Regards,
Team Appsmith

plush niche
#

Its back up. it looks as though the recent update took a lot longer to install than it should have