#No response from Discord, "awaiting gateway readiness"

1 messages Β· Page 1 of 1 (latest)

wispy sonnet
#

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
hallow roverBOT
quaint hemlockBOT
#

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

hallow roverBOT
mighty socketBOT
#

You’re actually farther along than it feels. From that output, Discord itself is connected:

  • bot token is loaded
  • bot logged in as @Dross
  • channel status says works

Also, awaiting gateway readiness is just the startup status string before Discord fully finishes logging in. If status --all now says works, that is probably not the current blocker.

The next split is: are you testing in a DM with the bot, or in a server channel?

A very common Discord footgun is this:

  • if you only set DISCORD_BOT_TOKEN and never added a channels.discord config block, Discord falls back to groupPolicy: "allowlist"
  • that means the bot can be online and healthy, but still ignore guild messages

Also, since your status shows intents:content=limited, for a first test I’d try explicitly mentioning the bot in the server channel.

Can you paste these next, with secrets redacted: