1

enter image description here

The security group assigned to it has both Inbound and Outbound rule as ALL traffic and ALL port range, so why does it say it's not allowing traffic on that listener port?

enter image description here

Avery235
  • 4,756
  • 12
  • 49
  • 83
  • Does the balancer actually work? – Michael - sqlbot Nov 07 '17 at 02:22
  • I added Route 53 that alias it and point the namecheap nameservers to Route 53, the website gives Bad gateway error. – Avery235 Nov 07 '17 at 02:28
  • 1
    So it sounds like the load balancer itself is working, otherwise it wouldn't be able to return that error. Are the instance targets showing healthy? – Michael - sqlbot Nov 07 '17 at 02:49
  • 1
    Ok resolved. The target group must use HTTP instead of HTTPS https://i.imgur.com/OOZBZHp.png, presumably because my Express server is listening on HTTP. Thanks for the help! – Avery235 Nov 07 '17 at 03:13

1 Answers1

1

If the LoadBalancer was created by ElasticBeanstalk environment, you would have to add the listener in the ElasticBeanstalk configurations

sydadder
  • 354
  • 2
  • 15
  • Once you added the listener, make sure you click on the "Save" button at the very bottom of the page. It can easily be missed – clem Jan 12 '22 at 19:04