Hi everyone, I'm facing an issue while using Airbyte, deployed on AWS (Amazon EC2)

t2.large

instance, 502 badgateway, any ideas for this?

I'm sorry to hear that you're experiencing issues with Airbyte on AWS EC2. A

502 Bad Gateway

error typically indicates that one server on the internet received an invalid response from another server. Based on the information provided in the extracts, a user on the Airbyte forum had a similar issue where they were getting a

502 Bad Gateway

error. They were able to resolve this issue by simply restarting the Docker containers using the command

sudo docker compose restart

[source](https://discuss.airbyte.io/t/3239). If the issue persists, I would recommend checking the logs for any error messages that could help identify the root cause of the problem. You can get the logs by running

docker logs airbyte-server > server.log

[source](https://discuss.airbyte.io/t/3715). If you're still unable to resolve the issue, you can reach out to the Airbyte community on their [Slack](https://slack.airbyte.com/) or [forum](https://discuss.airbyte.io/). If all else fails, you can open a Github ticket for further assistance [source](https://docs.airbyte.com/troubleshooting). Remember to ensure that your Docker Desktop app is running to ensure all services run smoothly [source](https://docs.airbyte.com/deploying-airbyte/on-aws-ec2).