OpenClaw Beginner's Guide: 5 Most Common Problems and Solutions
📖 Glossary
AI Box (also known as Agent Computer / Agent PC), is a dedicated local hardware device that runs AI Agents. Pre-installed with an AI agent management system, plug-and-play, running 24/7. Users can remotely command AI to work via Discord, Slack, Telegram, WhatsApp, and more.
You installed OpenClaw, full of hope that your lobster would start working for you. Then it gets stuck on step one: nothing's happening. Skills won't install? WeChat integration failed? Don't panic—here are the 5 most common beginner problems and how to fix them.
Problem 1: Gateway Starts But Can't Connect ⭐⭐⭐⭐⭐
Symptom: Terminal shows Gateway running, but http://localhost:7834 is blank.
Cause: 99% of the time, the port is occupied or the firewall is blocking it.
Fixes (try in order):
- Change port: In
openclaw.yaml, changeport: 7834toport: 7835 - Check port conflict: Run
netstat -ano | findstr 7834to find what's using it - Disable firewall: Windows Firewall → Allow app → Add Python
- Run as admin: Right-click terminal → Run as administrator → Restart
# openclaw.yaml
gateway:
port: 7835
host: 0.0.0.0
Verify: After changing port, visit http://localhost:7835. If you see "OpenClaw Gateway" welcome page, you're good.
Problem 2: Skills Won't Install ⭐⭐⭐⭐
Symptom: openclaw skill install xxx errors out or installs but doesn't work.
| Cause | Check | Fix |
|---|---|---|
| Missing Python dependencies | Look for ModuleNotFoundError |
pip install <missing-package> |
| Old Node.js version | node --version |
Upgrade to v18+ |
| Network issues | ping github.com |
Use proxy or Chinese mirror |
| Permission errors | Check for Permission denied |
Run terminal as admin |
Universal fix:
openclaw update
openclaw skill cache-clear
openclaw skill install <name>
openclaw gateway --log-level debug
Problem 3: WeChat Connected But Messages Don't Arrive ⭐⭐⭐⭐
Root causes: 1. Device goes offline: WeChat auto-disconnects after prolonged inactivity 2. Message format incompatibility: Rich media (images, mini-programs) may not parse 3. Concurrency limits: Too many messages triggers rate limiting
Fixes:
wechat:
heartbeat_interval: 900 # ping every 15 min to stay alive
Add rate limiting: max 1 message per second per group, minimum 3-second gap.
Problem 4: Agent Goes Silent ⭐⭐⭐
Symptom: Agent suddenly stops responding or only sends template replies.
Debug in order:
1. Check API key balance/expiry → openclaw gateway --status
2. Check if System Prompt got corrupted → check agent.system_prompt in config
3. Check if context overflowed → set max_context_tokens limit
Most common cause: API credits ran out 💸
Set a budget: budget_limit_monthly: 100 (100 RMB/month cap) to prevent overnight runaway costs.
Problem 5: Agent Won't Schedule Tasks ⭐⭐⭐
Symptom: You said "send me a weekly report every Monday at 9 AM" but nothing ever arrives.
Fix: Scheduling requires explicit configuration:
schedules:
- name: "weekly-report"
cron: "0 9 * * 1" # Every Monday 9 AM
task: "Generate last week's business report summary, send to my WeChat"
agent: "assistant"
Common cron expressions:
0 9 * * 1 Every Monday at 9 AM
0 18 * * * Every day at 6 PM
0 9 1 * * First of month at 9 AM
*/30 * * * * Every 30 minutes
Pro Tips from Real Experience
💡 Don't rush to install 100 Skills. Use 3 core Skills first for a week. Add more once you're comfortable.
💡 Always set a budget. Agents burn API credits continuously. A monthly cap prevents waking up to a huge bill.
💡 Read the logs. Most "mysterious" problems have answers in the logs.
openclaw gateway --log-level debugis your best friend.
Bottom line: The 5 most common OpenClaw problems (can't connect / can't install / WeChat drops / goes silent / won't schedule) all have standard fixes. Know these 5, skip the detours.
OpenClaw column keeps publishing practical tips. Follow us and get your lobster running.