Get-PSUScript: Status(StatusCode="Unimplemented", Detail="Bad gRPC response. HTTP status code: 404")

[Darragh]

Product: PowerShell Universal
Version: 5.0.7

Error encountered when I run the following:
Get-PSUScript -ComputerName “https://fqdn:4443” -AppToken $AppToken -TrustCertificate
Get-PSUScript: Status(StatusCode=“Unimplemented”, Detail=“Bad gRPC response. HTTP status code: 404”)

This command works:
Connect-PSUServer -ComputerName “https://fqdn:4443” -AppToken $AppToken

I have tried this from both PowerShell on another computer and from within an app running on the PSU server.
The certificate is valid and signed by an external authority.

Any ideas welcome.

App settings:

"Kestrel": {
    "Endpoints": {
      "HTTPS": {
        "Url": "https://*:4443",
        "Certificate": {
          "Subject": "fqdn",
          "Store": "My",
          "Location": "LocalMachine",
          "AllowInvalid": true
        }
      }
    },
    "RedirectToHttps": "true",
    "UseHttpSys": "false",
    "BasePath": "",
    "Hsts": {
      "MaxAgeDays": 365
    },
    "CookiePolicy": ""
  },

Also for API section in AppSettings:

"Api": {
    "OpenAPI": {
      "Name": "Endpoints",
      "Description": "Endpoints defined within the PowerShell Universal admin console.",
      "Url": "v2",
      "Version": "v2"
    },
    "Url": "https://fqdn:4443",
    "GrpcPort": 0,
    "TrustCertificate": true
  },

As I said earlier, I have tried running this interactively from Powershell and from an app. The app is running under a new environment. So not running under the integrated environment.

This is a new installation of PowerShell Universal. running version 5.7.

I have looked at the following forum posts but they haven’t provided a solution:

SSL Error with Invoke-PSUScript

Hi, we use Powershell Universal 5 on IIS. I try to use Invoke-PSUScript -Name 'Example.ps1' But i get the error Cannot retrieve the dynamic parameters for the cmdlet. Status(StatusCode=“Internal”, Detail=“Error starting gRPC call. HttpRequestException: The SSL connection could not be established, see inner exception. AuthenticationException: The remote certificate was rejected by the provided RemoteCertificateValidationCallback.”, DebugException=“System.Net.Http.HttpRequestException: The SSL …

Calling a Script job from a dashboard

OK so this seems to work. $Script = Get-PSUScript | Where-Object {$_.Name -eq "Set-SlackDisabledUsers.ps1"} Invoke-PSUScript -Script $Script -Integrated | Wait-PSUJob

[parzog]

Can you try, for testing purposes, enabling the permissive security model [1] and bypassing the Connect-PSUServer command?

[Darragh]

No difference unfortunately.

[Darragh]

Error from logs doesn’t show much more:

Ignore the -integrated flag message. Not relevant.

[16:24:38 WRN][App][DTS Operations] Integrated is no longer used.
[16:24:39 ERR][App][DTS Operations] Cannot retrieve the dynamic parameters for the cmdlet. Status(StatusCode=“Unimplemented”, Detail=“Bad gRPC response. HTTP status code: 404”)
[16:24:39 ERR][App][DTS Operations] An error occurred: Cannot retrieve the dynamic parameters for the cmdlet. Status(StatusCode=“Unimplemented”, Detail=“Bad gRPC response. HTTP status code: 404”)
Endpoint: fd065fff-a3dc-46e0-b9f7-e462a0641522
Session: ac9a2b8a-e90b-429f-95e7-a1bf1d5cb5fc, User: admdoh@dcu.ie

at fd065fff-a3dc-46e0-b9f7-e462a0641522: line 10
at fd065fff-a3dc-46e0-b9f7-e462a0641522: line 1
at User account.ps1 : line 42

at fd065fff-a3dc-46e0-b9f7-e462a0641522: line 10
at fd065fff-a3dc-46e0-b9f7-e462a0641522: line 1
at User account.ps1 : line 42

[parzog]

I’ve had the same issue - what is your infrastructure/installation method? MSI/Module/IIS (nested?)/etc? You can check through this thread and see if any of the steps I took that are mentioned are helpful:

PSU 5.0.6 gRPC Errors

Product: PowerShell Universal Version: 5.0.6 Hi all, I’ll start with some environment info - we are running PSU in a nested IIS10 configuration on a Windows server. The application pool and application were set up with the applicable setup guides for v5. We use a nested folder structure of {...}\inetpub\<version>\ acting as the version root folder, with bin and data folders underneath. Anonymous authentication is enabled at the global level within IIS, as well as for the site version we are us…

[Darragh]

I installed via MSI.
I’m not hosting through IIS.
Running on Windows 2022.
No proxy.

[Darragh]

Still looking for a solution to this.
Get-psuscript -computer “https://fqdn” -AppToken $AppToken also does not work. Provides the same error.

No longs under c:\programdata\PowerShellUniversal that indicate what the error relates to.

[parzog]

I for the life of me cannot remember how I fixed this, I’m sorry. I believe the permissive security model and TrustCertificate fixed it for my particular case, but I may be wrong. Things move too fast!

When you were trying with Connect-PSUServer, did you process in the same structure as the following?

Connect-PSUServer -ComputerName $SiteRoot -AppToken $AppToken
$PSUScripts = Get-PSUScript

I believe this should return all PSU scripts in your environment. If you are still getting the gRPC when running these exact commands, I may not be able to help unfortunately.

[parzog]

Oh - I just noticed. In your Kestrel config, can you try adding a protocol here:
Kestrel.Endpoints.HTTPS.Protocol = "Http1andHttp2"
Then, restart Universal.Server and give it another try.

This may not have any effect but it may be worth a shot.

[MikeShepard]

Having the same issue…Http1andHttp2 didn’t help.