These are defaults, not recommendations to expose them publicly. Corresponding HOST/PORT settings change listeners; reverse proxies should route only the intended role.
Development ingress
The managed launcher defaults to a Cloudflare development channel and needs cloudflared. It forwards the credential listener, not management. Console Network & ingress displays its status; management remains independently available when the tunnel fails. The tunnel carries delegated tokens and request/response content through its service. Fixed/production networks should use a stable HTTPS origin. Example external configuration:Hosted and preview routing
Hosted requires stable HTTPS credential ingress and rejects temporary tunnels. Verify reachability from a real Sandbox: a loopback health request from the control plane is insufficient. Management remains authenticated. Previews require a dedicated wildcard domain/TLS and grant-specific subdomains, separate from Console origin. See preview limits. OAuth callbacks belong to management authorization routing; a credential tunnel is not an OAuth callback tunnel.Outbound proxies and policy
Saved outbound_proxy settings and explicit process environment govern their respective paths. Environment wins; bypass entries merge with loopback. Protected upstreams have additional destination enforcement: direct paths check public DNS and reject redirects; trusted proxy mode requires exact approved hosts.HEXAGON_ACCESS_EGRESS_PROXY_URL and HEXAGON_ACCESS_EGRESS_HOSTS configure protected upstream proxying. Hosts are exact names, not wildcards. Successful npm traffic does not prove model/Tool egress works.
Sandbox allowlists must include the credential origin hostname. Sandbox policy and control-plane Tool egress are different boundaries; see network policy.
Follow the request, not just the port
The graph describes traffic roles, not a claim that every arrow shares one authorization system. ToolBroker calls occur in the control plane; Sandbox domain allowlists do not govern that outbound path. The local-mode cloud/recovery record is evidence for its actual temporary-ingress topology, not every stable hosted origin. Repeat cloud reachability and preview isolation checks in your chosen topology.
Diagnose in order
- Confirm control-plane health and intended workspace.
- Check credential origin identity, TLS, and routing.
- Test actual Sandbox access, including allowlist restrictions.
- Check model protocol, fixed upstream, credentials, and outbound proxy.
- For previews, check process/port, grant, origin, and expiry.