Unable to connect on port 443

Question

I have a CentOS 7 EC2 instance with Apache HTTPD running on port 443.

```
$ netstat -tnlp | grep 443
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      2533/httpd          
```

I cleared all inbound rules for the Security Group and now have just these 3:

```
IPv4	HTTPS	TCP	443	/32
IPv4	HTTP	TCP	80	/32
IPv4	SSH	TCP	22	/32
```

But not able to connect to the web server on the public IP (Google Chrome browser reports ERR_CONNECTION_TIMED_OUT). It was working previously before I removed some inbound rules and stopped the instance for a few days.

```
$ telnet  443
Trying ...
telnet: connect to address : No route to host
$ telnet  80 
Trying ...
telnet: connect to address : No route to host
$ telnet google.com 443
Trying 142.250.188.46...
Connected to google.com.
Escape character is '^]'.
```

Anything else I can check?
Thanks

**UPDATE:**
I installed VNC server on the instance and connected using VNC viewer. Launched Firefox, opened URL https://localhost and was able to login to the web app. But still can't access using https://.

SV · Accepted Answer

Adding port 443 using the firewall command did the trick for me.

```
$ sudo firewall-cmd --permanent --add-port=443/tcp

$ sudo firewall-cmd --reload

$ sudo firewall-cmd --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: eth0
  sources: 
  services: dhcpv6-client ssh
  ports: 3389/tcp 443/tcp
  protocols: 
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules:

```

AWS-User-2227877 · Answer

Please its been 2 weeks now, have tried everything but each time I telnet telnet  443 or telnet telnet  80, I keep getting;  telnet: Unable to connect to remote host: Connection timed out

And when I do curl -I   80, I get curl: (7) Failed to connect to  port 80: Connection timed out.

My  is an elastic IP.

Please help

kentrad · Answer

If you have a [default Public IP](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html#concepts-public-addresses) you will get a new IP address every time you stop/start the instance. Could it be that?

Unable to connect on port 443

Relevant content