Whenever I try to launch a page in google chrome, it does not connect due to an improper security certificate. I have enabled the Allow invalid certificates for resources loaded from localhost. experimental feature in chrome, but it still gives the same SSL error.
google chrome always gives me the same error message: ERR_SSL_PROTOCOL_ERROR
I am suddenly getting the following error message when trying to connect to an "wss" WebSocket connection string in Chrome that is not happening in Firefox:
Error in connection establishment: net::ERR_SSL_OBSOLETE_VERSION
My current version of Chrome is: Version 81.0.4044.34 (Official Build) beta (64-bit).
I'm guessing this is due to an update since I was able to connect to the same WebSocket connection string recently and the SSL certificate is the same one I have been using for a while and is valid when I use Firefox.
I have started looking around for documentation on this issue but haven't found anything yet.
Chrome is deprecating support for TLS 1.0 and 1.1. I modified the code for my WebSocket server by enabling support for TLS 1.2 and that fixed the issue.
I have installed latest Chrome Version 68.0.3440.84 (Official Build) (64-bit)
on Windows 7 Home Premium
When I access google.com/youtube.com I get following error:
Your connection is not private
Attackers might be trying to steal your information from www.google.com (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_AUTHORITY_INVALID
I have tried importing the certificate as mentioned in Getting Chrome to accept self-signed localhost certificate, but that didn't help
I can access google.com from Mozilla Firefox without any error
My laptop time is up to date
Any pointers will be very helpful
Resolved the issue by Installing the certificate from : https://secure.globalsign.net/cacert/Root-R2.crt in chrome
Ran into an issue earlier today with errors on our internal certificate. Other users/consumers/clients were not getting the errors. Was getting an error "there are issues with the sites certificate chain" and then when viewing the certificate, sure enough just the end certificate was listed, not the whole chain tree. The cert used to work fine after I generated it and installed on our servers a month or so ago and continues to work for my colleagues.
I am on Version 59.0.3071.115 (Official Build) (64-bit) on Ubuntu 14.04.
I resolved the issue on a whim by going to my custom CA settings here chrome://settings/certificates?search=cert and then Authorities and "edit"ing my CA, unchecking all the boxes, pressing okay, then re-editing and re-checking them and pressing okay, no browser restart needed. Next page refresh and my Certificate error was gone!
So this is likely a Chrome bug of some sort and its interaction with NSSDB.
I've got a web site that uses SSL Client certificate authorization.
All client certificates are generated using OpenSSL and are self-signed. Everything worked with all web-browsers, but the recommended one was Google Chrome, because it uses same SSL warehouse as IE, so certificate installation was pretty easy (click-click-password-done!).
After last update of Google "Chrome 29.0.1547.57 m", noone can access my web-server, even me.
Google chrome error only! IE and FF working fine.
Error is: ERR_SSL_CLIENT_AUTH_SIGNATURE_FAILED.
Same in server error log.
Do you have any suggestions?
The problem is that most part of clients are non familiar with PC's and they got very frightened about that situation. So phone support guys are under the wave of calls.
We are experiencing the same problem. As Sean has reported, it seems that Chrome on Windows XP
negotiates TLSv1.2 even though the operating system does not support SHA-2 (say, SHA-256 or SHA-384)
hash function.
We found that Chrome fails when it receives "client certificate request" following SERVER HELLO.
SERVER HELLO itself negotiates RC4-SHA1 (in our environment) which should succeeds. The problematic
packet seems the "client certificate request" that includes SHA-2 (as well as SHA1) functions for hashes.
Invoking Chrome with "--enable-logging --log-level=0" outputs the following message:
ERROR:nss_ssl_util.cc(193)] ERR_SSL_CLIENT_AUTH_SIGNATURE_FAILED: NSS error -12222, OS error -2146893816
This is an Operating system error corresponding "NTE_BAD_ALGID" for CryptSignHash function:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa380280(v=vs.85).aspx
Disabling TLSv1.2 on the server should fix the problem. But I think Chrome should prefer SHA1 on Windows XP.
I'm experiencing the same thing here with Windows7 client systems unable to authenticate with client certificates against some of our systems, but not others. The affected servers are running Apache Tomcat while the unaffected are running IIS7, though I'm hesitant to identify that difference as the culprit.
Anyone else seeing this?
EDIT:
I'm able to eliminate the problem by disabling TLSv1.2 on the server. Is anyone else able to replicate this experience?
I would also be interested to know whether anyone else is seeing this on anything but the Windows platform, as it's the only place it's happening here (same version OSX has no issues).
EDIT2:
Chrome Bug Report here: https://code.google.com/p/chromium/issues/detail?id=278370
EDIT3:
Should be working again in latest Chrome stable. Chrome 30 will have a more robust fix, but 29.x should also work now.
I recently had a similar issue in Chrome on Mac OS. It worked fine with Firefox, but started failing in Chrome and Safari after changing my corporate (AD) credentials -- I guess the issue was a mismatch between system creds and the keychain creds.
The solution for me was a reset of the private key(s) access permissions in the Keychain Access app.
To do the reset:
In Keychain Access app right-click each private key that fails and select "Get Info".
Go to "Access Control" tab and set "Allow all applications to access this item" -- click on that option even if it's already set. Then click Save Changes.
Refresh the website that fails and you should be prompted to enter keychain password -- enter it and select Allow Always.
It is combination of Win XP and Google Chrome 29.0.1547.57 m
On Win 7/8 this problem doesn't occur.
You could install older working version 28.0.1500.95
http://www.filehippo.com/download_google_chrome/15657/
But settings for disabling updating are not so easy.
http://dev.chromium.org/administrators/turning-off-auto-updates
The problem is caused by Chrome running TLSv1.2 on Windows XP.
This can be disabled on the server side but also on the client side.
To run Chrome with a lower version of TLS, start it with the command-line option --ssl-version-max=tls1.1
I had this problem Connecting Chrome with WebSockets to apache throw proxy_wstunnel_module.
My solution was configuring httpd.conf
ProxyPass /wss2/ ws://127.0.0.1:8080/ retry=0 keepalive=On
ProxyPassReverse /wss2/ ws://127.0.0.1:8080/ retry=0
<Location /wss2/>
SSLRequireSSL On
SSLVerifyClient none
SSLVerifyDepth 1
SSLOptions +StdEnvVars +StrictRequire
SSLRenegBufferSize 10486000
</Location>
Chrome WebSockets does not like the parameter SSLVerifyClient optional
I hope this helps.