I can access a file through the browser using standard HTTP, but when I add ssl support the browser hangs. I installed a self signed certificate and the browser does recognize this. I added a Security Exception in the browser (Chrome) so I believe it's exchanging the cert. I run the command 'openssl s_client -connect 10.121.17.177:443' and I see what looks like the correct output with the cert, etc. Here's my ssl nginx.conf values:
server {
listen 443;
ssl on;
server_name 10.121.17.177;
### SSL cert files ###
ssl_certificate mycert.pem;
ssl_certificate_key mycert.key;
ssl_session_cache shared:SSL:10m;
ssl_session_timeout 5m;
ssl_protocols SSLv2 SSLv3 TLSv1;
ssl_ciphers RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP;
ssl_prefer_server_ciphers on;
#keepalive_timeout 60;
root /home/stanley;
...



Edited 1 time(s). Last edit at 02/15/2011 07:15PM by shorspool.

more info: I used curl like this: curl -v -k https://hostname.domainname.com/index.html

If i use the http:// address, I get a valid response. If I use a different https address such as my bank https://www.patelco.org, I get a valid response.

I see this exact behavior. Did you sort this out? I have a perfectly good SSL wildcard cert that was working until yesterday.