- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
I can hit http://app.blockchatdao.com/ (plain HTTP on port 80) fine in a browser, but not https://app.blockchatdao.com/
Can you confirm that inbound TCP port 443 is open on the security group associated with the EC2 instance?
From what I can see the inbound rules are set up correctly. I have not even touched these settings. I am a beginner on AWS and do not even know how to open the terminal or check if it's a firewall or not.
Those security group rules look fine.
Are you now able to view the website using HTTP to both the DNS name and the IP address?
Port 22 being open in the security group suggests the EC2 is running Linux, is that correct? Check what ports are opened and being listened on with
netstat -tulpn
If the output is too large, limit it to just the webserver ports
netstat -tulpn | egrep -w '80|443'
Issue here could be that the connections aren't reaching the EC2 instance or the webservice itself is not listening on https/443 please check whether the instance is listening on 443 by doing 'telnet localhost 443' from the instance's terminal/cmd. if it gets connected, 443 is listening and the issue is either with Security group or the OS Firewall. if the Telnet gets Not connected then check the webserver configuration to understand why the service is not listening only on port 80
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 5 Monaten
Hi Steve, thanks for the quick reply.
I've opened up the security group associated but how do I check its open?
I also could not get the http:// to work? the Elastic IP works directly for me though
Both http://app.blockchatdao.com/ and http://3.210.166.43/ work for me. But I get connection timeout on both https://app.blockchatdao.com/ and https://3.210.166.43/
You can check that port 443 is open in the security group in AWS Console -> EC2 -> Instances and then select the instance, go to the security tab and verify the inbound rules.
On the instance itself, is the webserver setup to listen on port 443?
Is there a host-based firewall, and is this allowing port 443 traffic through? Depending on what OS the instance is running this could be
firewalld
(RHEL/CentOS/Fedora), orufw
(Ubuntu), or Windows Firewall, or something else (or you might not have a host-based firewall running at all).Best place to start is double-checking the security group has the port open, and that the webserver is listening on that port.