- Newest
- Most votes
- Most comments
Hello.
Is the domain "https://<domain-name>/" correct for accessing ALB?
Have you linked your domain to EC2 by mistake?
Did you update your domain after adding the ALB?
As you can see in the image, there is only 443 in the listener rule, so access on port 80 should fail.
The domain is correct and the certificate obtained for it is valid.
Not sure i understand this: "Have you linked your domain to EC2 by mistake?" - since the webserver gives me correct responses via 80, the domain setup should be correct, isn't it?
Adding HTTP:80 to the rules didn't help...
Could you please share an image of your ALB security group?
@Riku_Kobayashi re: screenshot - updated the question
When I run the nslookup command, a different IP address is returned. What kind of domain settings do you have?
nslookup webserver-531843639.us-east-1.elb.amazonaws.com Server: 192.168.11.1 Address: 192.168.11.1#53 Non-authoritative answer: Name: webserver-531843639.us-east-1.elb.amazonaws.com Address: 34.231.232.72 Name: webserver-531843639.us-east-1.elb.amazonaws.com Address: 52.20.15.22 nslookup staging.memory-lane.ai Server: 192.168.11.1 Address: 192.168.11.1#53 Non-authoritative answer: Name: staging.memory-lane.ai Address: 54.160.251.252
If zone has just been updated, there may be some cache remaining due to TTL.
Relevant content
- asked 10 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Hello. Could you please send a screenshot with the target group configuration and Listeners configuration?
Best regards, Andrii
@Andrii S - updated the question