3 Answers
- Newest
- Most votes
- Most comments
0
Considering you can still connect to the instance over SSH but not over HTTP/S, it sounds like a service issue within the instance. Have you checked the logs to ensure that the service operating on those ports is not failing (Apache, Nginx, etc.)?
Relevant content
- asked 6 months ago
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- I host a website on an EC2 instance. How do I allow my users to connect on HTTP (80) or HTTPS (443)?AWS OFFICIALUpdated 7 months ago
Hi Chris, Thanks for your reply. The Apache Service is running. I Checked the log and there is no error there. Also I can ping google.com from the instance after connecting to SSH. However, outbound traffic is not working and coming with message "Connection Timed Out, could not connect to port 80". However when I stop and Start the instance, the outbound and inbound traffic works though port 80 for a few minutes and then again gets blocked automatically.