HTTPS - Connection Timed Out

i have a virtual machine within Azure which serves up a web site.

when i navigate to it works fine.  i purchased a SSL certificate and it imported into IIS.  i edited the bindings for the cert using the default port of 443.  i added the site's name to the bindings.  

when i navigate to i get a "The connection has timed out" error.

the firewall rules allow 443 (default rule).

what else can i check and/or modify within IIS or the OS?  any help is appreciated.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

on the server, execute
 netstat -na | findstr 443
is there such line as
 TCP                LISTENING

on the client, try to execute
telnet 443
does the server respond?
andyalderSaggar maker's framemakerCommented:
Surely is who you bought the virtual host from rather than your own host's DNS name?
freezingHotAuthor Commented:
yes, this one of the responses:

 TCP                LISTENING

telnet 443 - could not open connection to the host
SolarWinds® VoIP and Network Quality Manager(VNQM)

WAN and VoIP monitoring tools that can help with troubleshooting via an intuitive web interface. Review quality of service data, including jitter, latency, packet loss, and MOS. Troubleshoot call performance and correlate call issues with WAN performance for Cisco and Avaya calls

freezingHotAuthor Commented:
i own and have it being forwarded to the virtual machine.
if you do
telnet 443
from the server itself, does it connect?
freezingHotAuthor Commented:
same thing on the local server - can't open connection.
zc2Commented: may not be resolved (does it?) to the local IP address. Try instead
telnet localhost 443
freezingHotAuthor Commented:
yes, telnet localhost 443 appears to connect.

the server using nslookup does resolve to the proper public IP address.
Does the public IP address actually equal the inner interface IP address?
If not, try to add a line like the following to the file C:\Windows\System32\drivers\etc\hosts
< local interface IP address>

How many sites on this server?
If there only one, try to remove the "Host name" from the binding.
Then you should be able to test is the site acceptable by https://localhost
freezingHotAuthor Commented:
i added the line into the hosts file.  when i did, i was able to telnet 443 on the local server.

i removed from the bindings as it is the only website being served; however, neither fixed connecting from the outside world.

when i telnet 443 on an outside machine, i still get the connection error.

the local server presents the default home page when i navigate to, but i can't do it from the outside world.
Looks like a firewall issue. Can you temporary turn the firewall off and try connect from the outside again?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
freezingHotAuthor Commented:
same thing with the firewall off - turned off both private and public
Do you have a firewall in the Azure virtual network?
freezingHotAuthor Commented:
Azure firewall didn't have 443 enabled.  thank you very much for your time!
You are welcome!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.