pearl nova
Hey all — running into issue #54558. Telegram channel silently fails to register on every gateway restart. Symptoms exactly match the issue:
openclaw status shows completely empty Channels table
Bot token is valid (confirmed via getMe API call — returns correctly)
Config reads correctly (channels.telegram.enabled: true, valid botToken, dmPolicy: pairing)
Gateway runs fine, webchat works
openclaw channels status --probe shows "Gateway reachable" but no channels
No Telegram entries in logs after midnight — not erroring, just not trying to start
Steps already tried:
Multiple gateway restarts
sudo kill -9 + fresh start
openclaw doctor — fixed service entrypoint mismatch (entry.js → index.js), still broken
Reset update offset file
openclaw update to 2026.3.28
openclaw configure rerun
Environment:
OpenClaw 2026.3.28
WSL2 Ubuntu 24.04 on Windows 11
Node 24.14.1 (via nvm)
Gateway: local, loopback, port 18789, systemd user service
Any known fix or workaround?
scenic tundra