Found 15 possible answers.
|User||Answered At||Possible Answer|
- @gavin.hardy i got it all sorted in the end my nginx container gets assigned a random port and added to the target group automatically Is there a way i can remove the port 80 target on my load balancer target group?
- right @nocode, so I should be getting a port assigned, and then setup my target group's port to 80 (to let the ALB route to it), and configure the target to be whatever port was assigned to my container?
- in the target group are all the instances healthy?
- Okay, I have set up my ALB to listen on 443 with a target of 80, so it should terminate the SSL right? On the instance listens an Nginx on port 80 but when I try to access it via the load balancer I receive gibberish```10.0.2.182 - - [28/Mar/2018:19:53:50 +0000] "\x16\x03\x01\x00\xA.... looks like the SSL termination is not working is it? If I access it directly it works fine ```
- telnet to port 80?
- So that port is mapped to port 80 automagically?
- can you telnet to your LB on port 443? that shouldn't be an issue then
- no, that should be fine. what error are you getting when you try to hit your https domain? all of my HTTPS listeners map to a TG using port 80
- On the listeners?
- Are you sure that the webserver is not running on port 80?