267
Hello,
I have a client that can access the GP web client on IE11, but if they try firefox or Chrome they get the error NS_ERROR_NET_INADEQUATE_SECURITY, or ERR_HTTP2_INEADEQUATE_TRANSPORT_SECURITY. I have upgraded them to 18.3 and reinstalled web client so it should now support TLS 1.2, but I am still getting the same error. Do I need to have TLS 1.0 disabled on the server in order to force it to 1.2? Are there any other settings/configuration that I need to do?
Regards,
Kayla
Hello Kayla,
This appears to be an issue with HTTP2.
This is noted on the Windows Server doc site, and has more to do with the order of the Suites:
The notice:
docs.microsoft.com/.../tls-cipher-suites-in-windows-10-v21h1
The solution/workaround provided in the notice:
docs.microsoft.com/.../deploy-custom-cipher-suite-ordering
Basically you will want to swap what order the "TLS Languages" your workstation and server attempt to talk in so the more secure items are first.
Thanks!
I don't know that I've seen these errors with Web Client before, nor could I find any mention of them when I looked.
As Web Client is working fine on IE 11, I wouldn't think it a need for Web Client that TLS 1.0 be enabled or disabled, otherwise I wouldn't think it would work with any browser if that was the case.
If you installed Web Client from the MDGPFALL2020_DVD_ENUS media, it should function fine with TLS 1.0 and TLS 1.1 disabled, which sounds like what you're seeing, just with Firefox and Chrome, it doesn't work.
I'm not sure if there's something with those two browsers or not, I'd be curious if MS Edge browser works with Web Client for you or not?
I will say we haven't seen these errors yet with GP 18.3 and Web Client.
Thanks
#1
Abhilash Warrier
565
#2
Martin Dráb
536
Most Valuable Professional
#3
André Arnaud de Cal...
402
Super User 2025 Season 1
Share
Report
All responses (
Answers (
