NVIDIA / NVIDIA/NemoClaw

[macOS][Onboard] Ollama onboard completes while the newly installed backend is not running

Open
#11,984 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
22.5k
Forks
3.1k
Avg merge
1d 1h
Merged PRs (30d)
715

Description

## Description

NemoClaw v0.0.125 completes non-interactive onboarding with the macOS Ollama provider after installing Ollama, creates the sandbox, and starts the Ollama authentication proxy. However, the Ollama backend itself is not listening after onboarding.

Platform scope: Reproduced on macOS arm64 only; other platforms were not tested for this symptom.

Regression: Unknown.

## Environment

- Device: macOS arm64 test host
- OS: macOS 26.5 (Darwin 25.5.0)
- Architecture: arm64
- Node.js: v22.23.2
- npm: 10.9.8
- Docker: Docker Engine 29.5.2
- OpenShell CLI: 0.0.116
- NemoClaw: v0.0.125
- OpenClaw: 2026.7.1
- Ollama: 0.34.1

## Steps to reproduce

1. Start from a macOS arm64 host without an active Ollama backend.
2. Install NemoClaw v0.0.125.
3. Run non-interactive onboarding with the OpenClaw agent and select the macOS Ollama install path.
4. Wait for onboarding and sandbox creation to complete.
5. Check listeners for ports 11434 and 11435.
6. Run `ollama --version` and query `http://127.0.0.1:11434/api/tags` without a proxy.

## Expected result

Successful onboarding with the Ollama provider should leave both the Ollama backend on loopback port 11434 and its authentication proxy on port 11435 available, because the created sandbox depends on that inference path.

## Actual result

Onboarding reports that Ollama is used on localhost:11434 and the proxy on 11435, and sandbox creation succeeds. After onboarding, port 11435 is listening but port 11434 has no listener. The Ollama client reports that it cannot connect to a running Ollama server. Cleanup also reports that the saved local route cannot reach the backend.

## Logs

```text
Ollama 0.34.1 installed
Using Ollama on localhost:11434 (proxy on :11435)

ollama --version:
Warning: could not connect to a running Ollama instance
Warning: client version is 0.34.1

Listener check:
port 11434: no listener
port 11435: node process listening

Cleanup:
No reachable local Ollama endpoint was found at http://127.0.0.1:11434
```

Contributor guide

Open the contributing guide

Research direction

Start by tracing the macOS Ollama install path used during non-interactive onboarding, then inspect how sandbox creation and the authentication proxy are started. Reproduce on macOS arm64 and verify that onboarding leaves both 127.0.0.1:11434 and port 11435 listening, with /api/tags reachable without the proxy.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, ollama, typescript
Domain
api, backend, mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.