Updating from Moltbot (yesterday) to OpenClaw (today) broke Telegram
Yesterday I learned about this project and installed it, then today I learned it changed names (again), and tried to install it over itself.
This mostly worked, but now Telegram isn't connecting right. It does work sometimes, but it's breaking too often.
Here's what it has to say:
Setup
- Installed OpenClaw on macOS (Apple Silicon) yesterday (Jan 29).
- Today updated / ran doctor; currently on OpenClaw 2026.1.29.
- Gateway is local: bind=loopback 127.0.0.1, port 18789.
- Model auth:
- Channels: Telegram enabled, WhatsApp now disabled.
What’s broken (symptoms)
- Telegram works intermittently, but often messages get delayed/buffered and then arrive in a burst (e.g., 4 replies at once).
-
-
- During failures, bot doesn’t reliably send messages / chat actions.
What we observed in logs
- Gateway logs repeatedly show Node/Undici network failures:
-
-
-
-
- This looks like outbound HTTPS requests failing from the OpenClaw gateway process, not a Telegram token problem.
What we tested
- Network seems fine at OS level:
-
-
- Restarting macOS helped temporarily.
-
Config/actions we took
- Disabled WhatsApp plugin in config:
-
- Cleaned up old/disabled cron jobs (med reminders); kept only one active job:
- “Meds smart reminder engine (every 10 min)”
- Found duplicate LaunchAgents:
-
-
- The CLI kept reporting “other gateway-like services detected: ai.openclaw.mac”.
- Verified
- Disabled it:
- Moved plist to Trash:
- After that,
- Despite that cleanup, Telegram still flaps with the same
Hypothesis / what I’m asking Discord
- This might be a Node 22 + macOS DNS/IPv6/Undici issue causing intermittent aborts (even when curl works), or something about the gateway process environment vs. shell.
- Any known fix? (e.g. force IPv4 first with
Useful command outputs
-
-
This mostly worked, but now Telegram isn't connecting right. It does work sometimes, but it's breaking too often.
Here's what it has to say:
TL;DR for OpenClaw Discord (copy/paste)
Setup
- Installed OpenClaw on macOS (Apple Silicon) yesterday (Jan 29).
- Today updated / ran doctor; currently on OpenClaw 2026.1.29.
- Gateway is local: bind=loopback 127.0.0.1, port 18789.
- Model auth:
openai-codex- Channels: Telegram enabled, WhatsApp now disabled.
What’s broken (symptoms)
- Telegram works intermittently, but often messages get delayed/buffered and then arrive in a burst (e.g., 4 replies at once).
-
openclaw status --deep-
WARN failed (unknown) - This operation was aborted- During failures, bot doesn’t reliably send messages / chat actions.
What we observed in logs
- Gateway logs repeatedly show Node/Undici network failures:
-
TypeError: fetch failed-
Telegram network error: Network request for 'getUpdates' failed!; retrying...-
telegram sendChatAction failed: Network request ... failed!-
telegram sendMessage failed: Network request ... failed!- This looks like outbound HTTPS requests failing from the OpenClaw gateway process, not a Telegram token problem.
What we tested
- Network seems fine at OS level:
-
curl -I https://api.telegram.org-
curl https://api.telegram.org/bot<TOKEN>/getMe- Restarting macOS helped temporarily.
-
openclaw gateway restartConfig/actions we took
- Disabled WhatsApp plugin in config:
-
plugins.entries.whatsapp.enabled=false- Cleaned up old/disabled cron jobs (med reminders); kept only one active job:
- “Meds smart reminder engine (every 10 min)”
- Found duplicate LaunchAgents:
-
ai.openclaw.gateway-
ai.openclaw.mac- The CLI kept reporting “other gateway-like services detected: ai.openclaw.mac”.
- Verified
ai.openclaw.maclaunchctl list- Disabled it:
launchctl disable gui/$UID/ai.openclaw.mac- Moved plist to Trash:
~/Library/LaunchAgents/ai.openclaw.mac.plist- After that,
openclaw gateway status- Despite that cleanup, Telegram still flaps with the same
fetch failedgetUpdatesHypothesis / what I’m asking Discord
- This might be a Node 22 + macOS DNS/IPv6/Undici issue causing intermittent aborts (even when curl works), or something about the gateway process environment vs. shell.
- Any known fix? (e.g. force IPv4 first with
NODE_OPTIONS=--dns-result-order=ipv4firstUseful command outputs
-
openclaw status --deep-
openclaw logs --plainTypeError: fetch failedgetUpdates/sendMessage
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Was this page helpful?
