Gateway 문제 해결

Since the Gateway owns sessions, routing, and channels, most problems trace back to it, which makes it the first place you look. 🔧

Open the dashboard at http://127.0.0.1:18789/ to see whether your assistant and its connections are actually running and healthy.

The Gateway lives as a persistent local daemon, so if nothing responds, confirm that daemon is up before chasing anything else.

If one chat app goes quiet, the issue is often that single channel; the Gateway may be fine while one bridge dropped.

No replies in a chat can simply mean your allowFrom list does not include that sender, so OpenClaw is ignoring them on purpose.

Silence in a group is often requireMention doing its job; without the right mention pattern, OpenClaw stays quiet by design.

Many issues come from the JSON5 config at ~/.openclaw/openclaw.json, so re-read it for typos in keys or sender values.

If the assistant connects but cannot think, check that your API key for the chosen LLM provider is present and valid.

Odd startup errors often mean an old runtime; OpenClaw needs Node 22.19+ minimum, with Node 24 recommended.

If a known bug is biting you, an update may already carry the fix on your current channel.

When the cause is unclear, the /gateway/troubleshooting docs walk you through diagnosing connection and routing problems step by step.

Let us check your first troubleshooting move.

To troubleshoot, check the Gateway via the dashboard, then channels, allowlists, mentions, config, API key, and Node, and lean on the docs. 🎉