When accessing https://www.twitch.tv on Chromium-based browsers (new Edge, Google Chrome, Opera) the following (commonly known) error appears:
Your connection isn't private
Attackers might be trying to steal your information from www.twitch.tv (for example, passwords, messages, or credit cards).
NET::ERR_CERT_REVOKED
When checking the SSL certificate, it states that is valid until June 13th, 2020. However, it also states that the certificate is withdrawn by the certificate authority.
Accessing the site from Firefox and from Chrome on another PC both work fine. Several SSL check websites also state that the certificate is fine.
I already tried the following:
Check date, time and timezone
Clear cookies and cache of the browser
Clear SSL state in internet options
Clear DNS cache
Temporarily disable anti-virus and windows defender
After an extensive search, I found a solution that worked for me. For those who have a similar problem: https://support.google.com/chrome/thread/24475945?hl=en
Related
I am having this strange issue with SSL on my site. The domain is pointed towards Cloudflare and I am using flexible SSL settings. The universal default certificate is set on Cloudflare.
Now all my devices ( android, ios, windows, and any browser Edge, Chrome, Safari ) it works perfectly. But some users are complaining that they get NET::ERR_INVALID_CERT_AUTHORITY.
I have tried it with a lot of versions of google chrome(56-77). And both developers on the team all tried plus for other people I know it works. But some users ( according to client 70%) face this issue. Even the client is not having this issue.
Website is : https://beinhaoranim.co.il or https://www.beinhaoranim.co.il
please don't duplicate or something like that. I have serched through whole web and my problem is unique. Other solutions are most related to google chrome and its same on all devices.
I also faced the same issue long time ago which you can read in my post ERR_CERT_AUTHORITY_INVALID. I am explaining the same below.
The main reason is "SSL Certificate" conflict. What was happening is that
there was already a SSL on the hosting and sometime the SSL is
self-signed so make sure there is no other ssl certificate for that
site as it will conflict with the SSL provided by CloudFlare.
Download the SSL provided by CloudFlare and install on the
hosting. Remove any earlier SSL of that site first. Wait for upto 24
hours so that new changes are reflected everywhere.
How resolve this problem in google chrome for my site:
The certificate for this site expires in 2017 or later, and the certificate chain contains a certificate signed using SHA-1.
in Internet Explorer functions normally.
You resolve the problem by getting a new certificate that uses SHA2. The SHA1 algorithm has been proven to have collisions, which means someone could make up a fake certificate and impersonate your site.
Chrome on purpose warns and does not accept those certificates anymore.
Typically, if you revoke and re-issue a certificate with your CA, you will get credit for the remaining time of your existing certificate.
The problem is not with Chrome, but with your certificate being considered 'unsafe' and Chrome taking a hard stance to make sure things are actually secure.
I am having an issue with a website where IE & MS Edge & Chrome all believe that the certificate is revoked (firefox works fine)
Error from IE:
This organisation's certificate has been revoked.
Security certificate problems may indicate an attempt to trick you or intercept any data you send to the server.
I have run check on SSLLabs, and the only problem i can see there is that it uses SHA1 hashes. Am i just seeing this error because of the SHA1 RSA Signatures?
URL: https://www.gunemporium.com.au/
Yep, SHA-1 is completely broken, and does not provide any effective encryption.
I would more suggest that there is some SSL intercepting middlebox or AV software involved which changes the certificate and the issuer of the certificate. IE and Chrome both use the same CA store and proxy settings while Firefox has their own settings which would explain why you see it with IE and Chrome but not Firefox on the same PC and why you don't see it on another PC.
I would suggest to have a look at the certificate details (subject, issuer, fingerprint) and chain and compare what you see in Firefox with what you see in IE/Chrome.
I am able to access a URL in Chrome 36 and IE8 but in Chrome 39 or 40 or Firefox 35 it throws the error:
Unable to make a secure connection to the server. This may be a
problem with the server, or it may be requiring a client
authentication certificate that you don't have.
Error code: ERR_SSL_PROTOCOL_ERROR}.
It seems that it is an issue related to the SSL certificate. How can I fix this?
Google announced that they would begin removing support for SHA-1 cryptographic hash algorithm beginning with Chrome 39. According to Google:
HTTPS sites whose certificate chains use SHA-1 and are valid past 1 January 2017 will no longer appear to be fully trustworthy in Chrome’s user interface.
There are several sites which can provide detailed analysis of your SSL certificate chain, such as Qualys SSL Labs' SSL Test.
Google Chrome does have a highly risky command-line option --ignore-certificate-errors which might bypass certain certificate errors. Be aware that ignoring certificate errors puts all of your SSL traffic at risk of being eavesdropped on.
It's also possible that this is a new bug. Google switched from using OpenSSL library to it's own "BoringSSL" library in Chrome 38. To report a bug in Chrome visit chrome://help/ and click "Report an issue".
Try this. In Chrome, enter "chrome://flags/#enable-quic" without the quotes as a URL. CTRL + F to search for "quic", at which point you'll find...
Experimental QUIC protocol. Mac, Windows, Linux, Chrome OS, Android
Enable experimental QUIC protocol support. #enable-quic
Turn that to disabled, and let it restart your browser when prompted below.
Go to Windows Firewall, click on "Restore Defaults", then again. The problem should be fixed.
For me this issue resolved when I turned off my Antivirus Browsing control.
First check that in :
Internet Explorer- go to tools/internet options/advanced in the settings box, scroll all the way to the bottom and select Use TLS 1.0 and it will fix the problem.
SSL 2.0 or 3.0 and these are should also be selected.
Google Chrome-Click "wrench" sign on the tope right of it.Click Options then Under the bonnet in network click Change Proxy Settings and follow the steps above as in Internet Explorer.
If this didn't work try the following steps:
Unhide all the files and folders.
Then go to C:\Windows\System32\drivers\etc\hosts.
Right click on hosts file,then click properties. Then click security tab. After that click edit.
Here,click system and you have to check on allow full control and uncheck deny.
Click OK and then OK.
Now delete the hosts file.
You could read google forum tips from here
or you get all the details solution about err_ssl_protocol_error from here. I hope this will work and fix the error.
I have created my own CA and signed a certificate for use on an internal HTTPS website. I have imported the CA Certificate into both the Trusted Root Certificate Authorities and the Intermediate Certificate Authorities on the IIS machine and the site certificate is bound to the site on port 4433.
This works fine on IE9 and Firefox (i.e. the site is trusted) but I still get an HTTPS with a red score through it in Chrome (version 23.0.1271.91) saying that the site is not trusted.
Everything I have come across thus far says add the CA to Trusted.... But this seems to be of no avail in Chrome.
Any Ideas?
I believe this is a server/IIS issue.
Try to restart the server and check your SSL expiration date....
Check this page it might help you