unable to open port 443

Question

_{Monday, September 8, 2014 12:40 PM}

telnet  168.63.241.248 443
Trying 168.63.241.248...
telnet: Unable to connect to remote host: Connection refused

 telnet  168.63.241.248 80                                               1 ↵
Trying 168.63.241.248...
Connected to 168.63.241.248.
Escape character is '^]'.
^CConnection closed by foreign host.

Although as per my dashboard both ports are open

All replies (3)

_{Monday, September 8, 2014 2:00 PM ✅Answered}

Hi;

Please Check SSL bindings. As this appears to be an application level issue, i was able to access your car website on port 80 using http"//168.63.241.248.

Check if the SSL endpoint for the Vm or the Cloud service is 443 if yes then check if the Website can be accessible from the Server itself.

Warm Regards

Prasant

_{Monday, September 8, 2014 5:08 PM ✅Answered | 1 vote}

Hi;

There could be many reasons, but the most common are:

1. Firewall blocking access between the machines (also check local firewalls)
2. Port not open on the destination machine

After checking for firewalls and that the port is open, use telnet to connect to the ip/port to test connectivity. This removes any potential issues from your application.

The error means the OS of the listening socket recognized the inbound connection request but chose to intentionally reject it. Assuming an intermediate firewall is not getting in the way, there are only two reasons (that I know of) for the OS to reject an inbound connection request. One reason has already been mentioned several times - the listening port being connected to is not open. There is another reason that has not been mentioned yet - the listening port is actually open and actively being used, but its backlog of queued inbound connection requests has reached its maximum so there is no room available for the inbound connection request to be queued at that moment. The server code has not called accept() enough times yet to finish clearing out available slots for new queue items. Wait a moment or so and try the connection again. Unfortunately, there is no way to differentiate between "the port is not open at all" and "the port is open but too busy right now". They both use the same generic error code.

Connection refused means that the port you are trying to connect to is not actually open.

So either you are connecting to the wrong IP address, or to the wrong port, or the server is listening on the wrong port, or is not actually running.

A common mistake is not specifying the port number when binding or connecting in network byte order.

Check at the server side that it is listening at the port 2080. First try to confirm it on the server machine by issuing telnet to that port:

telnet localhost 2080

If it is listening, it is able to respond.

Although it does not seem to be the case for your situation, sometimes a connection refused error can also indicate that there is an ip address conflict on your network. You can search for possible ip conflicts by running:

 arp-scan -I eth0 -l | grep <ipaddress>

and

arping <ipaddress>

Hope this helps;

Prasant

_{Monday, September 8, 2014 2:16 PM}

hi, this is not related to application but something related to infra. I am not even able to do telnet at the 443 while port 80 is working fine