ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY when accessing PowerShell Universal
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.
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.
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.
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 ...
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. ...
KB0011 - Are licenses different between Production, QA and Test/Development servers?
Developers licenses with limited functionality may be created for PowerShell Universal QA/Test servers by using the 'Generate Developer License' button under Settings -> License (see screenshot below) ? You must have at least 1 licensed instance of ...
PowerShell Universal crashes after upgrade to 1.5
Version: 1.5 Issue: The PowerShell Universal service will not start properly when upgrading from 1.4 to 1.5. The following error is shown in the log. Unhandled exception. System.InvalidCastException: Unable to cast object of type ...
PowerShell Universal cmdlets return a 404 over HTTPS
Version: 1.4 PowerShell Version: Windows PowerShell 5.1 Problem When issue commands against the PowerShell Universal Management API (such as Get-UAJob, Get-UAScript, etc), the cmdlet will return a 404 error. This can happen when running scripts ...