[Ubuntu 24.04][Onboard] non-interactive onboard aborts when Telegram API is unreachable

[cr7258]

Description

Description

NemoClaw v0.0.50 non-interactive onboard aborts at the optional Telegram messaging step when api.telegram.org is unreachable from the host. This breaks DevTest T5987920: optional component failures should warn, skip the optional integration, and continue onboarding; the Brave invalid-key path already behaves that way.

Environment

Device: NVIDIA A100 80GB PCIe Ubuntu server
OS: Ubuntu 24.04.4 LTS
Architecture: x86_64
Node.js: v22.22.3
npm: 10.9.8
Docker: Docker version 29.1.3, build 29.1.3-0ubuntu3~24.04.2
OpenShell CLI: openshell 0.0.44
NemoClaw: v0.0.50
OpenClaw: N/A (onboard aborted before sandbox setup completed)

Steps to Reproduce

1. Use an Ubuntu 24.04 host where outbound HTTPS to api.telegram.org is blocked or reset.

2. Install NemoClaw v0.0.50.

3. Run a non-interactive onboard with a Telegram token present and without NEMOCLAW_SKIP_TELEGRAM_REACHABILITY:

   NEMOCLAW_NON_INTERACTIVE=1 NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1 NEMOCLAW_PROVIDER=build NVIDIA_API_KEY= TELEGRAM_BOT_TOKEN=INVALID_TOKEN TELEGRAM_ALLOWED_IDS=123456 nemoclaw onboard --non-interactive --yes --fresh --name t5987920-focused --yes-i-accept-third-party-software --no-sandbox-gpu --no-gpuExpected Result

Telegram is an optional messaging integration. If Telegram validation or reachability fails, onboard should print a clear warning, skip/disable Telegram for this run, and continue to the next onboarding step. This should match the Brave optional component behavior, where an invalid Brave API key logs a warning and onboard continues.Actual Result

The onboard flow aborts in non-interactive mode as soon as api.telegram.org is unreachable:

[5/8] Messaging channels
[non-interactive] Messaging tokens detected: telegram

⚠ api.telegram.org is not reachable from this host.
Telegram integration requires outbound HTTPS access to api.telegram.org.
This is commonly blocked by corporate network proxies.
Aborting onboarding in non-interactive mode due to Telegram network reachability failure.
onboard_status=1Logs

Relevant excerpt:
T5987920 focused repro start 2026-05-26T09:46:37+00:00
curl: (35) Recv failure: Connection reset by peer
precheck_tg_curl_exit=35 http_code=000

[5/8] Messaging channels
[non-interactive] Messaging tokens detected: telegram

⚠ api.telegram.org is not reachable from this host.
Telegram integration requires outbound HTTPS access to api.telegram.org.
This is commonly blocked by corporate network proxies.
Aborting onboarding in non-interactive mode due to Telegram network reachability failure.
onboard_status=1

Bug Details

Field	Value
Priority	Unprioritized
Action	Dev - Open - To fix
Disposition	Open issue
Module	Machine Learning - NemoClaw
Keyword	NemoClaw, NEMOCLAW_GH_SYNC_APPROVAL, NemoClaw_Onboard, NemoClaw_Policy&Network

---

[NVB#6222831]

[laitingsheng]

Duplicate of #4238

[wangericnv]

Reopening — verify FAILED. The dup-of-#4238 routing did not land a fix; #4238 itself is still OPEN with no NVBug mirror, so closing this canonical issue was premature.

Re-verified on NemoClaw v0.0.52 / OpenShell 0.0.44 (DGX Spark 10.173.104.110, Ubuntu 24.04 aarch64, 2026-05-28). The repro env is a corp-network host where api.telegram.org is blocked (verified curl ... timed out after 5000ms).

NEMOCLAW_NON_INTERACTIVE=1 NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1 \
NEMOCLAW_PROVIDER=build NVIDIA_API_KEY=<key> NEMOCLAW_PROVIDER_KEY=<key> \
TELEGRAM_BOT_TOKEN='1234567890:FAKE_BUT_FORMAT_VALID_TOKEN' \
TELEGRAM_CHAT_ID='1234567890' \
TELEGRAM_AUTHORIZED_CHAT_IDS='1234567890' \
nemoclaw onboard --non-interactive --yes --no-gpu --name tg-unreach --fresh

End-of-onboard output (verbatim, on current main):

[5/8] Messaging channels
──────────────────────────────────────────────────
[non-interactive] Messaging tokens detected: telegram

⚠ api.telegram.org is not reachable from this host.
  Telegram integration requires outbound HTTPS access to api.telegram.org.
  This is commonly blocked by corporate network proxies.
Aborting onboarding in non-interactive mode due to Telegram network reachability failure.

After this output, the tg-unreach sandbox is NOT registered (nemoclaw list doesn't show it; nemoclaw tg-unreach destroy --yes returns "Sandbox 'tg-unreach' does not exist"). The onboard fully aborts at the messaging-channel step — exactly the bug's original symptom.

Suggested fix direction (matching the original report): instead of Aborting onboarding, surface ⚠ Telegram unreachable — channel will be added but bridge will not start until network reachability is restored and continue through phases [6/8]→[8/8] so the sandbox lands in a usable state for the inference-only workflows. The user can then re-enable Telegram later by running nemoclaw <name> channels add telegram once network reachability returns.

cc @laitingsheng — please confirm whether the dup-mapping to #4238 was intended to also pull this canonical issue back into the open state once #4238 progresses. Right now #4239 (this one) was marked closed against an NVBug fix that doesn't appear to have actually landed, while #4238 (the dup target) remains open. NVBug #6222831 has been reverted to Dev - Open - To fix / Open issue with the same evidence.

[laitingsheng]

#4307 is still WIP, so no fix has been merged yet. I think @cr7258 decided to use #4238 to track this issue