Answers: <p>I solved it, I had forgotten that I had to add port 443 to the security group that my load balancer group belongs to.</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-04-26T13:24:51.483Z
Answers: 2021-04-26T14:45:03.373Z
Answers: 2021-04-26T14:45:03.373Z
Answers: Felix Eklöf
Body: <p>I've setup an &quot;Application Load balancer&quot; in AWS. It has two Listeners, one on HTTP (port 80) and one on HTTPS (port 443).
  It also has one target group that with only one FARGATE instance that I've registered in ECS.</p>
  <p>In the Image below you can see the two listeners and the SSL Cert. I've attached to the HTTPS listener. You can also see that they have the same rule defined. Both of them target the same TargetGroup, over HTTP (port 80). From what I've understood that's an accepted practice to have a Load balancer listen to HTTPS but forward the request over HTTP since it's in the same VPC.</p>
  <p>But for some reason only the HTTP listener is working. I've visited the site over HTTPS both directly through the LB's DNS Name and the domain I've attached to the SSL cert. both I both of the give the same result, it loads a while until it gets a timeout.</p>
  <p>Any guess what could be wrong?</p>
  <p><a href="https://i.sstatic.net/pj4Zu.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/pj4Zu.png" alt="enter image description here" /></a></p>
  
Tags: <amazon-web-services><amazon-ecs><load-balance><loadbalancing>
Title: AWS ELB Application Load balancer, SSL not working
UserDisplayName: Felix Eklöf
ThreadText: # AWS ELB Application Load balancer, SSL not working
  
  (Asked by: username_0 on 2021-04-26)
  
  I've setup an "Application Load balancer" in AWS. It has two Listeners, one on HTTP (port 80) and one on HTTPS (port 443).
  It also has one target group that with only one FARGATE instance that I've registered in ECS.
  
  In the Image below you can see the two listeners and the SSL Cert. I've attached to the HTTPS listener. You can also see that they have the same rule defined. Both of them target the same TargetGroup, over HTTP (port 80). From what I've understood that's an accepted practice to have a Load balancer listen to HTTPS but forward the request over HTTP since it's in the same VPC.
  
  But for some reason only the HTTP listener is working. I've visited the site over HTTPS both directly through the LB's DNS Name and the domain I've attached to the SSL cert. both I both of the give the same result, it loads a while until it gets a timeout.
  
  Any guess what could be wrong?
  
  [![enter image description here](https://i.sstatic.net/pj4Zu.png)](https://i.sstatic.net/pj4Zu.png)
  
  **Tags:** amazon-web-services, amazon-ecs, load-balance, loadbalancing
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2021-04-26. Score: 1
  
  I solved it, I had forgotten that I had to add port 443 to the security group that my load balancer group belongs to.
  
  
  ---
  
  