Troubleshooting¶
A collection of the most common problems and how to fix them quickly.
Quick diagnostics¶
# Container status
docker compose ps
# Last 200 log lines
docker compose logs --tail=200 -f
# Server health
curl http://localhost:8080/health
# Disk space
df -h .
# Jarvis version
docker compose exec server jarvis version
Common issues¶
❌ "Cannot connect to Docker daemon"¶
Cause: Docker not running or your user is not in the docker group.
❌ "Port 8080 already in use"¶
Cause: another process is bound to the port.
❌ Server stays unhealthy on docker compose ps¶
Look for:
database connection error→ see belowqdrant timeout→ see belowsecret key not set→ check.env
❌ "database connection error"¶
If Postgres won't start:
docker compose down
docker volume rm open-jarvis_postgres_data # ⚠️ deletes DB data
docker compose up -d
❌ Qdrant unresponsive¶
❌ Cloud LLM returns 401 / 403¶
Cause: wrong or expired API key.
- Check the key in the provider (Anthropic Console, OpenAI Dashboard, …)
- Update
.env docker compose up -d --force-recreate server
❌ Ollama "model not found"¶
❌ Mobile device pairing fails¶
- Verify desktop and mobile are on the same LAN (for the first pairing)
- If you use a reverse-proxy, check
JARVIS_PUBLIC_URLis correct and reachable - Re-issue the QR code:
docker compose exec server jarvis enroll --type=mobile
❌ "Hey Jarvis" wake-word not responding¶
- Verify app/system microphone permissions
docker compose logs voice-agent --tail=100- Realign the wake-word model:
jarvis voice retrain
❌ Not receiving push notifications¶
- iOS: check Settings → Jarvis → Notifications
- Android: check the app is not in battery optimisation
- Push token registered?
jarvis device list --type=mobile
❌ Memory "forgets" too much¶
Cause: short-term memory TTL too low.
❌ RAG cannot find a document you have¶
Backup and restore¶
Backup¶
docker compose exec postgres pg_dump -U jarvis jarvis > backup-$(date +%F).sql
docker run --rm -v open-jarvis_qdrant_data:/data -v $(pwd):/backup \
alpine tar czf /backup/qdrant-$(date +%F).tar.gz /data
Restore¶
Full reset¶
⚠️ Erases all data:
Collecting logs for support¶
Attach jarvis-logs.txt (after redacting secrets) when opening a GitHub issue.
Continue to → FAQ