Recent Articles
KB0082 - Why is PSU listening on port 5000 even though it is not configured to?
Background You have PSU setup using only HTTPS (typically on port 443) by way of the appsettings.json file located in $Env:ProgramData\PowerShellUniversal[1]. Problem The PSU instance is listening on two ports: the default port of 5000 and the port ...
KB3012 - PowerShell Pro Tools feature not working
Scope This article only applies to features of PowerShell Pro Tools for VS Code. Problem A feature (e.g. Refactoring) doesn't work even though you expect it to. Symptoms No action occurs when invoking one of the PowerShell Pro Tools features from the ...
KB0081 - unknown certificate lookup failure during git sync
Scope Users attempting to configure git sync against a self-hosted git repository such as GitLab. Problem The git client cannot perform a clone, pull or push. With the error unknown certificate lookup failure: 16777280. Root Cause The certificate ...
KB0080 - Failed to Locate Secret in Database or Vault
Scope Users running PowerShell Universal 5.0.16 attempting to run a script as another user based on a new secret PSCredential variable. Problem When attempting to run the script as the user stored in the PSCredential secret, the application reports ...
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, ...
Frequently Asked Questions
For articles about the Ironman Software Storefront (FastSpring)