Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Issue 141601 Error while trying to connect to a HTTPS website - Error 117 (net::ERR_BAD_SSL_CLIENT_AUTH_CERT)
Starred by 9 users Reported by, Aug 9 2012 Back to list
Status: Archived
Last visit > 30 days ago
Closed: Feb 2015
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Sign in to add a comment
Chrome Version       : 21.0.1180.75
OS Version: 5.1 (Windows XP)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5: Not tested
  Firefox 4.x: OK
     IE 7/8/9: OK

What steps will reproduce the problem?
1. Trying to connect in a HTTPS website

What is the expected result?
Simply connect to the website

What happens instead?
Error page

Please provide any additional information below. Attach a screenshot if

UserAgentString: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.75 Safari/537.1

error 117.JPG
50.8 KB View Download
Labels: -Area-Undefined Area-Internals Internals-Network-SSL
Status: Untriaged
Thanks for the report!

We'll need some more information to help diagnose the problem.

See for instructions.

Comment 2 by, Aug 13 2012
Labels: Action-FeedbackNeeded
Status: Assigned
stefano.vassena: thank you for the bug report.

In addition to what cbentzel requested in comment 1, please try running
chrome.exe with the command-line option

Does that fix the problem?

The screen shot error 117.JPG shows an URL
in Chrome's location bar.  I believe Facebook does not use client
certificates.  So there may be an SSL man-in-the-middle proxy device
on your network, and that device is requesting client certificates?
Hi, I've the same problem even with
any ideas ? 

I need to get this fixed asap.  Mine occurs very randomly.  I can refresh a few times to finally have the page show up.  Everything HTTPS is very random at this point.  How can I contribute to further this issue ? 
Comment 5 by, Aug 27 2012
ricardo.angelosanto: if you're seeing client-auth problems then we recently worked around a bug in IIS related to renegotiation in r152116. This should be in the beta channel by now at least.
Comment 6 by, Nov 6 2012
Same problem here with "Google Chrome Version 22.0.1229.94 m". The problem occurs with every HTTPS-Site, but as mentioned by ricardo after a few refreshes there is no problem opening the site. But after closing Chrome and opening again or changing the site and come back to the site again, the problem occurs again. Clicking on any link on HTTPS-Sites p.e. Link: "Weiter" results in the same error again. After refreshing I am rerouted to the first site.
To add to this, I have tried the beta route, with no success.  Back to firefox unfortunately...
Comment 8 by Deleted ...@, Dec 21 2012
I am facing this problem from few days, I feel it is an issue regarding firewall which blocks the site from opening with this error message "Error 117 (net::ERR_BAD_SSL_CLIENT_AUTH_CERT): Bad SSL client authentication certificate."
128 KB View Download
Comment 9 by Deleted ...@, Jan 10 2013
I get the error even when I open But, when I refresh the page, it works fine. This is very irritating. 

Error 117 (net::ERR_BAD_SSL_CLIENT_AUTH_CERT): Bad SSL client-authentication certificate.

I started having the same problem.
It was working until few days ago. I have Version 23.0.1271.101.
Mozilla keep working fine.
Yesterday chrome was working as well, today no more.

I get "Certificate-based authentication failed", "Error 117 (net::ERR_BAD_SSL_CLIENT_AUTH_CERT): Bad SSL client authentication certificate."
I forgot to add that Safari works fine as well, so it is not a problem with my keychain.

Can people still encountering this issue do two things:

1) Attempt to use the latest Google Chrome Canary version - - and see if the problem still exists.

2) Gather a net-internals log, as described at
Comment 13 by Deleted ...@, Feb 26 2013
Here is my results with Chrome Canary ( That I downloaded seconds ago. )

The problem still persists with CHROME CANARY.

103 KB View Download
Comment 14 by, Feb 27 2013
Tested today with google canary. Same problem.

Enclosed the net-internals-log.json -File
1.8 MB View Download
For comment #14: It appears from Event ID 753 that the browser is sending a client hello to ssl/, and the server is responding with an SSL alert for "Access Denied" (eg: alert 49). Socket #636 shows this same thing, but for Receiving an alert this early suggests a server misconfiguration - the server never even sends the CertificateRequest message needed to indicate that a client cert is required.

For comment #13: Your log does not contain sufficient data. Please make sure carefully follow the steps from (you can also find instructions at chrome://net-internals/help.html ). This involves closing all instances of Chrome, loading a new instance with a single tab, opening chrome://net-internals, and then in a new tab, reproducing the error.
Project Member Comment 16 by, Mar 9 2013
Labels: -Action-FeedbackNeeded Needs-Feedback
Project Member Comment 17 by, Mar 10 2013
Labels: -Area-Internals -Internals-Network-SSL Cr-Internals Cr-Internals-Network-SSL
Comment 18 by, Feb 20 2015
Status: WontFix
Closing for lack of feedback.
Comment 19 by, Feb 20 2015
Status: Archived
Sign in to add a comment