- Newest
- Most votes
- Most comments
When encountering a "This site can't be reached" error for your website, there are several potential causes and solutions to consider:
- Check your EC2 instance configuration:
- Ensure your EC2 instance is running in a public subnet.
- Verify that you're using the public IP address of your EC2 instance, not the private IP.
- Consider setting up an Elastic IP if you don't have a public IP address.
- Review your security settings:
- Check the inbound rules of your EC2 security group to allow HTTP (port 80) and HTTPS (port 443) traffic.
- Verify the inbound and outbound rules in your subnet's Network Access Control List (NACL).
- If using Route 53 for DNS:
- Confirm that your A record is set up correctly.
- Ensure your nameserver records are properly configured and aligned with the NS records in your Route 53 public hosted zone.
- Check the TTL (Time to Live) for your NS records, and consider lowering it temporarily if you've recently made changes.
- For CloudFront distributions:
- Verify that your SSL/TLS certificate is properly set up and linked to your distribution.
- Check that your domain name is correctly configured in CloudFront.
- Backend health:
- Ensure your web server (e.g., Apache) is running correctly on your EC2 instance.
- Check server logs for any errors or issues.
If you're still experiencing issues after verifying these points, you may need to investigate further by checking your application logs, testing connectivity directly to the server, or consulting AWS support for more specific troubleshooting steps.
Sources
this site can't be reached | AWS re:Post
i am getting "This site can’t be reached" ERROR | AWS re:Post
Route53 – This site can’t be reached | AWS re:Post
site can't reachable through the public IP | AWS re:Post
domain name cant be reached | AWS re:Post
Hello.
To troubleshoot your EC2 instance and get your website back online please follow bellow step you will be got it solution.
1. Check if EC2 is Running
- Go to your AWS Management Console > EC2 > Instances.
- Ensure your instance is Running. If not, start it.
2. Check Security Group
- Go to Security Groups under Network & Security in EC2.
- Ensure you have inbound rules allowing traffic for:
- HTTP (port 80) for a regular website.
- HTTPS (port 443) if you're using SSL.
- Make sure your IP (or 0.0.0.0/0 for public access) is allowed.
3. Restart Web Server
- Log in to your instance using SSH.
- Restart your web server (EX. Apache or Nginx)
For Apache command.
sudo systemctl restart apache2
For Nginx Command.
sudo systemctl restart nginx
Check DNS
- Ensure your domain's DNS is pointing to your EC2 instance's public IP.
- Use https://dnschecker.org/ to verify DNS propagation.
Hello,
- Check EC2 health status on console: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_status.html . If Instance check failed, maybe you could stop ec2 and start.
2.SSH EC2, check your application or service.
Relevant content
- asked 2 years ago
- asked a year ago
- asked 2 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 4 months ago