`nemoclaw onboard` rolls back after dashboard forward detection fails, although OpenShell forwarding works independently

### Description

`nemoclaw onboard` fails at the dashboard forward step.

During onboarding, the sandbox temporarily reaches `Ready`, and the dashboard service inside the sandbox appears to be healthy:

- `my-assistant` is shown as `Ready`
- port `18789` is listening inside the sandbox
- `curl http://127.0.0.1:18789/health` from inside the sandbox returns `HTTP/1.1 200 OK`

However, NemoClaw still reports that no active forward was found for port `18789`, fails to allocate the dashboard port, then rolls back and deletes the sandbox.

I also verified that OpenShell sandbox creation, sandbox exec, and OpenShell gRPC forwarding work independently with a simple test sandbox. Therefore, this looks specific to NemoClaw's dashboard forward creation/detection during onboarding, rather than a general OpenShell forwarding failure.


### Reproduction Steps


## Installing NeMoClaw with shell script

It was failed with `Failed to start dashboard forward on port 18789`.

The terminal (`1st terminal`) output is below.

```
$ ss -ltnp | grep -E '(:18789|:18790|:18791|:18890|:8080)' || true
$ openshell forward list || true
No active forwards.
$ NEMOCLAW_SANDBOX_GPU=0 bash -c 'curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash'

   ███╗   ██╗███████╗███╗   ███╗ ██████╗  ██████╗██╗      █████╗ ██╗    ██╗
   ████╗  ██║██╔════╝████╗ ████║██╔═══██╗██╔════╝██║     ██╔══██╗██║    ██║
   ██╔██╗ ██║█████╗  ██╔████╔██║██║   ██║██║     ██║     ███████║██║ █╗ ██║
   ██║╚██╗██║██╔══╝  ██║╚██╔╝██║██║   ██║██║     ██║     ██╔══██║██║███╗██║
   ██║ ╚████║███████╗██║ ╚═╝ ██║╚██████╔╝╚██████╗███████╗██║  ██║╚███╔███╔╝
   ╚═╝  ╚═══╝╚══════╝╚═╝     ╚═╝ ╚═════╝  ╚═════╝╚══════╝╚═╝  ╚═╝ ╚══╝╚══╝

  Launch OpenClaw in an OpenShell sandbox.


[1/3] Node.js
  ──────────────────────────────────────────────────
[WARN]  Node.js v20.19.4, npm major 10 found but NemoClaw requires Node.js >=22.16.0 and npm >=10 — upgrading via nvm…
[INFO]  nvm installer integrity verified
  ✓  Installing nvm...
  ✓  Installing Node.js 22...
default -> 22 (-> v22.22.3)
[INFO]  Node.js installed via nvm: v22.22.3 (default alias)
[WARN]  Your current shell may still resolve `node` to an older version until it's reloaded.
        Open a new terminal, or run this in your existing shell:
          source "${NVM_DIR:-$HOME/.nvm}/nvm.sh" && nvm use 22
[INFO]  Runtime OK: Node.js v22.22.3, npm 10.9.8

[2/3] NemoClaw CLI
  ──────────────────────────────────────────────────
[INFO]  Installer payload is not a persistent source checkout — installing from GitHub…
[INFO]  Installing NemoClaw from GitHub…
[INFO]  Resolved install ref: latest
  ✓  Cloning NemoClaw source
  ✓  Preparing OpenClaw package
  ✓  Installing NemoClaw dependencies
  ✓  Building NemoClaw CLI modules
  ✓  Building NemoClaw plugin
  ✓  Linking NemoClaw CLI
  ✓  Installing OpenShell CLI
[INFO]  Verified: nemoclaw is available at /home/masaki/.local/bin/nemoclaw

[3/3] Onboarding
  ──────────────────────────────────────────────────

  Detected container runtime: docker
[INFO]  Installer stdin is piped; attaching the usage notice to /dev/tty…
[INFO]  Running nemoclaw onboard…
[INFO]  Installer stdin is piped; attaching onboarding to /dev/tty…

  NemoClaw Onboarding
  ===================

  [1/8] Preflight checks
  ──────────────────────────────────────────────────
  ✓ Docker is running
  ⚠ Container DNS probe inconclusive (reason: no_output).
    docker run produced no output (timed out or failed to start)
    Proceeding. If the sandbox build later hangs at `npm ci`, see issue #2101.
  ✓ Container runtime: docker
  ✓ Container runtime resources: 24 vCPU / 94.0 GiB
  ✓ openshell CLI: openshell 0.0.39
  ✓ Port 8080 available (OpenShell gateway)
  ✓ NVIDIA GPU detected (NVIDIA GeForce RTX 4090, 23028 MB)
  ✓ Sandbox GPU: disabled by configuration
  ✓ Memory OK: 96292 MB RAM + 2047 MB swap
  NVIDIA GPU detected with working drivers, but GPU passthrough was not enabled.
  If Docker GPU support is needed, install nvidia-container-toolkit and run:
  sudo nvidia-ctk runtime configure --runtime=docker && sudo systemctl restart docker

  [2/8] Starting OpenShell gateway
  ──────────────────────────────────────────────────
  Starting OpenShell Docker-driver gateway...
  Gateway log: /home/masaki/.local/state/nemoclaw/openshell-docker-gateway/openshell-gateway.log
  OpenShell gateway compatibility patch active (host glibc 2.35 is older than openshell-gateway requirement 2.39).
  Running openshell-gateway inside a Docker compatibility container.
  Compatibility gateway bind: 0.0.0.0 (required for Docker sandbox callbacks).
  ✓ Docker-driver gateway is healthy

  [3/8] Configuring inference (NIM)
  ──────────────────────────────────────────────────
  Detected local inference option: Ollama


  Inference options:
    1) NVIDIA Endpoints
    2) OpenAI
    3) Other OpenAI-compatible endpoint
    4) Anthropic
    5) Other Anthropic-compatible endpoint
    6) Google Gemini
    7) Local Ollama (localhost:11434) — running (suggested)
    8) Model Router (experimental)

  Choose [1]: 7
  Configuring Ollama systemd loopback override...
  Applying an Ollama systemd override (OLLAMA_HOST=127.0.0.1:11434). The next steps use sudo to write the drop-in, reload systemd, and restart the service; you may be prompted for your password.
  ✓ Using Ollama on localhost:11434 (proxy on :11435)

  Ollama models:
    1) gemma4:31b
    2) bge-m3:latest
    3) gpt-oss:20b
    4) Other...

  Choose model [1]: 3
  Loading Ollama model: gpt-oss:20b
  Chat Completions API available — OpenClaw will use openai-completions.
  Sandbox name (1-63 characters, lowercase, starts with a letter, letters/numbers/internal hyphens only, ends with letter/number) [my-assistant]: my-assistant

  ──────────────────────────────────────────────────
  Review configuration
  ──────────────────────────────────────────────────
  Provider:      ollama-local
  Model:         gpt-oss:20b
  API key:       (not required for ollama-local)
  Web search:    disabled
  Managed tools: none
  Messaging:     none
  Sandbox name:  my-assistant
  Note:          Sandbox build typically takes 3–8 minutes on this host.
  ──────────────────────────────────────────────────
  Web search and messaging channels will be prompted next.
  Apply this configuration? [Y/n]: Y

  [4/8] Setting up inference provider
  ──────────────────────────────────────────────────
✓ Active gateway set to 'nemoclaw'
✓ Updated provider ollama-local
Gateway inference configured:

  Route: inference.local
  Provider: ollama-local
  Model: gpt-oss:20b
  Version: 4
  Timeout: 180s
  Priming Ollama model: gpt-oss:20b
  ✓ Inference route set: ollama-local / gpt-oss:20b
  Enable Brave Web Search? [y/N]: N

  [5/8] Messaging channels
  ──────────────────────────────────────────────────

  Available messaging channels:
    [1] ○ telegram — Telegram bot messaging
    [2] ○ discord — Discord bot messaging
    [3] ○ wechat — WeChat (personal) bot messaging
    [4] ○ slack — Slack bot messaging
    [5] ○ whatsapp — WhatsApp Web messaging (QR pairing)

  Press 1-5 to toggle, Enter when done:
  Skipping messaging channels.

  [6/8] Creating sandbox
  ──────────────────────────────────────────────────
  Creating sandbox 'my-assistant' (this takes a few minutes on first run)...
  Pinning base image to sha256:62abb74f274f...
  Building sandbox image...
  Building image openshell/sandbox-from:1779442118 from /tmp/nemoclaw-build-4XNnhW/Dockerfile
  Step 1/74 : ARG BASE_IMAGE=ghcr.io/nvidia/nemoclaw/sandbox-base@sha256:62abb74f274fcb4ee1a2b96f57f437ea581937b4...
  Step 2/74 : FROM node:22-trixie-slim@sha256:2d9f5c76c8f4dd36e8f253bee5d828a83a6c09f36188f0b0414325232e0b175d AS...
  Step 3/74 : ENV NPM_CONFIG_AUDIT=false     NPM_CONFIG_FUND=false     NPM_CONFIG_UPDATE_NOTIFIER=false     NPM_C...
  Step 4/74 : COPY nemoclaw/package.json nemoclaw/package-lock.json nemoclaw/tsconfig.json /opt/nemoclaw/
  Step 5/74 : COPY nemoclaw/src/ /opt/nemoclaw/src/
  Step 6/74 : WORKDIR /opt/nemoclaw
  Step 7/74 : RUN npm ci && npm run build
  Step 8/74 : FROM ${BASE_IMAGE}
  Step 9/74 : RUN set -eu;     apt-mark manual procps e2fsprogs 2>/dev/null || true;     (apt-get remove --purge ...
  Step 10/74 : COPY --from=builder /opt/nemoclaw/dist/ /opt/nemoclaw/dist/
  Step 11/74 : COPY nemoclaw/openclaw.plugin.json /opt/nemoclaw/
  Step 12/74 : COPY nemoclaw/package.json nemoclaw/package-lock.json /opt/nemoclaw/
  Step 13/74 : COPY nemoclaw-blueprint/ /opt/nemoclaw-blueprint/
  Step 14/74 : RUN chmod -R a+rX /opt/nemoclaw-blueprint/
  Step 15/74 : WORKDIR /opt/nemoclaw
  Step 16/74 : ENV NPM_CONFIG_AUDIT=false     NPM_CONFIG_FUND=false     NPM_CONFIG_UPDATE_NOTIFIER=false     NPM_...
  Step 17/74 : RUN npm ci --omit=dev
  Step 18/74 : COPY scripts/patch-openclaw-tool-catalog.js /usr/local/lib/nemoclaw/patch-openclaw-tool-catalog.js
  Step 19/74 : RUN chmod 755 /usr/local/lib/nemoclaw/patch-openclaw-tool-catalog.js
  Step 20/74 : RUN set -eu;     MIN_VER=$(grep -m 1 'min_openclaw_version' /opt/nemoclaw-blueprint/blueprint.yaml...
  Step 21/74 : RUN set -eu;     OC_DIST=/usr/local/lib/node_modules/openclaw/dist;     fg_export="$(grep -RIlE --...
  Step 22/74 : RUN node /usr/local/lib/nemoclaw/patch-openclaw-tool-catalog.js     /usr/local/lib/node_modules/op...
  Step 23/74 : RUN mkdir -p /sandbox/.nemoclaw/blueprints/0.1.0     && cp -r /opt/nemoclaw-blueprint/* /sandbox/....
  Step 24/74 : COPY scripts/lib/sandbox-init.sh /usr/local/lib/nemoclaw/sandbox-init.sh
  Step 25/74 : COPY scripts/nemoclaw-start.sh /usr/local/bin/nemoclaw-start
  Step 26/74 : COPY nemoclaw-blueprint/scripts/*.js /usr/local/lib/nemoclaw/preloads/
  Step 27/74 : COPY scripts/codex-acp-wrapper.sh /usr/local/bin/nemoclaw-codex-acp
  Step 28/74 : COPY scripts/generate-openclaw-config.py /usr/local/lib/nemoclaw/generate-openclaw-config.py
  Step 29/74 : COPY scripts/seed-wechat-accounts.py /usr/local/lib/nemoclaw/seed-wechat-accounts.py
  Step 30/74 : COPY nemoclaw-blueprint/openclaw-plugins/ /usr/local/share/nemoclaw/openclaw-plugins/
  Step 31/74 : RUN chmod 755 /usr/local/bin/nemoclaw-start /usr/local/bin/nemoclaw-codex-acp         /usr/local/l...
  Step 32/74 : ARG NEMOCLAW_MODEL=gpt-oss:20b
  Step 33/74 : ARG NEMOCLAW_PROVIDER_KEY=inference
  Step 34/74 : ARG NEMOCLAW_PRIMARY_MODEL_REF=inference/gpt-oss:20b
  Step 35/74 : ARG CHAT_UI_URL=http://127.0.0.1:18789
  Step 36/74 : ARG NEMOCLAW_INFERENCE_BASE_URL=https://inference.local/v1
  Step 37/74 : ARG NEMOCLAW_INFERENCE_API=openai-completions
  Step 38/74 : ARG NEMOCLAW_CONTEXT_WINDOW=131072
  Step 39/74 : ARG NEMOCLAW_MAX_TOKENS=4096
  Step 40/74 : ARG NEMOCLAW_REASONING=false
  Step 41/74 : ARG NEMOCLAW_INFERENCE_INPUTS=text
  Step 42/74 : ARG NEMOCLAW_AGENT_TIMEOUT=600
  Step 43/74 : ARG NEMOCLAW_AGENT_HEARTBEAT_EVERY=
  Step 44/74 : ARG NEMOCLAW_INFERENCE_COMPAT_B64=e30=
  Step 45/74 : ARG NEMOCLAW_MESSAGING_CHANNELS_B64=W10=
  Step 46/74 : ARG NEMOCLAW_MESSAGING_ALLOWED_IDS_B64=e30=
  Step 47/74 : ARG NEMOCLAW_DISCORD_GUILDS_B64=e30=
  Step 48/74 : ARG NEMOCLAW_TELEGRAM_CONFIG_B64=e30=
  Step 49/74 : ARG NEMOCLAW_WECHAT_CONFIG_B64=e30=
  Step 50/74 : ARG NEMOCLAW_DISABLE_DEVICE_AUTH=1
  Step 51/74 : ARG NEMOCLAW_BUILD_ID=1779442117994
  Step 52/74 : ARG NEMOCLAW_DARWIN_VM_COMPAT=0
  Step 53/74 : ARG NEMOCLAW_PROXY_HOST=10.200.0.1
  Step 54/74 : ARG NEMOCLAW_PROXY_PORT=3128
  Step 55/74 : ARG NEMOCLAW_WEB_SEARCH_ENABLED=0
  Step 56/74 : ENV NEMOCLAW_MODEL=${NEMOCLAW_MODEL}     NEMOCLAW_PROVIDER_KEY=${NEMOCLAW_PROVIDER_KEY}     NEMOCL...
  Step 57/74 : WORKDIR /sandbox
  Step 58/74 : USER sandbox
  Step 59/74 : RUN python3 /usr/local/lib/nemoclaw/generate-openclaw-config.py
  Step 60/74 : RUN openclaw doctor --fix --non-interactive
  Step 61/74 : ENV NPM_CONFIG_OFFLINE=true     NPM_CONFIG_AUDIT=false     NPM_CONFIG_FUND=false
  Step 62/74 : RUN openclaw plugins install /opt/nemoclaw     && openclaw plugins enable nemoclaw     && openclaw...
  Still building sandbox image... (60s elapsed)
  Step 63/74 : RUN python3 -c "import json, os; path = os.path.expanduser('~/.openclaw/openclaw.json'); cfg = jso...
  Step 64/74 : USER root
  Step 65/74 : RUN set -eu;     config_dir=/sandbox/.openclaw;     data_dir=/sandbox/.openclaw-data;     mkdir -p...
  Still building sandbox image... (80s elapsed)
  Step 66/74 : RUN if id gateway >/dev/null 2>&1 && id sandbox >/dev/null 2>&1; then         if ! id -nG gateway ...
  Step 67/74 : RUN chown -R sandbox:sandbox /sandbox/.openclaw     && chmod -R g+rwX,o-rwx /sandbox/.openclaw    ...
  Still building sandbox image... (100s elapsed)
  Still building sandbox image... (105s elapsed)
  Still building sandbox image... (120s elapsed)
  Still building sandbox image... (135s elapsed)
  Step 68/74 : RUN if ! grep -q "/tmp/nemoclaw-proxy-env.sh" /etc/profile.d/nemoclaw-proxy.sh 2>/dev/null; then  ...
  Step 69/74 : RUN sha256sum /sandbox/.openclaw/openclaw.json > /sandbox/.openclaw/.config-hash     && chmod 660 ...
  Step 70/74 : RUN chown root:root /sandbox/.nemoclaw     && chmod 1755 /sandbox/.nemoclaw     && chown -R root:r...
  Step 71/74 : RUN if [ "$NEMOCLAW_DARWIN_VM_COMPAT" = "1" ]; then         chmod -R a+rwX /sandbox/.openclaw;    ...
  Step 72/74 : HEALTHCHECK --interval=30s --timeout=5s --start-period=45s --retries=3     CMD port="${NEMOCLAW_DA...
  Step 73/74 : ENTRYPOINT ["/usr/local/bin/nemoclaw-start"]
  Step 74/74 : CMD ["/bin/bash"]
  Creating sandbox in gateway...
  Built image openshell/sandbox-from:1779442118
  Waiting for sandbox to become ready...
  Sandbox reported Ready before create stream exited; continuing.
  Waiting for sandbox to become ready...
  Waiting for NemoClaw dashboard to become ready...
  Dashboard taking longer than expected to start. Continuing...
! No active forward found for port 18789
✓ Deleted sandbox my-assistant

  Could not allocate a dashboard port for 'my-assistant'.
  Failed to start dashboard forward on port 18789: spawnSync /home/masaki/.local/bin/openshell ETIMEDOUT
  The orphaned sandbox has been removed — you can safely retry.
```

After that, the sandbox no longer exists.

```
$ openshell --gateway nemoclaw sandbox list
No sandboxes found.
$ openshell --gateway nemoclaw sandbox exec -n my-assistant -- bash -lc \
  'ps aux | grep -E "openclaw|nemoclaw|node|18789|18790" | grep -v grep || true'
Error:   × status: NotFound, message: "sandbox not found", details: [], metadata: MetadataMap { headers: {"content-type":
  │ "application/grpc", "date": "Fri, 22 May 2026 09:34:12 GMT", "x-request-id": "f17068ab-2423-48f5-9d91-
  │ 23b062d85758"} }
$ openshell --gateway nemoclaw sandbox exec -n my-assistant -- bash -lc \
  'ss -ltnp | grep -E "18789|18790|node|openclaw" || true'
Error:   × status: NotFound, message: "sandbox not found", details: [], metadata: MetadataMap { headers: {"content-type":
  │ "application/grpc", "date": "Fri, 22 May 2026 09:34:23 GMT", "x-request-id": "10f4c2a4-a58b-4879-8dcc-
  │ 26e1aac993f7"} }
$ openshell --gateway nemoclaw sandbox exec -n my-assistant -- bash -lc \
  'curl -v --max-time 5 http://127.0.0.1:18789/health || true'
Error:   × status: NotFound, message: "sandbox not found", details: [], metadata: MetadataMap { headers: {"content-type":
  │ "application/grpc", "date": "Fri, 22 May 2026 09:34:30 GMT", "x-request-id": "bc0585de-1768-48f7-b7fa-
  │ e9bcd5444eb8"} }
```

## Dashboard Health Observation during Onboarding

While the installer was waiting for the NemoClaw dashboard, I monitored the sandbox from another terminal (`2nd terminal`).
This suggests that the dashboard service inside the sandbox is healthy on port 18789, but the host-side dashboard forward is not created or detected by `nemoclaw onboard`.

On `2nd termina`,

```
$ watch -n 1 '
date
echo "=== sandbox list ==="
openshell --gateway nemoclaw sandbox list 2>&1 || true

echo
echo "=== ports in my-assistant ==="
openshell --gateway nemoclaw sandbox exec -n my-assistant -- bash -lc '"'"'ss -ltnp | grep -E "18789|18790|node|openclaw" || true'"'"' 2>&1 || true

echo
echo "=== health 18789 ==="
openshell --gateway nemoclaw sandbox exec -n my-assistant -- bash -lc '"'"'curl -sS -i --max-time 3 http://127.0.0.1:18789/health || true'"'"' 2>&1 || true

echo
echo "=== health 18790 ==="
openshell --gateway nemoclaw sandbox exec -n my-assistant -- bash -lc '"'"'curl -sS -i --max-time 3 http://127.0.0.1:18790/health || true'"'"' 2>&1 || true
'
```

At the time when onboarding printed: ` Dashboard taking longer than expected to start. Continuing...`,
the monitor showed:

```
2026年  5月 22日 金曜日 18:32:07 JST
=== sandbox list ===
^[1mNAME        ^[0m  ^[1mCREATED            ^[0m  ^[1mPHASE^[0m
my-assistant  2026-05-22 09:30:55  ^[32mReady^[39m

=== ports in my-assistant ===
Cannot open netlink socket: Operation not permitted
LISTEN 0      0            0.0.0.0:18789      0.0.0.0:*

=== health 18789 ===
HTTP/1.1 200 OKe
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer
Permissions-Policy: camera=(), microphone=(self), geolocation=()
Content-Type: application/json; charset=utf-8
Cache-Control: no-storeo
Date: Fri, 22 May 2026 09:32:08 GMT
Connection: keep-alive
Keep-Alive: timeout=5
Content-Length: 27

{"ok":true,"status":"live"}
=== health 18790 ===
curl: (7) Failed to connect to 127.0.0.1 port 18790 after 0 ms: Could not connect to server
```

## OpenShell Forwarding Test

I also tested OpenShell sandbox creation and forwarding independently.
OpenShell sandbox creation, sandbox exec, and OpenShell gRPC forwarding appear to work in isolation.

This suggests that OpenShell forwarding works in isolation, while `nemoclaw onboard` fails to create or detect its own dashboard forward.

On the `1st terminal`,

```
$ openshell sandbox create --name forward-test --from base -- \
  bash -lc 'python3 -m http.server 18790 --bind 127.0.0.1'
Created sandbox: forward-test                                                                                           
Serving HTTP on 127.0.0.1 port 18790 (http://127.0.0.1:18790/) ...
```

And on the `2nd terminal`,

```
$ openshell sandbox exec -n forward-test -- \
  bash -lc 'curl -v --max-time 5 http://127.0.0.1:18790/ || true'
* Uses proxy env variable no_proxy == '127.0.0.1,localhost,::1'
*   Trying 127.0.0.1:18790...
* Connected to 127.0.0.1 (127.0.0.1) port 18790
> GET / HTTP/1.1
> Host: 127.0.0.1:18790
> User-Agent: curl/8.5.0
> Accept: */*
>
* HTTP 1.0, assume close after body
< HTTP/1.0 200 OK
< Server: SimpleHTTP/0.6 Python/3.13.12
< Date: Fri, 22 May 2026 09:38:56 GMT
< Content-type: text/html; charset=utf-8
< Content-Length: 419
<
<!DOCTYPE HTML>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Directory listing for /</title>
</head>
<body>
<h1>Directory listing for /</h1>
<hr>
<ul>
<li><a href=".agents/">.agents/</a></li>
<li><a href=".bashrc">.bashrc</a></li>
<li><a href=".claude/">.claude/</a></li>
<li><a href=".profile">.profile</a></li>
<li><a href=".uv/">.uv/</a></li>
<li><a href=".venv/">.venv/</a></li>
</ul>
<hr>
</body>
</html>
* Closing connection
```

Then, on the `2nd terminal`,

```
$ openshell forward service forward-test --target-port 18790 --local 18790
✓ Forwarding 127.0.0.1:18790 -> 127.0.0.1:18790 in sandbox forward-test via gRPC
```

And from another terminal (`3rd terminal`),

```
$ curl -v --max-time 5 http://127.0.0.1:18790/ || true
*   Trying 127.0.0.1:18790...
* Connected to 127.0.0.1 (127.0.0.1) port 18790 (#0)
> GET / HTTP/1.1
> Host: 127.0.0.1:18790
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
* HTTP 1.0, assume close after body
< HTTP/1.0 200 OK
< Server: SimpleHTTP/0.6 Python/3.13.12
< Date: Fri, 22 May 2026 09:39:30 GMT
< Content-type: text/html; charset=utf-8
< Content-Length: 419
<
<!DOCTYPE HTML>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Directory listing for /</title>
</head>
<body>
<h1>Directory listing for /</h1>
<hr>
<ul>
<li><a href=".agents/">.agents/</a></li>
<li><a href=".bashrc">.bashrc</a></li>
<li><a href=".claude/">.claude/</a></li>
<li><a href=".profile">.profile</a></li>
<li><a href=".uv/">.uv/</a></li>
<li><a href=".venv/">.venv/</a></li>
</ul>
<hr>
</body>
</html>
* Closing connection 0
```


### Environment

- CPU: Intel Core-i9 12900KS
- memory: 96 GB
- storage: SATA SSD 500 GB (160 GB free)
- GPU: NVIDIA Geforce RTX 4090 * 1
- OS: Ubuntu 22.04 LTS
- NVIDIA driver: v565.77
- Python: v3.10.12
- Ollama: v0.20.4
- LLM: GPT-OSS:20B
- docker engine: v27.3.1
  > usable without sudo
- NVIDIA Container Toolkit: v1.18.1
- Node.js: v22.22.3
- npm: v10.9.8

### Debug Output

```shell

```

### Logs

```shell

```

### Checklist

- [x] I confirmed this bug is reproducible
- [x] I searched existing issues and this is not a duplicate

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`nemoclaw onboard` rolls back after dashboard forward detection fails, although OpenShell forwarding works independently #4064

Description

Reproduction Steps

Installing NeMoClaw with shell script

Dashboard Health Observation during Onboarding

OpenShell Forwarding Test

Environment

Debug Output

Logs

Checklist

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

nemoclaw onboard rolls back after dashboard forward detection fails, although OpenShell forwarding works independently #4064

Description

Description

Reproduction Steps

Installing NeMoClaw with shell script

Dashboard Health Observation during Onboarding

OpenShell Forwarding Test

Environment

Debug Output

Logs

Checklist

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions

`nemoclaw onboard` rolls back after dashboard forward detection fails, although OpenShell forwarding works independently #4064