Targets are not visible in the HCP Boundary Desktop application & CLI

Avatar
Radhu Sharma
  • Updated

Problem

There can be several reasons why a Boundary cluster might throw the following error. However, this Knowledge Base article specifically addresses the scenario where targets are suddenly not visible in the HCP Boundary Desktop application and CLI, despite having worked previously.

Error:

[2025-06-03T20:39:09.604+05:30] [warn]  Client Agent Status: {"error":"clientagentcmd.(StatusCommand).Status: client do failed: unknown: error #0: GET http://localhost:9300/v1/status giving up after 2 attempt(s): Get \"http://localhost:9300/v1/status\": dial tcp 127.0.0.1:9300: connectex: No connection could be made because the target machine actively refused it."}

 

Solutions:

Please try the below steps 

  • Restart the Affected System: If the machine has been running for a long time without a reboot, ask the user to restart it and verify if the issue is resolved.
  • Sign Out and Re-login Ask the user to sign out and then log in again to the Boundary Desktop application. This will refresh the user session.
  • Reinstall Boundary Desktop: If re-login does not resolve the issue, uninstall and then reinstall the Boundary Desktop client on the user's machine. Confirm if targets become visible afterward.
  • Please verify with your admin if you have necessary grants added to see specific targets. The below permission should be present in Scope: global, Role Name: global_anon_listing:
    ids=*;type=auth-token;actions=delete:self,list,read:self

  • If the necessary permissions are not set for the global_anon_listing role, run the following commands in the CLI as an admin user:

    Note: Replace r_PgZpgb5dP6 with your actual role ID retrieved from the global_anon_listing role.

    boundary roles add-grants -id r_PgZpgb5dP6 -grant "ids=*;type=auth-token;actions=delete:self,list,read:self"

    boundary roles set-grant-scopes -id r_PgZpgb5dP6 -grant-scope-id "this" -grant-scope-id "descendants"

 

Additional Information

In case the above steps doesn’t fix the issue, please collect the following information and contact HashiCorp Support.

  • Provide a screenshot or screen recording showing the error or issue when trying to view targets.
  • Collect Diagnostic Information:
    Linux: BOUNDARY_DESKTOP_LOG_LEVEL=debug ./boundary-desktop
    MacOS: BOUNDARY_DESKTOP_LOG_LEVEL=debug ./Boundary.app/Contents/MacOS/Boundary
    Windows: $env:BOUNDARY_DESKTOP_LOG_LEVEL='debug'; .\Boundary.exe
  • Share the log file /Library/Application Support/HashiCorp/Boundary/boundary-client-agent-state.json
  • Please run the following commands and share the full output:

boundary client-agent status

boundary client-agent resume

boundary client-agent pause

boundary cache status

boundary daemon status

Network settings:

nslookup <boundary cluster url>

netstat -nr

nslookup <boundary_dns>

echo "show State:/Network/Global/IPv4" | scutil

scutil --dns

netstat -ano 

 

Other useful links

https://developer.hashicorp.com/boundary/docs/client-agent/troubleshoot

 

Articles in this section

See more

Related articles