Q. In the Elastic Beanstalk environment, the domain is accessed, however after directly reconstructing EC2 and Load Balancer Auto Scaling, 502 error occurred when connecting to the domain.
A. In general, 502 error is occurred by a back-end system that is not be processed.
If there is a 504 Time out or a connection is denied, it's a firewall problem.
You can't check the status, however you need to narrow down the area to find the cause of the problem.
1. ELB(ALB) -> Connected Target Group -> Check Health Host Value 1 of Monitoring
2. Check the service status of the WEB(EC2) Server
-> There is a high probability that the WEB service is not running.
-> Since it is not registered as a startup service, the process may not be running as a result of the new drive.
2-1. Ensure Web access is available on EC2 alone except ELB
2-2. Health Checks
Please check whether the WEB server is running a service.
If not, we recommend that you run it and recreate the AMI with the startup program registered.
This document is based on February 2020.
Please leave a comment if document needs an update.
Customers of Bespin Global who needs additional support, you can get a free support through our team.