discord channel configuration | Friends of the Crustacean 🦞🤝 | Page 1

spare fractal Apr 8, 2026, 6:19 AM

#

I configured the bot to my discord and the bot is online but wont respond to anything i say, ( i configured all of the channel/serverid so i know it works) and when i run a command the "application does not respond"

turbid rapidsBOT Apr 8, 2026, 6:19 AM

#

slender deltaBOT Apr 8, 2026, 6:19 AM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

flat parcelBOT Apr 8, 2026, 6:20 AM

#

Yep — “bot is online” + “application does not respond” usually means Discord is connected, but message/command handling is blocked or timing out.

First, can you paste this exactly:

openclaw --version
openclaw status
openclaw channels status --probe

Then run:

openclaw logs --follow

…and in Discord send:

#

a normal message
a slash command like /status

Paste the relevant log lines.

Most common causes for your exact symptoms:

Message Content Intent not enabled in Discord Developer Portal
Guild allowlist / mention gating blocking messages (requireMention default is often true)
User/guild/channel not allowed under channels.discord.guilds policy
DM pairing not approved (if testing in DM with pairing mode)
Native commands stale/disabled → restart needed

After any config/intents change, do:

#

openclaw gateway restart

Docs:

Discord setup/troubleshooting: https://docs.openclaw.ai/channels/discord
Channel troubleshooting flow: https://docs.openclaw.ai/channels/troubleshooting

If you share the probe + logs, I can pinpoint the exact fix fast.

spare fractal Apr 8, 2026, 6:23 AM

#

Gateway not reachable: Error: gateway timeout after 10000ms
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /home/ubuntu/.openclaw/openclaw.json
Bind: loopback
Gateway not reachable; showing config-only status.
Config: /home/ubuntu/.openclaw/openclaw.json
Mode: local

Discord default: enabled, configured, token:config

This was the 2nd attempt:

Gateway not reachable: Error: gateway timeout after 10000ms
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /home/ubuntu/.openclaw/openclaw.json
Bind: loopback
Gateway not reachable; showing config-only status.
Config: /home/ubuntu/.openclaw/openclaw.json
Mode: local

Discord default: enabled, configured, token:config

flat parcelBOT Apr 8, 2026, 6:24 AM

#

Perfect, this output already gives the root cause: this is a Gateway issue, not a Discord config issue.

Gateway not reachable ... ws://127.0.0.1:18789 means OpenClaw can read config, but the actual Gateway process isn’t reachable — so Discord commands time out with “application does not respond.”

Run these on that Ubuntu host:

openclaw --version
openclaw gateway status
openclaw gateway start
openclaw status

If it still says unreachable:

#

openclaw gateway status --deep
openclaw doctor
openclaw logs --follow

If gateway status shows a config mismatch (Config (cli) vs Config (service)), run:

openclaw gateway install --force
openclaw gateway restart

Then test Discord again.

If you paste the output of openclaw gateway status + last ~30 lines from openclaw logs --follow, I can pinpoint the exact failing piece.

#

Refs:

spare fractal Apr 8, 2026, 6:24 AM

#

for the second thing you told me to do it came back with this: 🦞 OpenClaw 2026.4.8 (9ece252) — Somewhere between 'hello world' and 'oh god what have I built.'

gateway connect failed: GatewayClientRequestError: pairing required
Gateway pairing required; reading local log file instead.
Log file: /tmp/openclaw/openclaw-2026-04-08.log
05:39:17+00:00 info gateway {"subsystem":"gateway"} starting channels and sidecars...
05:39:17+00:00 info cron {"module":"cron","storePath":"/home/ubuntu/.openclaw/cron/jobs.json"} {"enabled":true,"jobs":0,"nextWakeAtMs":null} cron: started
05:39:17+00:00 info gateway/hooks {"subsystem":"gateway/hooks"} loaded 4 internal hook handlers
05:39:44+00:00 warn bonjour {"subsystem":"bonjour"} watchdog detected non- (more here but i cant paste)

flat parcelBOT Apr 8, 2026, 6:25 AM

#

Nice — this is a useful clue.

You’re on 2026.4.8 (good), and now the blocker is:

GatewayClientRequestError: pairing required

That means your local CLI device isn’t paired/approved with the gateway yet, so status/probe commands can’t talk to it reliably.

Run this next:

openclaw devices list
openclaw devices approve --latest
openclaw status

If --latest fails, use the exact request id:

#

openclaw devices approve <requestId>

After that, run:

openclaw channels status --probe
openclaw logs --follow

Then in Discord:

send a normal message
run /status

and paste the log lines around that moment.

#

If you can’t paste full logs, run this and paste output:

grep -Ei "discord|error|warn|drop guild|mention required|allowlist|intent|interaction" /tmp/openclaw/openclaw-2026-04-08.log | tail -n 120

That should expose exactly why Discord is ignoring messages/commands.

Refs: https://docs.openclaw.ai/cli/devices and https://docs.openclaw.ai/gateway/troubleshooting

spare fractal Apr 8, 2026, 6:28 AM

#

ubuntu@vps-7083132b:~$ openclaw devices list
openclaw devices approve --latest
openclaw status

🦞 OpenClaw 2026.4.8 (9ece252) — Less clicking, more shipping, fewer "where did that file go" moments.

│
◇
[openclaw] Failed to start CLI: Error: gateway timeout after 10000ms
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /home/ubuntu/.openclaw/openclaw.json
Bind: loopback
at Timeout.<anonymous> (file:///home/ubuntu/.npm-global/lib/node_modules/openclaw/dist/call-BjnDacVz.js:460:9)
at listOnTimeout (node:internal/timers:585:17)
at process.processTimers (node:internal/timers:521:7)

🦞 OpenClaw 2026.4.8 (9ece252) — If it works, it's automation; if it breaks, it's a "learning opportunity."

│
gateway connect failed: GatewayClientRequestError: pairing required
◇
Direct scope access failed; using local fallback.
│
gateway connect failed: GatewayClientRequestError: pairing required
◇
Direct scope access failed; using local fallback.
Approved 4d1267700f1426c720cabf7652111099316f84c84631e5a29ff6b7306f7bb402 (5c329d55-9557-4377-b9c6-9286a7992222)

flat parcelBOT Apr 8, 2026, 6:28 AM

#

Nice — this confirms two things:

pairing was pending (and you approved it ✅)
gateway connectivity is still flaky (gateway timeout)

So next step is a clean gateway restart + status check.

Run one by one:

openclaw gateway stop
openclaw gateway start
openclaw gateway status

If RPC probe is still not ok, run:

#

openclaw gateway install --force
openclaw gateway restart
openclaw gateway status --deep

Then:

openclaw status
openclaw channels status --probe

If it still fails, run foreground once (best debug signal):

#

openclaw gateway run --verbose

Keep that terminal open, send a Discord message + /status, and paste the new log lines.

You’re close — the Discord side isn’t the main issue right now; it’s the gateway process/reachability path.

spare fractal Apr 8, 2026, 6:30 AM

#

ubuntu@vps-7083132b:~$ openclaw gateway install --force
openclaw gateway restart
openclaw gateway status --deep

🦞 OpenClaw 2026.4.8 (9ece252) — Finally, a use for that always-on Mac Mini under your desk.

Installed systemd service: /home/ubuntu/.config/systemd/user/openclaw-gateway.service
Previous unit backed up to: /home/ubuntu/.config/systemd/user/openclaw-gateway.service.bak

🦞 OpenClaw 2026.4.8 (9ece252) — The only crab in your contacts you actually want to hear from. 🦞

Restarted systemd service: openclaw-gateway.service

🦞 OpenClaw 2026.4.8 (9ece252) — Your second brain, except this one actually remembers where you left things.

│
◇
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-04-08.log
Command: /usr/bin/node /home/ubuntu/.npm-global/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789

Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: running (pid 29977, state active, sub running, last exit 0, reason 0)
Warm-up: launch agents can take a few seconds. Try again shortly.
RPC probe: failed
RPC target: ws://127.0.0.1:18789
timeout

Port 18789 is already in use.

pid 29977 ubuntu: openclaw-gateway (127.0.0.1:18789)
Gateway already running locally. Stop it (openclaw gateway stop) or use a different port.
Listening: 127.0.0.1:18789
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting
ubuntu@vps-7083132b:~$

flat parcelBOT Apr 8, 2026, 6:31 AM

#

This is super helpful — we’ve narrowed it down a lot.

You now have:

✅ service installed correctly
✅ same config for CLI + service
✅ process listening on 127.0.0.1:18789
❌ RPC probe timeout (gateway process is up but not answering RPC)

That usually means the gateway is stuck during runtime init / event loop.

Next exact step (best signal)

openclaw gateway stop
openclaw gateway run --verbose

#

Leave that running. In another SSH session, do:

openclaw status

Then send a Discord message + /status, and paste the verbose logs from the foreground terminal.

If you want a quick log filter first, run:

tail -n 300 /tmp/openclaw/openclaw-2026-04-08.log | grep -Ei "error|warn|timeout|discord|watchdog|unhandled|intent|allowlist|drop"

At this point we need the runtime error line to pinpoint the exact fix.

#

(You’re very close — this is no longer “Discord setup wrong,” it’s gateway runtime not responding.)

spare fractal Apr 8, 2026, 6:36 AM

#

ubuntu@vps-7083132b:~$ openclaw gateway stop
openclaw gateway run --verbose

🦞 OpenClaw 2026.4.8 (9ece252) — I can grep it, git blame it, and gently roast it—pick your coping mechanism.

Stopped systemd service: openclaw-gateway.service

🦞 OpenClaw 2026.4.8 (9ece252) — Built by lobsters, for humans. Don't question the hierarchy.

│
◇
06:32:38+00:00 [gateway] loading configuration…
06:32:38+00:00 [gateway] resolving authentication…
06:32:38+00:00 [gateway] starting...
06:32:40+00:00 Registered plugin command: /pair (plugin: device-pair)
06:32:40+00:00 Registered plugin command: /phone (plugin: phone-control)
06:32:40+00:00 Registered plugin command: /voice (plugin: talk-voice)
06:32:41+00:00 [gateway] starting HTTP server...
06:32:41+00:00 [canvas] host mounted at http://127.0.0.1:18789/__openclaw__/canvas/ (root /home/ubuntu/.openclaw/canvas)
06:32:41+00:00 mcp loopback listening on 127.0.0.1:43341
06:32:41+00:00 [gateway] MCP loopback server listening on http://127.0.0.1:43341/mcp
06:32:41+00:00 bonjour: starting (hostname=openclaw, instance="vps-7083132b (OpenClaw)", gatewayPort=18789, minimal=true)
06:32:41+00:00 [heartbeat] started
06:32:41+00:00 [health-monitor] started (interval: 300s, startup-grace: 60s, channel-connect-grace: 120s)
06:32:41+00:00 [gateway] agent model: openai-codex/gpt-5.4
06:32:41+00:00 [gateway] ready (6 plugins, 2.7s)
06:32:41+00:00 [gateway] log file: /tmp/openclaw/openclaw-2026-04-08.log
06:32:41+00:00 [gateway] security warning: dangerous config flags enabled: gateway.controlUi.allowInsecureAuth=true. Run openclaw security audit.
06:32:41+00:00 [gateway] starting channels and sidecars...
06:32:41+00:00 [hooks:loader] Registered hook: boot-md -> gateway:startup
06:32:41+00:00 [hooks:loader] Registered hook: bootstrap-extra-files -> agent:bootstrap
06:32:41+00:00 [hooks:loader] Registered hook: command-logger -> command
06:32:41+00:00 [hooks:loader] Registered hook: session-memory -> command:new, command:reset
06:32:41+00:00 [hooks] loaded 4 internal hook handlers
06:33:13+00:00 [bonjour] watchdog detected non-announced service; attempting re-advertise (gateway fqdn=vps-7083132b (OpenClaw)._openclaw-gw._tcp.local. host=openclaw.local. port=18789 state=probing)
06:33:14+00:00 [bedrock-mantle-discovery] Mantle IAM token generation unavailable
06:33:22+00:00 [bonjour] restarting advertiser (service stuck in announcing for 8660ms (gateway fqdn=vps-7083132b (OpenClaw)._openclaw-gw._tcp.local. host=openclaw.local. port=18789 state=announcing))
06:33:22+00:00 bonjour: ignoring unhandled ciao rejection: CIAO ANNOUNCEMENT CANCELLED
06:33:25+00:00 [plugins] embedded acpx runtime backend registered (cwd: /home/ubuntu/.openclaw/workspace)
06:33:25+00:00 [browser] control listening on http://127.0.0.1:18791/ (auth=token)
06:33:25+00:00 Registered plugin command: /pair (plugin: device-pair)
06:33:26+00:00 Registered plugin command: /dreaming (plugin: memory-core)
06:33:26+00:00 Registered plugin command: /phone (plugin: phone-control)
06:33:26+00:00 Registered plugin command: /voice (plugin: talk-voice)
06:33:26+00:00 [plugins] hook runner initialized with 1 registered hooks
06:33:26+00:00 [hooks] boot-md skipped for agent startup run
06:33:26+00:00 [plugins] embedded acpx runtime backend ready
06:33:26+00:00 [discord] [default] Discord Message Content Intent is limited; bots (+ more) this was from the openclaw gateway stop
openclaw gateway run --verbose

flat parcelBOT Apr 8, 2026, 6:36 AM

#

Yep — you found the smoking gun:

[discord] ... Discord Message Content Intent is limited ...

That’s exactly why it appears online but ignores normal messages.

Fix this in Discord Developer Portal

Go to Discord Developer Portal → Your App → Bot
Under Privileged Gateway Intents, enable:

✅ Message Content Intent (required)
✅ Server Members Intent (recommended)

Save changes.

Then restart OpenClaw:

#

openclaw gateway restart
openclaw channels status --probe

Also verify slash command setup (for “application does not respond”)

When inviting bot, scopes should include:

bot
applications.commands

If unsure, re-generate invite URL with those and re-invite.

The other warnings you pasted (bonjour, bedrock-mantle) are not the main blocker here.

#discord channel configuration

Next exact step (best signal)

Fix this in Discord Developer Portal

Also verify slash command setup (for “application does not respond”)