SSL converted page is not reachable on the internet

My web page is hosted on AWS.and it was SSL converted.

I can see the page from my own computer and smartphone in my home Network and Wifi area. But from the outside (ex: access website from a smartphone outside) the page is not reachable.

So I checked the Security group and port NO.

Inbound rules are below.

According a manual I reffered it seems OK, but if there is something wrong please let me know.

Here is telnet command result on port 443 Sorry it's written in Japanese. It says that unable connect to the host. Port No 443: Failed to connect.

Does it mean port 443 is closed??

I tried iptables -L -v -n below

I can not figure out the meaning...

Result of curl to the AWS IP: curl -k -vv https://

It seems it does not working.

Result of tcpdump -nni any port 443

Route 53

Detail of load balancer Can you figure out information from above? If you need other information plase let me know.

Target group I can see something unhealthy above. Target group is not configured to receive traffic from the load balancer

And maybe there are other points I need to check, so If you need to see other point, Please let me know I'll update the detail.

Thank you.

• Try a curl to the AWS IP: curl -k -vv https://<your aws ip>.

• If it works, try the same thing using the hostname. If this time it doesn't work it's a DNS issue.

• Check if there's some firewall inside the VM. For example: iptables -L -v -n. You may have some firewall rules preventing most IPs from accessing your web server.

• Check if there's some ACL on the web server itself. Web servers can be configured to ignore requests coming from certain IP addresses. If you're using Apache, check the Require lines in your configuration.

As a general rule, you can run a tcpdump -nni any port 443 on the server (you may have to install tcpdump) and repeat your test. Tcpdump basically collects and displays the actual packets involved, so if you try and some packets reach the server on port 443, it means nothing outside the VM blocked it and the issue probably is server related. If, on the other hand, you don't see any packet, it means something else is blocking you from accessing the web server.

EDIT

If you have a load balancer, ensure it is correctly pointing to the 443 port of the backend server(s). If not, traffic reaching the load balancer may be redirected to another port (80?) where HTTPS is not supported, which can "break" your connection.