#No response from Discord, "awaiting gateway readiness"

1 messages · Page 1 of 1 (latest)

somber mist
#

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
covert geyserBOT
mortal sinewBOT
#

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

covert geyserBOT
smoky quarryBOT
#

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

From what you pasted, Discord itself looks healthy:

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

So this usually means the problem is not Podman/WSL or the Discord token. It is usually one of these:

  1. Guild/channel policy is blocking replies

    • groupPolicy: "allowlist"
    • missing channels.discord.guilds.<server_id>
    • requireMention: true

  2. DM pairing is still pending

    • Discord DMs default to pairing mode
#
  1. Message Content Intent is not really enabled
    • docs say it is required

One very common gotcha from the docs: if you only set DISCORD_BOT_TOKEN and do not define a channels.discord block, OpenClaw falls back to groupPolicy="allowlist", so the bot can look “connected and working” but still stay silent in server channels.

Please paste these next:

podman exec -it openclaw openclaw channels status --probe
podman exec -it openclaw openclaw config get channels.discord
podman exec -it openclaw openclaw pairing list discord

And tell me:

  • is the failing test in a DM or a server channel?
  • if it is a server channel, are you @mentioning the bot?