Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've installed the certificate and set 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 site 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 thedomain.com). But https://thedomain.com doesn't load.

I really don't know why the https url isn't loading... anyone have any ideas?

Thanks!

Edit: Turns out the problem was simply the EC2 security group firewall settings.

share|improve this question
    
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? –  Ben Doom Mar 29 '10 at 0:49
    
I get a "Server not found" error. Port 443 is open for TCP under Firewall->Incoming Connections. –  rksprst Mar 29 '10 at 2: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

2 Answers 2

You need to ensure that thedomain.com 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.

share|improve this answer
    
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 2:26
    
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 5: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 8:17

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

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

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

share|improve this answer
    
It's listening on port 443. –  rksprst Mar 30 '10 at 18:42

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.