- 最新
- 最多得票
- 最多評論
Hi Roberto,
What type of load balancer is it? ALB? NLB? Classic ELB?
Are you attempting to connect to the load balancer URL via HTTP or HTTPS? If HTTPS, do you have a valid certificate attached to the listener on the load balancer?
Can you please share your load balancer configuration?
Edited by: JayG50 on Sep 30, 2019 11:01 AM
Hi Jay,
The load balancer is an Application Loadbalancer.
I have a valid HTTPS certificate and the LoadBalancer imported the certificate without problems.
I am trying to connect to:
host1.mydomain.com that points to the loadbalancer and the ALB should forward the request to the server but apparently it is not.
I can see that the LoadBalancer can definitely reach the EC2 instance as I see:
"GET / HTTP/1.1" 429 6206 "-" "ELB-HealthChecker/2.0"
So the healthcheck works fine.
I might have found an issue with the security group that I am still investigating. Probably the problem is related to that.
Edited by: RobertoS on Sep 30, 2019 2:02 PM
Hi Roberto,
You may also want to look at how your target groups are configured and the ports they are listening on when traffic is forwarded from the listener. If your ALB is connecting to the EC2 instances via HTTP but the instances are configured to redirect to HTTPS, you will definitely have connectivity issues. Unless you need end-to-end encryption, you might want to try to disable HTTPS on the EC2 instances and only use HTTP to rule that out as the issue.
It would look something like this:
User -> (HTTPS) ALB -> Forward to Target group -> (HTTP) EC2
相關內容
- 已提問 7 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 8 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前