Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Telegram plugin entry file missing in v2026.4.7 causes gateway startup failure [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#63115•Fetched 2026-04-09 07:58:23
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Mubai1124Mubai1124
Participants
Mubai1124Mubai1124

OpenClaw v2026.4.7 fails to start due to a missing Telegram plugin entry file. The error occurs when loading the Telegram channel setup plugin.

Error Message

🦞 OpenClaw 2026.4.7 (5050017)

Config invalid File: ~/.openclaw/openclaw.json Problem:

  • <root>: read failed: Error: bundled plugin entry "./src/channel.setup.js" failed to open from ".../dist/extensions/telegram/setup-entry.js" (resolved ".../dist/extensions/telegram/src/channel.setup.js", plugin root ".../dist/extensions/telegram", reason "path"): ENOENT: no such file or directory, lstat '.../dist/extensions/telegram/src/channel.setup.js'

Run: openclaw doctor --fix

Root Cause

OpenClaw v2026.4.7 fails to start due to a missing Telegram plugin entry file. The error occurs when loading the Telegram channel setup plugin.

Fix Action

Workaround

Downgrade to v2026.4.2:

npm install -g [email protected]

Code Example

🦞 OpenClaw 2026.4.7 (5050017)

Config invalid
File: ~/.openclaw/openclaw.json
Problem:
 - <root>: read failed: Error: bundled plugin entry "./src/channel.setup.js" failed to open from ".../dist/extensions/telegram/setup-entry.js" (resolved ".../dist/extensions/telegram/src/channel.setup.js", plugin root ".../dist/extensions/telegram", reason "path"): ENOENT: no such file or directory, lstat '.../dist/extensions/telegram/src/channel.setup.js'

Run: openclaw doctor --fix

---

npm install -g openclaw@2026.4.2
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

OpenClaw v2026.4.7 fails to start due to a missing Telegram plugin entry file. The error occurs when loading the Telegram channel setup plugin.

Steps to reproduce

  1. Upgrade from v2026.4.2 to v2026.4.7 via npm install -g openclaw@latest
  2. Run openclaw gateway restart
  3. Gateway fails to start with config validation error

Expected behavior

Gateway should start successfully after upgrade.

Actual behavior

Gateway fails with the following error:

🦞 OpenClaw 2026.4.7 (5050017)

Config invalid
File: ~/.openclaw/openclaw.json
Problem:
 - <root>: read failed: Error: bundled plugin entry "./src/channel.setup.js" failed to open from ".../dist/extensions/telegram/setup-entry.js" (resolved ".../dist/extensions/telegram/src/channel.setup.js", plugin root ".../dist/extensions/telegram", reason "path"): ENOENT: no such file or directory, lstat '.../dist/extensions/telegram/src/channel.setup.js'

Run: openclaw doctor --fix

Additional observations

  • Running openclaw doctor --fix clears the entire config file, which is unexpected behavior
  • The setup-entry.js file exists in the telegram extension directory, but the code is looking for ./src/channel.setup.js which does not exist
  • Downgrading to v2026.4.2 resolves the issue

OpenClaw version

  • v2026.4.7 (clean install via npm)

Operating system

Linux (x86_64), Node.js v22.22.0

Install method

npm global

Workaround

Downgrade to v2026.4.2:

npm install -g [email protected]

Impact and severity

High - Users cannot upgrade to v2026.4.7 if they have Telegram channel configured.

extent analysis

TL;DR

The most likely fix is to downgrade OpenClaw to version 2026.4.2 until the issue with the missing Telegram plugin entry file is resolved.

Guidance

  • Verify that the setup-entry.js file exists in the telegram extension directory, but note that the code is looking for ./src/channel.setup.js which does not exist, indicating a potential misconfiguration or bug in the plugin loading mechanism.
  • Check the OpenClaw configuration file ~/.openclaw/openclaw.json for any references to the missing channel.setup.js file and consider manually updating or removing these references.
  • Avoid running openclaw doctor --fix as it clears the entire config file, and instead try to manually resolve the configuration issue or seek further assistance.
  • If downgrading to v2026.4.2 is not a viable long-term solution, consider reporting the issue to the OpenClaw developers or waiting for a patch release that addresses the problem.

Example

No code snippet is provided as the issue seems to be related to a configuration or plugin loading problem rather than a code-level issue.

Notes

The issue appears to be specific to the interaction between OpenClaw version 2026.4.7 and the Telegram channel setup plugin. Downgrading to version 2026.4.2 resolves the issue, but this may not be a suitable long-term solution.

Recommendation

Apply the workaround by downgrading to version 2026.4.2, as this is the only known solution that allows the gateway to start successfully with the Telegram channel configured.

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

Gateway should start successfully after upgrade.

#permission error#memory optimization#batch processing#GPU compatibility#latency issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING