[admin] [CASE 173269593200419] Chat: HTTP 502 – Bad Gateway
Thank you for reaching out regarding the 50=
2 errors you were experiencing with your Application Load Balancer (ALB). I=
wanted to summarize our discussion and the resolution we found:
1=
. Issue Details:
– 502 errors started occurring around 2024-11-27T00=
:04:00 UTC
– Targets were marked as unhealthy at the same time
=
– You mentioned deleting expired SSL certificates from the Windows IIS se=
rver prior to the issue
2. Root Cause:
– The load balancer =
encountered SSL handshake errors when connecting to the target
– Thi=
s was confirmed by the TargetTLSNegotiationErrorCount metric, which coincid=
ed with the ELB 502 errors
3. Investigation:
– We verified =
that the primary IP 10.10.40.229 of the target instance was not working wi=
th HTTPS requests
– The secondary IP (10.10.41.229) was responding c=
orrectly to HTTPS requests
– The ALB was sending traffic to the prim=
ary IP (************) over port 443, as the target was registered by instan=
ce ID
4. Resolution:
– We discussed two potential solutions=
:
a. Fix the HTTPS configuration on the primary IP
b. Ch=
ange the target group type from instance ID to IP-based, and register the c=
orrect IP
– You implemented option b by creating a new IP-based=
target group with the correct IP, which showed as healthy
After t=
hat everything was working as expected.
I hope I was able to provi=
de sufficient assistance. Please, do not hesitate to contact us if you have=
any other queries or concerns. It's always a pleasure to help you!
We value your feedback. Please share your experience by rating this a=
nd other correspondences in the AWS Support Center. You can rate a correspo=
ndence by selecting the stars in the top right corner of the correspondence=
.
Best regards,
Shivang
Amazon Web Services
=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=20
To share your experience or contact us again about this case, please re=
turn to the AWS Support Center using the following URL: https://console.aws.amazon.com/support/home#/case/?disp=
layId=3D173269593200419&language=3Den
Note, this e-mail was sent from an address that cannot accept incoming =
e-mails.
To respond to this case, please follow the link above to respond from y=
our AWS Support Center.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Don=E2=80=99t miss messages from AWS Support when you need help! Update=
your contact information:
htt=
ps://console.aws.amazon.com/billing/home#/account
If you receive an error message when visiting the contact information p=
age, visit:
ht=
tps://repost.aws/knowledge-center/iam-billing-access/
AWS Support:
https://repost.aws/know=
ledge-center/
AWS Documentation:
https://docs.aws.amazon.com/
AWS Cost Management:
https://aws.amaz=
on.com/aws-cost-management/
AWS Training:
http://aws.amazon.com/trainin=
g/
AWS Managed Services:
https://aws.amazon.=
com/managed-services/
Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amaz=
on.com is a registered trademark of Amazon.com.
This message was prod=
uced and distributed by Amazon Web Services, Inc. or its affiliates 410 Terry Ave. No=
rth, Seattle, WA 98109.
=C2=A9 [2024], Amazon Web Services, Inc. or i=
ts affiliates. All rights reserved. Read our Privacy Notice.