1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
There might be an incorrect DNS record causing your frontend to resolve the ALB DNS name to something that doesn't match the certificate and Your ALB might be configured to serve the wrong certificate, or misconfigured in the way it handles the traffic from your frontend.
As a solution
From the machine where your frontend runs (or if it's a web app, from your browser's developer tools), use nslookup <ALB-DNS-name> to verify that it resolves to the expected ALB address. In the AWS console, navigate to your ALB and its HTTPS:443 listener. Double-check that the certificate selected is the correct one for "example.com" and "*.example.com".
I don't see ALB DNS name anywhere in the network tab in browser's developer tool when sending request. I've double checked certificate in use as well as HTTPS listener for my ALB.