Please provide a net internals log. Here are the instructions: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

Thanks.

Yeah, sadly the netlog is just saying the same thing as the error message, just at a lower level, that the server refused the connection.

Would you be willing to get two tcpdumps, one of each of IE and Chrome trying to do the same thing?

tcpdump (windump) and wireshark can't sniff loopback traffic (this being 127.0.0.1)

http://www.winpcap.org/pipermail/windump/2010-March/001032.html
https://wiki.wireshark.org/CaptureSetup/Loopback

If there's a Chrome build that gives verbose logs or something, I can try it out.

All connection attempts failed after exactly 1 second (well, one failed after 1.001 seconds, but close enough).  This seems rather suspicious.  What security software are you running?  Could you try temporarily disabling it?

It's McAfee Enterprise; I tried again with its Host IPS, Network IPS and Firewall disabled, but the issue remains the same.

I enabled further debugging on the server side, and it shows that Chrome chose to send a small set of Cipher suites in its Client Hello, whereas IE sent a larger set. There wasn't a common cipher between the server and Chrome's suite, which is why the handshake failed.

In IE's case:
Cipher Suites: [TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA]

The handshake resulted in the selection of TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 from that list.

In Chrome's case:
Cipher Suites: [TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, Unknown 0xcc:0xa9, Unknown 0xcc:0xa8, Unknown 0xcc:0x14, Unknown 0xcc:0x13, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA]

Resulted in javax.net.ssl.SSLHandshakeException: no cipher suites in common

Please close this issue if Chrome has chosen to restrict its set of ciphers to these by design.

Ah, probably your server is configured with a DSA (self-signed?) certificate. We haven't supported DSA for ages and it's even completely forbidden as of TLS 1.3. How did you generate the certificate? DSA certificates are basically nonexistent.

Thank you for providing more feedback. Adding requester "shivanisha@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot