FAQ
Answers to common setup, security, and capability-boundary questions for the shipped auth + proxy stack.
Quick answers for the questions we hear most during local setup and security review.
Setup
What do I need installed?
Go 1.25+, Docker Desktop (or Docker Engine + Compose), make, and pnpm 9.x for the docs site. See TOOLCHAIN.md in the engineering docs.
Which ports does local dev use?
| Service | Port |
|---|---|
| Proxy HTTP | 8080 |
| Auth gRPC | 9091 |
| Postgres | 5432 |
| Redis | 6379 |
Boot the stack:
git clone https://github.com/Rick1330/ibex-harness.git
cd ibex-harness
make compose-dev-up
make db-migrateSecurity
Does the proxy fail open on rate limits?
Yes — if Redis is unreachable, requests proceed without rate limiting. This is intentional for availability; see the security integration tests in services/proxy.
Does agent verification fail closed?
Yes. A missing or cross-org X-IBEX-Agent-ID returns 403 before the request reaches provider logic.
Capability boundary
Why do I sometimes see 501 PROVIDER_NOT_CONFIGURED?
That code means the model id is not registered in the active provider registry (typo, or missing from defaults / IBEX_LLM_EXTRA_MODELS). In non-production environments, default IBEX_LLM_MODE=mock returns HTTP 200 for registered models. Mock mode is rejected when IBEX_ENV=production — use IBEX_LLM_MODE=live with OPENAI_API_KEY for live forwarding. See Provider adapters and Chat completions.
Where is the dashboard?
The operator dashboard is Phase 3+. Today the shipped surface is API-only: proxy + auth + this docs site. See current state.
Still stuck?
Open a GitHub issue with your request_id from the error envelope.
Was this page helpful?
Last updated on