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.

What error do you get at https://thedomain.com? A timeout? A cert error? A 404? You say port 443 is open. Where is it open? — Ben Doom, Mar 29 '10 at 00:49
I get a "Server not found" error. Port 443 is open for TCP under Firewall->Incoming Connections. — rksprst, Mar 29 '10 at 02:34
If you do a netstat -an at a command prompt do you see a line for port 443 in the local address column? — MattB, Mar 29 '10 at 13:44
It's listening on :443 ... but no ip address is specified (under the local address column). — rksprst, Mar 30 '10 at 18:37
In my case the server was on AWS and the inbound traffic was not allowed on port 443. Hope this helps someone. — Anshuman Jasrotia, Jun 02 '17 at 06:17
@rksprst Have you got the correct answer to this question? I'm stucked on this issue — Abdulhakim Zeinu, Feb 16 '21 at 18:43

score 4 · Answer 1 · edited Jul 22 '15 at 20:04

4

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.

edited Jul 22 '15 at 20:04

TRiG

1,181
3
13
30

answered Mar 29 '10 at 08:45

Vivek Kumbhar

3,073
1
18
13

It's listening on port 443. – rksprst Mar 30 '10 at 18:42
Checking "Secure World Wide Web Service (HTTPS)" worked for me. – Alyce Feb 14 '16 at 23:52
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 Apr 21 '20 at 21:18
after this there is no 443 port, and also site is not opened with https says This site can’t be reached – alamnaryab Apr 21 '20 at 21:20
@alamnaryab Check the firewall may be not allowed 443 port or using any services.. – Abhishek B. Mar 11 '22 at 05:22

score 2 · Answer 2 · edited Jul 23 '15 at 10:51

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.

edited Jul 23 '15 at 10:51

Giovanni Toraldo

2,587
19
27

answered Mar 29 '10 at 01:01

sybreon

7,405
1
21
20

It does point to the IP... the regular http domain works fine. It's only the https that is not working. – rksprst Mar 29 '10 at 02:26
2

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` – sybreon Mar 29 '10 at 05:59
1

Tried it and got operation timed out for port 443... If I changed the port to 80 I get Connected)... – rksprst Mar 30 '10 at 18:41
1

Then you better check your IIS configuration to ensure that it there is a binding for the SSL. – sybreon Mar 31 '10 at 08:17
I had the same symptoms and it was a firewall blocking port 443 – firstTimeCaller Jun 16 '15 at 06:55
@Giovanni. Any particular reason to prefer `example.com` to `example.net`? I used `.net` for the question & both answers. – TRiG Jul 22 '15 at 20:49
actually not :D – Giovanni Toraldo Jul 23 '15 at 10:52

score 0 · Answer 3 · answered Feb 16 '21 at 21:20

I was facing the same problem and this problem occurred because of my router's port forwarding configuration. I configured my public IPs port forwarding on port 80, not 443. Thats why I can't access my site remotely using HTTPS protocol. I solved this problem by configuring my public IP port forwarding on port 443. Then it starts working. But first, make sure to check that port 443 is open and it is allowed on your firewall.

score 0 · Answer 4 · answered Nov 08 '19 at 00:15

I had the same problem and the cause was that the firewall was blocking port 443, the same as a couple of other people in the comments of the other solutions. I don't know how all firewall software works, but in Windows Azure, you have to explicitly add an Inbound Traffic rule to allow traffic on port 443.

HTTPS not working; binding set, certificate installed

4 Answers4