#No response from Discord, "awaiting gateway readiness"

1 messages · Page 1 of 1 (latest)

mental hound
#

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
random frigateBOT
crimson meadowBOT
#

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

random frigateBOT
uncut minnowBOT
#

I'll dig into the specific readiness state in the Discord extension so I can tell you whether this is a real Discord problem or just a startup status message being misread.

#

Don’t give up yet, this actually looks closer than it feels.

From what you pasted, Discord itself is up:

  • token configured
  • bot connected
  • works
  • gateway reachable

So this does not look like “Discord is broken” anymore. It looks more like message flow/gating.

Also, I checked the source for that string.
awaiting gateway readiness is just the startup status before the gateway reports ready. It is not automatically a hard failure. In your case, since status --all already shows connected and works, that message is probably just an earlier startup phase, not the current blocker.

Next, please paste these:

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

Then do one test message where the bot should answer, and immediately run:

podman exec -it openclaw openclaw logs --follow

Paste the log lines around that test message.

Also tell me which case you’re testing:

  1. DM to the bot
  2. server channel/thread with @mention
  3. server channel/thread without @mention