-1

I cannot get access to the second port that I want to have to. So, here are the listeners I have in my ALB: enter image description here

Additionally, my TG-dev is not healthy: enter image description here

I am not sure what is the reason for this. Basically, what is my setup - I have Node.js API that is running on the AWS EC2 instance, on port 8080, and I run it using the PM2. However, configured a development purposes only API that is currently running on port 8081, again using the PM2. I have access to port 8080, but unable to access the server at port 8081. Here is my Security Group (SG) that is allowing the access only from the LB: enter image description here

This points to the initial SG that has rules for both ports: enter image description here

How can I achieve my goal to have access to both, 8080 and 8081, ports?

EDIT: Here is also my pm2 list and what actually is happening on port 8080 and 8081. Maybe the reason why I cannot access 8081 is that there is difference, but I am not sure how this is configured, cause we do not have contact with the person who designed this. Any ideas are appreciated! enter image description here

Vitomir
  • 335
  • 2
  • 15
  • If you app is running on port 8080, why would you think you can access it on port 8081? – Marcin Mar 13 '23 at 22:36
  • As it can be seen on the last screenshot, the app is running on both 8080 and 8081. I have two instances that are running on both ports, cause I want to have one that is running with the develop environment and the other with the prod. However, @AlexD already answered me correctly. Thanks :) – Vitomir Mar 14 '23 at 15:50

1 Answers1

1

Your processes are listening on IPv6 only but your security group doesn't have ports 8081 and 8080 open for IPv6, only for IPv4.

AlexD
  • 914
  • 7
  • 15