#OpenClaw Telegram provider regression on Windows after update

1 messages · Page 1 of 1 (latest)

finite gull
#

OpenClaw Telegram provider regression on Windows after 2026.4.23

Environment:

  • Windows 11
  • Local gateway: 127.0.0.1:18789
  • Telegram channel enabled
  • Discord disabled
  • ACPX enabled
  • Model: openai/gpt-5.5

Version behaviour:

  • 2026.4.23 works
  • 2026.4.24 / 2026.4.25 / 2026.4.26 fail

Main symptoms:
Gateway starts and reaches “ready”, but Telegram provider repeatedly fails webhook cleanup and command sync.

Relevant logs:
[telegram] deleteWebhook failed: Network request for 'deleteWebhook' failed!
[telegram] webhook cleanup failed: Network request for 'deleteWebhook' failed!; retrying
[telegram] deleteMyCommands failed: Network request for 'deleteMyCommands' failed!
[telegram] setMyCommands failed: Network request for 'setMyCommands' failed!
[telegram] command sync failed: HttpError: Network request for 'setMyCommands' failed!

Also seeing Bonjour instability:
[plugins] bonjour: watchdog detected non-announced service; attempting re-advertise
[plugins] bonjour: restarting advertiser (service stuck in probing/unannounced)

Extra details:

  • Direct PowerShell requests to api.telegram.org return HTTP 200 OK.
  • Manual webhook clearing was attempted.
  • Session locks were cleared.
  • Removing stale sessions was attempted.
  • Rolling back to 2026.4.23 restores functionality.

This looks like a regression in Telegram provider HTTP handling on Windows after 2026.4.23, possibly related to the runtime/fetch layer or plugin dependency changes.

mighty quiverBOT
#

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

slow mauveBOT
#

This does look like a real regression, not a stale-session/config issue.

Given:

  • 2026.4.23 works
  • 2026.4.24+ fails on the same Windows host
  • both deleteWebhook and setMyCommands fail
  • PowerShell can reach api.telegram.org

…I’d pin to 2026.4.23 for now and file this as a GitHub issue: https://github.com/openclaw/openclaw/issues

Useful things to include:

openclaw --version
node -v