All guides
Support7 min read
Troubleshooting Guide
Solutions to common problems when installing and running OpenClaw builds.
Troubleshooting
Common Issues
"API key not found" or "Authentication failed"
•Ensure your
.env file is in the project root directory•Check that the key is correctly formatted (no extra spaces)
•Verify the key is active in your provider's dashboard
"Module not found" errors
npm install
If that doesn't work:
rm -rf node_modules package-lock.json
npm install
Agent not responding to messages
•Check your channel configuration (API keys, webhook URLs)
•Verify the agent is running:
openclaw status•Check logs:
openclaw logsMemory/performance issues
•Reduce context window size in config
•Use a lighter LLM (e.g., Claude Haiku instead of Opus)
•For ChromaDB builds, ensure you have enough RAM (8GB+ recommended)
Cron tasks not running
•Verify cron syntax at crontab.guru
•Ensure the agent process stays running (use Docker or systemd)
•Check timezone settings in your config
MCP server connection failed
•Verify the MCP server is running and accessible
•Check firewall settings
•Ensure the correct port is configured
Getting Help
•Check the build's install guide for specific instructions
•Join our Discord community for real-time support
•Open an issue on the build's page on AgentForge
•Email support@agentforge.dev
bashnpm install
bashrm -rf node_modules package-lock.json npm install