ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY when accessing PowerShell Universal

ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY when accessing PowerShell Universal

Version:
​Any
Issue:
When accessing PowerShell Universal with a Chromium-based browser such as Google Chrome or Microsoft Edge, you can encounter an error when HTTPS is enabled. The error will state ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY. 
Root Cause:
The reason for this issue is because the operating system you are using does not support HTTP2. By default, PowerShell Universal will serve both HTTP1 and HTTP2 while favoring HTTP2. If you are running on an operating system, like Windows Server 2012R2, that does not support HTTP2, you will see this error in the browser.
Workaround:
To work around this issue, you can either run PowerShell Universal on an operating system that supports HTTP2 or you can turn off HTTP2 support in your appsettings.json file. 
To learn about turning off HTTP2 support, see our documentation: https://docs.ironmansoftware.com/config/hosting#protocol

    • Related Articles

    • PowerShell Universal Service crashes on startup after an upgrade to 1.4.6

      Version: PowerShell Universal 1.4.6 Issue The PowerShell Universal service will crash with the following error in Event Viewer.  Application: Universal.Server.exe CoreCLR Version: 4.700.19.56402 .NET Core Version: 3.1.0 Description: The process was ...

    • KB0002 - Security features of PowerShell Universal

      In terms of security features, PowerShell Universal currently provides: HTTPS for over the wire encryption Authentication providers such as SAML2, OpenID Connect, Windows (NTLM\Kerberos), WS-Federation, client certificate, and basic auth Role-based ...

    • KB0079 - gRPC Issues when using PowerShell Universal v5 Cmdlets

      Scope Users running PowerShell Universal v5 or later that are attempting to call cmdlets that interact with PowerShell Universal management APIs. Problem Various errors from PowerShell Universal cmdlets referring to gRPC. Root Cause The use of gRPC, ...

    • OpenID Connect does not work with HTTP

      Version: Any Problem: When configuring PowerShell Universal OpenID Connect authentication, the server will return a 500 error when attempting to authenticate.  Root Cause Chrome 80 introduced new settings that require cross-site cookies to be secure. ...

    • KB0041 - About Templates

      Purpose The purpose of this article is to provide a timeline around the Template functionality of PowerShell Universal. Background Templates were introduced to provide a starting point for newcomers to PowerShell Universal. They have since been ...