cloudtaser-cli wire status

Runs beacon wire-protocol diagnostics without registering a real cluster info hash. The command resolves configured beacon addresses, checks TCP and TLS reachability, and can send a throwaway registration probe to verify protocol compatibility and registration auth posture.

When a fingerprint and beacon salt are supplied, the command prints only wire.InfoHashPrefix redacted prefixes for comparison with beacon logs. It never sends those real derived hashes to the beacon.

Usage

cloudtaser-cli wire status [flags]

Examples

# Hosted beacon reachability and unauthenticated/auth-required probe
  cloudtaser-cli wire status

  # Use a ctb1 token from beacon install for authenticated diagnostics
  cloudtaser-cli wire status --beacon-token-file ./beacon.token

  # Compare redacted derived prefixes with beacon logs, without real registration
  cloudtaser-cli wire status --fingerprint <cluster-fingerprint> --beacon-salt-file ./beacon-salt

  # Include beacon /metrics evidence from the beacon host
  cloudtaser-cli wire status --metrics-address http://127.0.0.1:8080

Flags

Flag	Type	Default	Required	Description
--beacon-address	string	beacon.cloudtaser.io:443	no	beacon relay address host:port; repeat multiple addresses as a comma-separated list
--beacon-allow-insecure	bool	false	no	confirm intentional beacon TLS verification bypass for diagnostics
--beacon-auth-key	string	(empty)	no	base64-encoded beacon HMAC auth key
--beacon-auth-key-file	string	(empty)	no	path to a file containing the base64-encoded beacon HMAC auth key, or '-' for stdin
--beacon-insecure-skip-verify	bool	false	no	DANGEROUS: skip TLS certificate verification for beacon diagnostics (requires --beacon-allow-insecure)
--beacon-salt-file	string	(empty)	no	path to a file containing the hex-encoded per-cluster beacon salt, or '-' for stdin
--beacon-salt-hex	string	(empty)	no	hex-encoded per-cluster beacon salt used only to compute redacted diagnostic prefixes
--beacon-token	string	(empty)	no	opaque ctb1 beacon token from 'cloudtaser-cli beacon install' (bearer credential; prefer --beacon-token-file)
--beacon-token-file	string	(empty)	no	path to a file containing the ctb1 beacon token, or '-' for stdin
--fingerprint	string	(empty)	no	cluster fingerprint used only to compute redacted diagnostic prefixes
--help, -h	bool	false	no	help for status
--json	bool	false	no	emit diagnostics as JSON
--metrics-address	string	(empty)	no	optional beacon /metrics URL for pairing counters (for example http://127.0.0.1:8080)
--metrics-insecure	bool	false	no	allow plain-HTTP beacon metrics URL for non-loopback or scheme-less metrics addresses
--probe	bool	true	no	send a throwaway registration probe
--tenant-id	string	(empty)	no	optional wire tenant_id used when deriving registration auth for the probe
--timeout	duration	20m0s	no	maximum time for the command to complete (default 20m0s; also CLOUDTASER_TIMEOUT env)

All commands