Get-PSUEndpoint : Status(StatusCode="Unavailable", Detail="Error starting gRPC call
PSU Server 2026.2.5
PSU Agent : 2026.2.5
can someone help me to figure out this please ?
thanks
Get-PSUComputer | Where-Object { $_.name -eq "SRV-AGENT" }
Id : 3
Name : SRV-AGENT
HeartBeat : 13/09/2026 12:18:32
Status : Online
GrpcPort : 0
LoadingInfo :
Maintenance : False
Deleted : False
LoginErrorMessage :
Tags :
HangfireServerId :
HangfireWorkerCounter : 0
Version : 2026.2.5
FileSyncTimestamp : 01/01/0001 00:00:00
ReadOnly : False
DeploymentVersion :
DeploymentName :
GitSettings :
GitBranch :
Type : Agent
GitSshKey :
EditMode : Gui
DataItems :
Get-PSUEventHubConnection -Active
Id : 28
UserName : PSU_AGENT_SRV-AGENT
RemoteIpAddress : IP
RemoteComputer : SRV-AGENT
EventHub : PSU_HUB_VP-IDSE-A01
Computer : PSU-SRV
Connected : 13/09/2026 12:18:32
Disconnected :
ConnectionId : BciHPrffvmk9iwy-bjfRPg
RemoteUserName : SRV-AGENT$
RemoteDomainName : DOMAIN
Version : 2026.2.5
RemoteIpv6Address : ::ffff:10.205.128.9
Description : PSU_AGENT_SRV-AGENT
do port 5000 to be opened on Agent and do PSU serveur able to contact the Agent from that port ?
Id : 3
Name : SRV-AGENT
HeartBeat : 13/09/2026 12:18:32
Status : Online
GrpcPort : 0
LoadingInfo :
Maintenance : False
Deleted : False
LoginErrorMessage :
Tags :
HangfireServerId :
HangfireWorkerCounter : 0
Version : 2026.2.5
FileSyncTimestamp : 01/01/0001 00:00:00
ReadOnly : False
DeploymentVersion :
DeploymentName :
GitSettings :
GitBranch :
Type : Agent
GitSshKey :
EditMode : Gui
DataItems :
Get-PSUEndpoint -ComputerName SRV
Get-PSUEndpoint : Status(StatusCode="Unavailable", Detail="Error starting gRPC call. HttpRequestException: An error occurred while sending the request. WebException: Unable to connect to the remote server SocketException: A connection attempt failed because the
connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond IP:5000", DebugException="System.Net.Http.HttpRequestException: An error occurred while sending the request.")
At line:1 char:1
+ Get-PSUEndpoint -ComputerName SRV-AGENT
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-PSUEndpoint], RpcException
+ FullyQualifiedErrorId : Grpc.Core.RpcException,UniversalAutomation.GetEndpointCommand
Hey,
Couple of questions that might help others identify your issue:
How/Where are you running the script?
What is your security mode?
Have you tried PSU cmdlets with the -Integrated flag?
Have you tried with with a token?
I've also found GRPC can sometimes be permission related (even though the error is sort of misleading), so ensure that you have the correct permissions to do the actions you're trying.
Hello @meunier
Thank you for the details.
Before making any firewall changes or opening port 5000 on the Agent, I would like to confirm how Get-PSUEndpoint is being used in your environment.
Your Agent is reporting as Online and there is an active EventHub connection, but the Get-PSUEndpoint call is attempting a gRPC connection to the computer specified with -ComputerName, and that connection is timing out.
Could you please confirm the following?
Where are you running this command from: directly on the PSU Server, inside a PSU script, or from an external PowerShell console?
Get-PSUEndpoint -ComputerName <COMPUTER>
What are you expecting -ComputerName to represent in this command: the PSU Server or the PSU Agent?
From the same PowerShell session, please provide the sanitized output of these commands:
Get-Help Get-PSUEndpoint -Parameter ComputerName
Get-Help Get-PSUEndpoint -Parameter Integrated
This will allow us to confirm the parameter behavior using the cmdlet included with your PSU 2026.2.5 environment before changing any network configuration.
For now, I would not recommend opening port 5000 until we confirm whether a direct PSU Server to Agent connection is actually required for the operation you are attempting.
Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, connection strings, email addresses, usernames, customer data, internal domains, hostnames, IP addresses, and private URLs.
Best regards,
Ruben Tapia