Before anything else:
make application-ps shows which containers are up, and docker compose logs -f <service> shows why one is not. Most issues resolve from those two commands.Symptom index
The pages
- Common issues — startup, environment, ports, imports, health checks.
- Voice and audio — anything you can hear, or cannot.
- Telephony — the provider boundary: webhooks, applications, numbers, recordings.
- Campaigns — the orchestrator, ARQ worker, circuit breaker, and concurrency slots.
- Deployment — TLS, proxies, GPUs, disk, and volumes.
Still stuck
Collect these before opening an issue: the failing command,make application-ps, the last 100 log lines from the affected container, and your .env with every secret redacted.
Related
- Daily operations — health endpoints and which logs matter
- Ports and defaults