Need help with this specific problem
#messages consumed by long-poll but never logged or surfaced as pairing requests
rapid narwhal
Fresh install of OpenClaw 2026.4.24 on Hetzner Ubuntu 24.04 (root user). Bot connects but won't process messages — looking for ideas.
Symptom:
Token valid (confirmed via direct getMe API call)
Sending messages: getUpdates immediately returns [], so OpenClaw IS consuming updates
But openclaw pairing list telegram always returns empty
Zero log entries when messages arrive — no errors, no rejections, just silence
Already tried:
Revoked/replaced bot token
Set dmPolicy: "pairing"
Wiped ~/.openclaw/credentials and ~/.openclaw/agents
Re-ran onboard wizard fully (agent went from "bootstrapping" to "active")
Approved device scope upgrade — CLI has operator.read, .pairing, .admin, .write, .approvals, .talk.secrets
openclaw doctor reports no errors
Multiple restarts and a full server reboot
Updated 2026.4.22 → 2026.4.24
Possible lead:
Logs show repeated Unhandled promise rejection: CIAO PROBING CANCELLED from bonjour/mDNS after every restart. Each writes a stability bundle. Gateway logs ready (7 plugins: ...telegram...) but I never see the [default] starting provider (@MyBot) line. Plan tomorrow: disable mDNS via discovery.mdns.mode: "off" to see if Telegram actually initializes.
Questions:
Anyone seen Telegram updates being silently consumed without becoming pairing requests?
Is the CIAO PROBING CANCELLED issue known? Could it block channel init?
Anything else to check before filing a GitHub issue?
Happy to share redacted logs/config. Thanks!