Skip to main content

​
Troubleshooting

Common issues when building, deploying, and running Agentbot agents.

​
Installation Issues

npm install --legacy-peer-deps
Agentbot uses React 19 which some packages haven’t updated for yet. The --legacy-peer-deps flag resolves most conflicts.
npx prisma generate
Prisma client must be generated before build. If you see @prisma/client did not initialize, run the generate command manually.
lsof -i :3000
kill -9 <PID>
Or use a different port:
PORT=3001 npm run dev

​
Deployment Issues

Check that all imports use the @/ alias correctly. The @/ prefix maps to the web/ directory. Common mistake:
// ❌ Wrong
import { auth } from '../../../lib/auth'

// ✅ Right
import { auth } from '@/app/lib/auth'
The health check at /health must respond within 60 seconds. Common causes:
  • Database connection string is wrong (check DATABASE_URL)
  • Redis isn’t reachable (check REDIS_URL)
  • Missing environment variables causing startup crash
Check Render logs for the actual error.
Agentbot reads env vars at startup. After changing them:
  • Vercel: Redeploy from dashboard or vercel --prod
  • Render: Service auto-restarts on env change
  • Local: Restart the dev server (npm run dev)

​
Agent Issues

  1. Check agent status: GET /api/agents/{id}
  2. Verify the channel token (Telegram/Discord/WhatsApp) is valid
  3. Check the agent container logs
  4. Ensure the AI provider API key is set and has credits
Each agent has a memory limit based on plan:
PlanMemory
Solo2GB
Collective4GB
Label8GB
Network16GB
If you’re hitting limits, check for memory leaks in custom skills or upgrade your plan.
# List installed skills
GET /api/agents/{id}/skills

# Reinstall a skill
POST /api/agents/{id}/skills
{ "skillId": "weather" }
Skills are loaded at agent startup. If a skill fails to load, the agent will start without it and log the error.

​
Billing Issues

The legacy /api/checkout endpoint is deprecated. Use:
GET /api/stripe/checkout?plan=solo
  1. Verify your API key is valid (test it with curl)
  2. Check the provider name matches exactly: openrouter, anthropic, openai, google, groq
  3. Ensure the key has credits/quota remaining
  4. Disable and re-enable BYOK from the billing dashboard

​
Getting Help