Question : HTTPS Request are timing out even though SSL certificate is setup correctly

HTTPS requests are timing out when i try to open pages on my server. I've tried to verify that the certificate is setup correctly using the openssl s_client and everything looks good.

openssl s_client -connect localhost:443 -showcerts -CApath /etc/ssl/certs (see attached output)

What can I do to track down this issue? I'm not seeing any errors in the error log and the regular HTTP requests are processed correctly.

PLEASE HELP.

Code Snippet:

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:

 

CONNECTED(00000003)
depth=3 /L=ValiCert Validation Network/O=ValiCert, Inc./OU=ValiCert Class 2 Policy Validation Authority/CN=http://www.valicert.com//[email protected]
verify return:1
depth=2 /C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority
verify return:1
depth=1 /C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certificates.godaddy.com/repository/CN=Go Daddy Secure Certification Authority/serialNumber=07969287
verify return:1
depth=0 /O=*.mydomain.com/OU=Domain Control Validated/CN=*.mydomain.com
verify return:1
---
Certificate chain
 0 s:/O=*.mydomain.com/OU=Domain Control Validated/CN=*.mydomain.com
   i:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certificates.godaddy.com/repository/CN=Go Daddy Secure Certification Authority/serialNumber=07969287
-----BEGIN CERTIFICATE-----
XXX
-----END CERTIFICATE-----
 1 s:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certificates.godaddy.com/repository/CN=Go Daddy Secure Certification Authority/serialNumber=07969287
   i:/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority
-----BEGIN CERTIFICATE-----
XXX
-----END CERTIFICATE-----
 2 s:/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority
   i:/L=ValiCert Validation Network/O=ValiCert, Inc./OU=ValiCert Class 2 Policy Validation Authority/CN=http://www.valicert.com//[email protected]
-----BEGIN CERTIFICATE-----
XXX
-----END CERTIFICATE-----
 3 s:/L=ValiCert Validation Network/O=ValiCert, Inc./OU=ValiCert Class 2 Policy Validation Authority/CN=http://www.valicert.com//[email protected]
   i:/L=ValiCert Validation Network/O=ValiCert, Inc./OU=ValiCert Class 2 Policy Validation Authority/CN=http://www.valicert.com//[email protected]
-----BEGIN CERTIFICATE-----
XXX
-----END CERTIFICATE-----
---
Server certificate
subject=/O=*.mydomain.com/OU=Domain Control Validated/CN=*.mydomain.com
issuer=/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certificates.godaddy.com/repository/CN=Go Daddy Secure Certification Authority/serialNumber=07969287
---
No client certificate CA names sent
---
SSL handshake has read 5357 bytes and written 331 bytes
---
New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-SHA
Server public key is 2048 bit
Compression: NONE
Expansion: NONE
SSL-Session:
    Protocol  : TLSv1
    Cipher    : DHE-RSA-AES256-SHA
    Session-ID: 233D503622386D5B16871C821711C4DC804F396E3F4622A21F9EB2741B49ADA9
    Session-ID-ctx: 
    Master-Key: 88162AB7FA032389532E74895494A867FBD6974B679C198051A0BCAB84438F6DB46CFA8F9F5F959F6F77033886549BF1
    Key-Arg   : None
    Krb5 Principal: None
    Start Time: 1256970423
    Timeout   : 300 (sec)
    Verify return code: 0 (ok)
---
closed

Open in New Window

Select All

Answer : HTTPS Request are timing out even though SSL certificate is setup correctly

When you say timing out do you mean nothing displays at all? If so do you have a firewall and is it allowing HTTPS traffic? (TCP port 443).

If you're not seeing any errors in the logs etc. then it suggests the connections are being blocked and not hitting the web server.

Question : HTTPS Request are timing out even though SSL certificate is setup correctly

Answer : HTTPS Request are timing out even though SSL certificate is setup correctly

When you say timing out do you mean nothing displays at all? If so do you have a firewall and is it allowing HTTPS traffic? (TCP port 443).If you're not seeing any errors in the logs etc. then it suggests the connections are being blocked and not hitting the web server.

When you say timing out do you mean nothing displays at all? If so do you have a firewall and is it allowing HTTPS traffic? (TCP port 443).

If you're not seeing any errors in the logs etc. then it suggests the connections are being blocked and not hitting the web server.