HTTPS not working; binding set, certificate installed

Question

I've installed the certificate and set up the HTTPS bindings. However, when I load the site on HTTPS it does not load.

I've looked at all the settings but everything seems correct.

I've restarted the server numerous times. The certificate is stored on the local computer under Personal > Certificates. I have the private key for the certificate. The port (443) is open.

If I try https://localhost on the server, the site loads, but with a domain error (i.e., it's localhost and not example.net). But https://example.net doesn't load.

I really don't know why the HTTPS URL isn't loading.

Solution 1

If you are getting "Server Not Found", that means that the client could not find the responsible server to serve your request. In your case, that's a HTTPS-based application. You also said that HTTP works but HTTPS fails.

Verify the following:
Go to Control Panel\System and Security\Windows Firewall\Allowed Programs Verify that you have "Secure World Wide Web Service (HTTPS)" and "Domain, Home/Work, and Public" both checked.

You also said that when you try https://example.net from the server itself, it fails. Try browsing the application from the server itself and run netstat -ano and check whether there is any activity happening on port 443.

Solution 2

You need to ensure that example.net actually points to the server's IP. You can do this either with an nslookup or just plain old ping the machine. This is your most likely cause.

Comments

[Ben Doom]

What error do you get at thedomain.com? A timeout? A cert error? A 404? You say port 443 is open. Where is it open?

[Peter Wang]

I get a "Server not found" error. Port 443 is open for TCP under Firewall->Incoming Connections.

[MattB]

If you do a netstat -an at a command prompt do you see a line for port 443 in the local address column?

[Peter Wang]

It's listening on :443 ... but no ip address is specified (under the local address column).

[Anshuman Jasrotia]

In my case the server was on AWS and the inbound traffic was not allowed on port 443. Hope this helps someone.

[Abdulhakim Zeinu]

@rksprst Have you got the correct answer to this question? I'm stucked on this issue

[Peter Wang]

It does point to the IP... the regular http domain works fine. It's only the https that is not working.

[sybreon]

In that case, then you need to make sure that the port is actually open and accessible from the outside. Try: openssl s_client -connect host:port

[Peter Wang]

Tried it and got operation timed out for port 443... If I changed the port to 80 I get Connected)...

[firstTimeCaller]

I had the same symptoms and it was a firewall blocking port 443

[TRiG]

@Giovanni. Any particular reason to prefer example.com to example.net? I used .net for the question & both answers.

[Giovanni Toraldo]

actually not :D

[Alyce]

Checking "Secure World Wide Web Service (HTTPS)" worked for me.

[alamnaryab]

TCP 192.168.90.100:49706 40.90.19.152:443 ESTABLISHED 6284 TCP 192.168.90.100:51655 111.22.29.254:443 TIME_WAIT 0 TCP 192.168.90.100:51662 205.15.16.42:80 ESTABLISHED 1192 TCP 192.168.90.100:51663 152.19.19.11:443 TIME_WAIT 0 TCP 192.168.90.100:51666 111.22.29.254:443 ESTABLISHED 8364 TCP 192.168.90.100:51667 151.253.18.12:443 SYN_SENT //this server ip

[alamnaryab]

after this there is no 443 port, and also site is not opened with https says This site can’t be reached

[Abhishek B.]

@alamnaryab Check the firewall may be not allowed 443 port or using any services..