Troubleshooting

Start with configuration and service state:

./release/abada-platform doctor dev --no-pull
./release/abada-platform status dev
./release/abada-platform logs dev

Symptom	Check
Production config exits immediately	Replace every required placeholder in .env.prod; validate DNS, CORS and OIDC URLs
Server start stops at set ABADA_DOMAIN	Set ABADA_DOMAIN and ABADA_ACME_EMAIL in .env.server; the secrets are generated
Browser shows TRAEFIK DEFAULT CERT on the server profile	DNS for the domain and its wildcard does not reach the VM yet, port 80 is closed, or the records are proxied; see ./release/abada-platform logs server
Server sign-in returns “Invalid redirect uri”	ABADA_DOMAIN changed after the first start; rerun ./release/abada-platform up server
Port 80/443 already used	Stop the conflicting service or move Abada to a dedicated host
no matching manifest for linux/arm64/v8 with 1.0.0-rc.1	Use the current repository launcher; it detects the immutable amd64-only RC.1 images and enables Docker compatibility mode
Studio shows configuration error	Inspect the generated /config.js; all four runtime values are mandatory and URLs must be HTTP(S)
Login loops	Match redirect URI, web origin, issuer, realm and client ID exactly
Engine unhealthy	Check PostgreSQL health and engine logs; telemetry must not be the cause
No Grafana data	Confirm the telemetry overlay is present, then inspect Collector, Alloy and Grafana containers
Workflow succeeds while collector is down	Expected: telemetry export is best-effort and independent of workflow correctness
Instance stays ACTIVE at an agent node	Expected without a worker or LLM key; check the Agent Worker is Online and ABADA_AGENT_LLM_* is configured in .env.dev
Worker shows Error or Offline in Operations	Inspect last rejection and consecutive failures; verify engine URL, OIDC client credentials and LLM endpoint reachability
Agent task fails at deployment with a model error	The node’s model is outside ABADA_AGENT_ALLOWED_MODELS, or requested tools are outside ABADA_AGENT_ALLOWED_TOOLS
No Insight proposals appear	Confirm ABADA_INSIGHT_ENABLED=true and that enough terminal facts exist (thresholds under abada.insight.*); proposals are never auto-approved

Render the merged configuration without starting anything:

docker compose --env-file .env.prod \
  -f compose.yaml -f compose.prod.yaml config

Do not post .env.prod, JWTs, authorization headers or full sensitive payloads in support reports. Include exact image versions, Compose version, health output, redacted logs and the command that failed.