502 Bad Gateway when loading changedetection in browser after launching on AWS ECS Fargate

[patelc75]

I installed changedection.io via AWS Co-Pilot on top of ECS Fargate (see logs below). When I go to http://change-Publi-kNlwvbUpBGM8-182468462.us-west-2.elb.amazonaws.com:5000 (port added at end), I get 502 Bad Gateway. Below are the ELB listener and Security Groups settings. Any help would be appreciated.

✔ Proposing infrastructure changes for stack changedetection-dev-chirag
- Creating the infrastructure for stack changedetection-dev-chirag                [create complete]     [349.5s]
  - Service discovery for your services to communicate within the VPC             [create complete]     [0.0s]
  - Update your environment's shared resources                                    [update complete]     [167.7s]
    - A security group for your load balancer allowing HTTP traffic               [create complete]     [1.4s]
    - An Application Load Balancer to distribute public traffic to your services  [create complete]     [154.9s]
    - A load balancer listener to route HTTP traffic                              [create in progress]  [152.8s]
  - An IAM role to update your environment stack                                  [create complete]     [19.8s]
  - An IAM Role for the Fargate agent to make AWS API calls on your behalf        [create complete]     [15.9s]
  - An HTTP listener rule for path `/` that forwards HTTP traffic to your tasks   [create complete]     [0.0s]
  - A custom resource assigning priority for HTTP listener rules                  [create complete]     [3.6s]
  - A CloudWatch log group to hold your service logs                              [create complete]     [8.7s]
  - An IAM Role to describe load balancer rules for assigning a priority          [create complete]     [15.9s]
  - An ECS service to run and maintain your tasks in the environment cluster      [create complete]     [123.7s]
    Deployments
               Revision  Rollout      Desired  Running  Failed  Pending
      PRIMARY  4         [completed]  1        1        0       0
  - A target group to connect the load balancer to your service on port 80        [create complete]     [15.9s]
  - An ECS task definition to group your containers and run them on ECS           [create complete]     [0.0s]
  - An IAM role to control permissions for the containers in your tasks           [create complete]     [19.8s]
✔ Deployed service chirag.
Recommended follow-up action:
  - Your service is accessible at http://change-Publi-kNlwvbUpBGM8-182468462.us-west-2.elb.amazonaws.com over the internet.

[patelc75]

I figured this out. When using AWS Co-Pilot, the dev server is local and you have to hit http://127.0.0.1:5000/. I know obvious but wondering why Fargate was being configured even when launching a dev environment