Self-hosting guide
Troubleshooting
Fixes for common issues encountered when self-hosting answerLoops.
Find your symptom below, open it, and follow the fix. Problems are grouped by where you notice them. For most of them, the first thing to check is the logs.
docker compose logs app --tail=50
docker compose logs bot --tail=50If you run the published-image or from-source stack, add -f docker-compose.ghcr.yml or -f docker-compose.prod.yml after docker compose.
Quick lookup
| What you see | Most likely cause | Jump to |
|---|---|---|
| App will not start | Missing setting, or the database is not ready | Startup and database |
ECONNREFUSED on port 5432 | Wrong database host, or Postgres still starting | Startup and database |
redirect_uri_mismatch | Google redirect URI does not match AUTH_URL | Sign-in and access |
| No sign-in button | Google credentials not set | Sign-in and access |
| No AI draft on a ticket | No usable AI key | Answers and AI |
| Bot connects but never replies | Automatic Deflections is off | Channels |
| Knowledge-base syncs never finish | Bot service is not running | Channels |
| Data gone after a restart | Volumes were deleted | Startup and database |
Startup and database
Sign-in and access
Answers and AI
Channels
Still stuck?
Gather the relevant log lines from the app and bot, and the exact error text, before you ask for help. Remove any keys or tokens first.