- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello
You need to open port 80 HTTP so that you can access the apache page please check the security group, Here is the link helpful
Thanks for your information provided. But still failed. I don't know how to handle this website issue.
Hi there,
It turns out most browsers try to resolve using SSL when URLs are opened even if you don't have an SSL configured on your server. That's why you are getting the error. To solve this, copy the IP to the browser directly or right click on the URL and choose the 'Go to option.' This will open the link without SSL.
Still failed. Same error: This site can't be reached.
Thanks for your reply,. However, my AWS EC2 is a Linux server: Amazon Linux 2 AMI (HVM) - Kernel 5.10
How can I run telnet? Or is there any similar Linux command?
Telnet is by far the easiest and simplest way to do this. Just install it:
sudo yum install telnet
I have added 2 inbound rules:
IPV4, SSH, TCP, Port range: 22, Source: done by running https://checkip.amazonaws.com on my Windows 10 PC. IPV4, HTTP, TCP, Port 80, Source: 0.0.0.0/0
On the web server, I have already enable port 80 and port 443. Then I tested my Apache Web server by: http://ec2-99999999.xxxx.compute.amazonaws.com But still got the error: This site can't be reached. I have no idea about this issue and don't know in what way I should handle it. Please help me, thanks a lot.
"To solve this, copy the IP to the browser directly or right click on the URL and choose the 'Go to option.' This will open the link without SSL."
Still failed. Same error: This site can't be reached.
Some troubleshooting steps:
- On the instance, try doing
telnet 127.0.0.1 80(or 443 - up to you) and see if the session opens. That proves that the Apache server is running. - For good measure, also try the same command to the local IP address of the instance:
telnet 10.0.0.24 80for example. - Create another instance in the same subnet and perform that second
telnetcommand from the other instance.
If all three work then I'm not sure what the problem is because the routing and the public IP clearly work because you can SSH to the instance.
However, I'm guessing that at least one of the three above will fail.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
I recommend that you don't put the DNS name (or IP address) of your instance on the forum. This is a public space and someone may use this information in a malicious way to attempt to compromise your instance.