While opening my private website, I am getting the following error in CHROME only. in internet explorer its working without any issue.
I tried resetting chrome, delete all cache but no luck. nothing changed from backend site and error was started as of sudden.
weird thing is, if I open Fiddler 4 at the same time then its working. don't know what Fiddler is doing to fix that prob but when I close it again, then its again giving the same error.
RC4 is a 30 year old cipher and TLS 1.0 is also outdated and insecure - as per security reasons enterprise managed devices are not allowed to use them.
Even if you find a with a temporary workaround (Going back to Chrome 97 and enable chrome://flags/#enable-quic) TLS 1.0 and 1.1 will be deprecated and your website host will need to update their Transport Layer Security.
This issue is listed in the official Google Known issues article: https://support.google.com/chrome/a/known-issues/1700835?visit_id=1-636640442263392447-217633526&hl=en&rd=1
I have also found a third party article with additional information on the matter: https://blog.pcisecuritystandards.org/are-you-ready-for-30-june-2018-sayin-goodbye-to-ssl-early-tls
This has started happening with Chrome v98. If you downgrade to Chrome v97 it will work again. I'm not sure what changed between versions.
The warning occurs because the website does not support TLS 1.2. Contact the site administrator. Problem encountered after updating Chrome to 98x. The warning appears with Firefox but the site works by enabling tls 1.0 and 1.1.
just fixed this problem by opening Chrome. Add in the search bar chrome://flags/#enable-quic, select the first entry "Experimental Quick protocol" and change its status into disabled. Save the changes and restart Chrome.
It should be solved, if not there are other fixes here you can try as well.
Let me know if you managed. Cheers
Type thisisunsafe at the warning page. It will let you access to the website even with insecure configurations(e.g. TLS 1.0, Non-HTTPS connection on HSTS, ...).
Remember -- This is totally unsafe. You must upgrade your website's TLS version as soon as possible.
