Access Path Check

When clients cannot reach FinClaw, troubleshoot the access path layer by layer, working from the outside in.

1. Entry Gateway

curl -v http://<host>:26100/health

Confirm that the API Gateway (26100) is reachable, that TLS (if enabled) works correctly, and that JWT validation is not blocking legitimate requests.

2. Inbound Conversation Path

The inbound request path is: api-gateway → ag-ui-server → orchestrator → ai-infra-rs → delivery. Verify it hop by hop:

curl http://localhost:26103/health   # ag-ui-server
curl http://localhost:26102/health   # orchestrator
curl http://localhost:26450/health   # ai-infra-rs

3. Infrastructure Connectivity

Confirm that PostgreSQL (26110), TimescaleDB (26111), NATS (26112), Redis (26114), and others are reachable. For the full list of ports, see Deployment Components.

TODO: To be completed. Add troubleshooting methods for common blocking points such as firewall / SELinux / container networking.