Summary

After upgrading OpenClaw from v2026.2.23 to v2026.2.26, Telegram communication became unreliable.
Gateway logs repeatedly show Network request failed for Telegram API operations (deleteWebhook, setMyCommands, sendMessage, sendChatAction, sendDocument, sendPhoto).

I verified that host-level connectivity is available (curl works), but Node HTTPS requests to https://api.telegram.org time out in this environment.

Steps to reproduce

1. Start from a working setup on v2026.2.23.
2. Upgrade to v2026.2.26.
3. Restart gateway (systemctl --user restart openclaw-gateway).
4. Observe Telegram provider startup and normal message activity.
5. Run diagnostics:
   openclaw --version

curl -sS -o /dev/null -w "curl_http=%{http_code}\n" https://api.telegram.org

node -e "fetch('https://api.telegram.org').then(r=>console.log('node_http='+r.status)).catch(e=>console.error(e.cause?.code,e.message))"

node -e "require('https').get('https://api.telegram.org',r=>{console.log('https_ok',r.statusCode);r.resume()}).on('error',e=>console.log('https_err',e.code,e.message))"

node -e "const s=require('net').connect({host:'149.154.166.110',port:443,timeout:5000},()=>{console.log('tcp_ok');s.destroy()});s.on('timeout',()=>{console.log('tcp_timeout');s.destroy()});s.on('error',e=>console.log('tcp_err',e.code));"

Expected behavior

Telegram provider initialization and message operations should succeed when host network connectivity is available.

Actual behavior

Telegram requests fail with repeated network errors, including:

• Network request for 'deleteWebhook' failed!
• Network request for 'setMyCommands' failed!
• Network request for 'deleteMyCommands' failed!
• Network request for 'sendChatAction' failed!
• Network request for 'sendMessage' failed!
• Network request for 'sendDocument' failed!
• Network request for 'sendPhoto' failed!

These failures persist even after setting:
• channels.telegram.network.autoSelectFamily = true and false
• channels.telegram.network.dnsResultOrder = "ipv4first"
• channels.telegram.streaming = "off"

OpenClaw version

v2026.2.26

Operating system

Ubuntu 24.04.4 LTS

Install method

No response

Logs, screenshots, and evidence

Representative gateway logs:
• [telegram] deleteWebhook failed: Network request for 'deleteWebhook' failed!
• [telegram] webhook cleanup failed: ... retrying ...
• [telegram] setMyCommands failed: Network request for 'setMyCommands' failed!
• [telegram] command sync failed: HttpError: Network request for 'setMyCommands' failed!
• [telegram] sendChatAction failed: Network request for 'sendChatAction' failed!
• [telegram] slash final reply failed: HttpError: Network request for 'sendMessage' failed!

Diagnostic contrast from same host:
• curl https://api.telegram.org => HTTP 302 (success)
• node fetch('https://api.telegram.org') => UND_ERR_CONNECT_TIMEOUT / ETIMEDOUT
• node https.get('https://api.telegram.org') => ETIMEDOUT
• node net.connect(149.154.166.110:443) => tcp_ok
• DNS resolves correctly (149.154.166.110, IPv4)
• openssl s_client -connect 149.154.166.110:443 -servername api.telegram.org succeeds

Impact and severity

• Severity: High
• Impact: Telegram channel is unreliable or non-functional.
• Consequence: Production chat replies are delayed or missing.

Additional information

• Issue started immediately after the upgrade to v2026.2.26.
• Network team reports no intentional blocking/filtering/inspection policy change.
• DM policy appears unrelated (set to pairing; behavior does not match DM-policy rejection).
• This reproduces during Telegram startup operations (deleteWebhook, setMyCommands), before normal chat flow.

I downgraded from v2026.2.26 back to v2026.2.23 and restarted the gateway.
The same Telegram startup failures still occur on v2026.2.23:

• deleteWebhook failed: Network request for 'deleteWebhook' failed!
• deleteMyCommands failed: Network request for 'deleteMyCommands' failed!
• setMyCommands failed: Network request for 'setMyCommands' failed!
• command sync failed: HttpError: Network request for 'setMyCommands' failed!

Node HTTPS test on the same host after downgrade still fails:

node -e "require('https').get('https://api.telegram.org',r=>{console.log('https_ok',r.statusCode);r.resume()}).on('error',e=>console.log('https_err',e.code,e.message))"

Output: https_err ETIMEDOUT

This indicates the issue is not limited to v2026.2.26 only and may be environment-specific in Node HTTPS transport to Telegram API.