Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

My website on EC2 reports it is running but no one can see it

0

Hello! Since sometime last week people who try to find my current home page have been contacting me to tell me it is not there. I checked with the EC2 console and even restarted it, and even gone into it via SSH and confirmed that it is running. My domain name register merged earlier last week with one they think is better. I thought that did it. But they confirm nothing is broken on their end.

What else happened? And do I need to launch a newer image to keep going?

Topics
Management & GovernanceCompute
Tags
Amazon EC2AWS Account Management
Language
English

asked a year ago155 views

1 Answer
0
Accepted Answer

When your EC2-hosted website appears to be running but isn't accessible to visitors, there are several potential causes to investigate:

  1. DNS Configuration Issues: If your domain registrar recently merged with another company, there might be changes in how your DNS is being managed. Verify that your domain's DNS settings are still correctly pointing to your EC2 instance's public IP address.

  2. Security Group Settings: Check that your EC2 instance's security group allows incoming traffic on ports 80 (HTTP) and 443 (HTTPS) from all sources (0.0.0.0/0). Security group rules might have changed or been reset.

  3. Web Server Status: Even though your instance is running, your web server (Apache, Nginx, etc.) might have stopped. Try restarting the web server service on your EC2 instance.

  4. Network Configuration: Ensure that your subnet's route table includes a route for internet-bound traffic pointing to the internet gateway.

  5. IP Address Changes: If you recently restarted your EC2 instance and it doesn't have an Elastic IP associated with it, its public IP address might have changed, making your DNS records outdated.

  6. Application Configuration: Your application might have hardcoded IP addresses or domain names that need to be updated.

  7. DNS Propagation: If you made recent DNS changes, be aware that propagation can take up to 48 hours to complete globally.

To troubleshoot:

  • SSH into your instance and check your web server logs for any error messages
  • Verify the web server is running with the appropriate service status command
  • Try accessing the site using the EC2 instance's public IP directly to rule out DNS issues
  • Check for any recent changes in your application configuration

You shouldn't need to launch a newer image unless there's an underlying issue with your current instance that can't be resolved through configuration changes.
Sources
EC2 Website Connection Timeout | AWS re:Post
Troubleshooting www.bbc-1.com Website Issue | AWS re:Post

answered a year ago

EXPERT

reviewed a year ago

  • Doctor Who
    a year ago

    I've done all of that. And nothing worked. Except SSHing into the image to check on things. There were no web server logs.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content