Adapted community discussion: Paraphrased and condensed from an anonymized public OpenClaw Discord support conversation from September 2026. Technical guidance was reviewed for OpenClaw 2026.9.3.
After upgrading, the Gateway initially refused connections on the local port. It now appears to start, but none of my configured Discord accounts come online.
A restarted service is not yet proof of a healthy Gateway. Wait for startup and verify the RPC probe before changing Discord:
openclaw gateway status --deep
openclaw channels status --probe
If the Gateway is healthy but Discord remains stopped, treat that as a channel or plugin problem rather than restarting the service repeatedly.
The Gateway probe is healthy. The default Discord account is unconfigured, but explicitly starting each named account also returns started: false.
Doctor reported that the official Discord plugin requires capability consent. Review the plugin, then enable it with the accepted capabilities and restart once:
openclaw plugins inspect discord --runtime --json
openclaw plugins enable discord --accept-capabilities
openclaw gateway restart
openclaw channels status --channel discord --probe
Accept capabilities only for the expected official plugin.
Accepting the Discord plugin capabilities fixed it. The configured accounts are starting again.
That confirms the upgrade blocker was pending plugin capability consent. Run one final openclaw status --deep and keep the capability review with the upgrade record.