Self signed certificate issue

[awehost]

Hi All

I wanted to access a cpanel account with ssl and self signed certificate, so in the Cpanel for the account I went to ssl/tls manager, the created a private key.

Next I went to the Certificates (CRT) page entered the details for the domain and generated the certificate on the server, and it's listed as installed.

Problem is I still can't get https:// for www-mysite-com. I know with self signed you still get the warning but you can continue and add an exception etc, but this doesn't give me that, just the message below.
And yes, I made sure if I used www in the cert I also used it in the url, neither will work anyway.
* url is modified to allow me to post.

--
The connection has timed out
The server at www-mysite-com is taking too long to respond.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
--

Any thoughts?

Thanks

 

[townwebsites]

Think you need a dedicated IP

in order to attach an SSL certificate. I don't know the internals but I think basically the ssl connection has to be made at the socket level, rather than in the web server. By having the IP dedicated to the domain and to the certificate, the connection internals can be kept private.

In any case, the way https is implemented in Apache works that way, so that you do need a dedicated IP even for a self-signed certificate.

SSH logins can use the same IP, so I don't think this is an inherent issue of SSL. But the connection there is persistent, where http is stateless ( a new connection is made for each http request). I suspect that is the reason for the difference in implementations.