#No response from Discord, "awaiting gateway readiness"

1 messages · Page 1 of 1 (latest)

fickle crystal
#

I'm trying to get OpenClaw setup and configured in a container on my personal PC while I wait for a Mac Mini to transfer it to. I've been working with Claude for about the past week or so and Claude has pretty much given up on trying to get Discord working and suggested moving on to other things so I'm asking here before I give up.

I've read some other similar posts so I'll add my setup information across a few posts as its a lot of text.

$ podman exec -it openclaw openclaw status --all

🦞 OpenClaw 2026.4.15 (unknown)
I'll do the boring stuff while you dramatically stare at the logs like it's cinema.

OpenClaw status --all

Overview (Response trimmed agressively)

Version: 2026.4.15 | OS: WSL2 Ubuntu | Node: 24.14.0 | Gateway: reachable (37ms)

Channels
│ Discord │ ON │ OK │ token config (sha256:0d3356dd · len 72) · accounts 1/1 │
│ default │ OK │ token:config │

  • Discord default: enabled, configured, running, connected, in:3h ago, bot:@Dross, intents:content=limited, works
rocky orbitBOT
main questBOT
#

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

rocky orbitBOT
marble craterBOT
#

Don’t give up yet, this status is actually encouraging.

What you’ve shown says the Discord transport itself is up:

  • gateway reachable
  • token loaded
  • bot connected
  • status says works

So the problem is probably not “Discord is broken”, it’s usually one of these:

  • guild/channel policy is blocking replies (groupPolicy / guilds)
  • requireMention is still on, so it ignores normal channel messages
  • DM pairing/policy is blocking DMs
  • channel permissions are missing in the specific server/channel

Also, status --all saying works only means the bot is online and connected, not that your current server/channel is allowed to trigger replies.

#

Please paste these next:

podman exec -it openclaw openclaw channels status --probe
podman exec -it openclaw openclaw pairing list discord

And then your redacted channels.discord config, especially:

  • groupPolicy
  • dmPolicy
  • dm.enabled
  • guilds
  • requireMention
  • users
  • channels

Fast self-check while you’re gathering that:

#
  • DM works, server does not → likely guild allowlist / requireMention
  • Server only works when pinging the bot → requireMention is still effectively on
  • DM does not work either → pairing or DM policy issue

One more useful test: run logs, then send one test message in Discord and paste the lines around it:

podman exec -it openclaw openclaw logs --follow

The logs usually say pretty directly whether it was dropped for mention gating or allowlist.

Docs I checked: