Google Chrome ERR_BAD_SSL_CLIENT_AUTH_CERT: How to Fix It

Q: What causes ERR_BAD_SSL_CLIENT_AUTH_CERT in Chrome?

This error is caused by a failure in SSL client certificate authentication. Common causes include an expired or revoked client certificate, a corrupted certificate store, an incorrect system date and time, a network proxy or VPN interfering with the SSL handshake, or a mismatch between the certificate Chrome is presenting and what the server expects.

Q: How do I know if my client certificate is expired?

On Windows, press Windows+R, type certmgr.msc, and press Enter. Go to Personal > Certificates and look at the 'Expires' column next to your certificate. On Mac, open Keychain Access, select 'My Certificates,' and double-click the certificate to see its validity period. If today's date is past the expiration date, you need a new certificate from your IT team or certificate authority.

Q: Can ERR_BAD_SSL_CLIENT_AUTH_CERT affect all websites or just specific ones?

This error typically only affects websites that require client certificate authentication to verify your identity, such as corporate intranets, government portals, banking platforms, or VPN web gateways. Standard public websites like Google or YouTube do not use client certificates, so you will only see this error on sites that specifically request one.

Q: Does clearing Chrome's cache fix ERR_BAD_SSL_CLIENT_AUTH_CERT?

Clearing Chrome's SSL state and cache can fix this error if it was caused by a stale or corrupted cached session. Go to Chrome Settings > Privacy and security > Clear browsing data, select all cached content, and clear it. Also clear Chrome's SSL state via Internet Options > Content > Clear SSL state on Windows. This is not always the root cause, but it is a quick and safe step to try early in troubleshooting.

Q: Why does ERR_BAD_SSL_CLIENT_AUTH_CERT only happen on Chrome and not other browsers?

Chrome manages its own SSL state and, on Windows, can use both the Windows Certificate Store and its own internal store. If a certificate is correctly installed in one location but not recognized by Chrome, or if Chrome's SSL cache is stale, you may see this error in Chrome while other browsers like Edge or Firefox handle it differently. Edge uses the Windows Certificate Store more directly, and Firefox maintains its own separate certificate database. Clearing Chrome's SSL state or re-importing the certificate into the correct store usually resolves the discrepancy.

Abstract

The ERR_BAD_SSL_CLIENT_AUTH_CERT error in Google Chrome means the browser failed to authenticate using a client SSL certificate when connecting to a website or web service. This typically happens when the certificate is expired, corrupted, missing, or not trusted by the server. It is most common on corporate networks, government portals, or any site that requires a personal or device certificate to verify your identity before granting access.