HashiCorp Boundary

Multi-Hop Session Failure from Non-Unique Controller Names

configuration

Multi-hop sessions fail with 'No ingress workers with valid next-hop paths could be found' error in high availability controller deployments, caused by controllers lacking unique names in their configuration.

HashiCorp Boundary insight details requires a free account. Sign in with Google or GitHub to access the full knowledge base.

Sign in to access