Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: cron status abnormal when Discord plugin is enabled (v2026.3.24) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#55561•Fetched 2026-04-08 01:38:01
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
kurodzkurodz
Participants
kurodzkurodz
Timeline (top)
labeled ×2

When the Discord plugin is enabled, openclaw cron status fails with a gateway closed error. Disabling the Discord plugin restores normal behavior. Issue introduced in v2026.3.24.

Error Message

When the Discord plugin is enabled, openclaw cron status fails with a gateway closed error. 3. Observe gateway closed error gateway connect failed: Error: gateway closed (1000): ◇ Error: gateway closed (1000 normal closure): no close reason

Root Cause

When the Discord plugin is enabled, openclaw cron status fails with a gateway closed error. Disabling the Discord plugin restores normal behavior. Issue introduced in v2026.3.24.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

When the Discord plugin is enabled, openclaw cron status fails with a gateway closed error. Disabling the Discord plugin restores normal behavior. Issue introduced in v2026.3.24.

Steps to reproduce

  1. Enable Discord plugin
  2. Run openclaw cron status
  3. Observe gateway closed error

Expected behavior

openclaw cron status should return normal status regardless of which plugins are enabled.

Actual behavior

Command fails with:

gateway connect failed: Error: gateway closed (1000): ◇ Error: gateway closed (1000 normal closure): no close reason Gateway target: ws://127.0.0.1:18789 Source: local loopback Config: /home/node/.openclaw/openclaw.json Bind: lan

OpenClaw version

2026.3.24

Operating system

Synology NAS (Docker container)

Install method

Docker container (custom Dockerfile based on ghcr.io/openclaw/openclaw:latest)

Model

codex/gpt5.4

Provider / routing chain

openclaw -> OpenAI Oauth -> openai-codex/gpt5.4

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

  • Downgrading to v2026.3.23 resolves the issue
  • Disabling the Discord plugin on v2026.3.24 also resolves the issue
  • Gateway bind: lan (0.0.0.0:18789)

extent analysis

Fix Plan

The fix involves updating the Discord plugin to properly handle gateway connections.

  • Update the Discord plugin to the latest version.
  • Modify the openclaw.json configuration file to include the following settings:
{
  "plugins": {
    "discord": {
      "gateway": {
        "bind": "0.0.0.0:18789",
        "protocol": "ws"
      }
    }
  }
}
  • In the Discord plugin code, ensure that the gateway connection is properly closed when the plugin is disabled:
// discord-plugin.js
module.exports = {
  // ...
  stop: async () => {
    // Close the gateway connection when the plugin is stopped
    await gateway.close();
  }
};

Verification

To verify that the fix worked, follow these steps:

  • Enable the Discord plugin.
  • Run openclaw cron status and check that it returns the normal status without any gateway closed errors.
  • Disable the Discord plugin and run openclaw cron status again to ensure that it still works as expected.

Extra Tips

  • Ensure that the Discord plugin is properly configured and updated to the latest version.
  • Check the OpenClaw logs for any errors related to the Discord plugin or gateway connections.
  • If issues persist, try downgrading to v2026.3.23 or disabling the Discord plugin to isolate the problem.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

openclaw cron status should return normal status regardless of which plugins are enabled.

#pipeline error#runtime error#dependency conflict#environment setup#docker error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING