help with onboard linux | Friends of the Crustacean 🦞🤝 | Page 1

radiant spindle Apr 16, 2026, 1:15 AM

#

So i was installing openclaw on linux and there is an error ```TypeError: Cannot read properties of undefined (reading 'trim')

how to fix it?

mystic salmonBOT Apr 16, 2026, 1:16 AM

#

That one is annoying. If this is happening during openclaw onboard, it matches a known recent setup bug around provider selection.

First, can you paste:

openclaw --version

If you're not on the newest build, try:

openclaw update
openclaw doctor
openclaw onboard --install-daemon

If you need the fix before the next stable release, try the current main build:

#

openclaw update --tag main

Docs:

If it still throws, paste the full stack trace and the exact command that triggered it. There are a couple different trim crashes, and the stack trace will tell which one you hit.

radiant spindle Apr 16, 2026, 1:23 AM

#


│
◇  ✗ Updating via package manager (292.32s)
    npm error code 128
    npm error An unknown git error occurred
    npm error command git --no-replace-objects ls-remote ssh://git@github.com/whiskeysockets/libsignal-node.git
    npm error git@github.com: Permission denied (publickey).
    npm error fatal: Could not read from remote repository.
    npm error
    npm error Please make sure you have the correct access rights
    npm error and the repository exists.
    npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-16T01_17_26_876Z-debug-0.log
│
◇  ✓ Running doctor checks (17.54s)

Update Result: ERROR
  Root: /usr/lib/node_modules/openclaw
  Reason: global update
  Before: 2026.4.14
  After: 2026.4.14

Total time: 310.58s

mystic salmonBOT Apr 16, 2026, 1:25 AM

#

Nice, this log helps a lot.

You’ve got 2 separate issues here:

The trim crash looks like a known onboard/setup bug that’s fixed on main, not in 2026.4.14 stable yet.
Your update failed because Git is trying to fetch a public dependency over SSH (git@github.com) instead of HTTPS.

So plain openclaw update won’t help yet anyway, and the SSH rewrite is blocking the main build too.

Try this one-off:

GIT_CONFIG_GLOBAL=/dev/null GIT_CONFIG_NOSYSTEM=1 openclaw update --tag main
openclaw doctor
openclaw onboard --install-daemon

#

If that works, then your Git config is rewriting GitHub URLs to SSH. You can confirm with:

git config --global --get-regexp '^url\\..*github\\.com.*insteadof$' || true
git config --system --get-regexp '^url\\..*github\\.com.*insteadof$' || true

If those show rewrites to git@github.com: or ssh://git@github.com/, that’s the culprit.

Docs: https://docs.openclaw.ai/install/updating

If the command above still fails, paste the output of those 2 git config commands and I’ll help you clean it up.

radiant spindle Apr 16, 2026, 1:36 AM

#

``` still appears an error

mystic salmonBOT Apr 16, 2026, 1:37 AM

#

Okay, at this point I need the full trace, not just the top line, because that exact trim error can come from a few different paths.

Please paste these outputs:

openclaw --version
openclaw --verbose onboard --install-daemon

And also this, since your earlier update failure looked like a Git URL rewrite issue:

git config --global --get-regexp '^url\\..*github\\.com.*insteadof$' || true
git config --system --get-regexp '^url\\..*github\\.com.*insteadof$' || true

If openclaw --version still says 2026.4.14, then you’re probably still on the old stable build, and we’re likely hitting the known setup bug I mentioned earlier. If you did get onto main, the verbose stack trace will tell us exactly where it’s still blowing up.

#

Docs: https://docs.openclaw.ai/start/wizard

radiant spindle Apr 16, 2026, 1:41 AM

#

its says version is 2026.4.14

mystic salmonBOT Apr 16, 2026, 1:41 AM

#

Yep, that confirms it.

2026.4.14 is still the old stable build, so you’re very likely still hitting the known onboarding bug. The fix is on main, not in that release yet.

Try this exact command:

GIT_CONFIG_GLOBAL=/dev/null GIT_CONFIG_NOSYSTEM=1 openclaw update --tag main

Then check:

openclaw --version

If that shows a newer main build, retry:

#

openclaw onboard --install-daemon

If the update still fails, paste these too:

git config --global --get-regexp '^url\\..*github\\.com.*insteadof$' || true
git config --system --get-regexp '^url\\..*github\\.com.*insteadof$' || true

Your earlier log showed Git trying to fetch GitHub over SSH, which is probably why the update didn’t land.

Docs: https://docs.openclaw.ai/install/updating

radiant spindle Apr 16, 2026, 1:45 AM

#

GIT_CONFIG_GLOBAL=/dev/null GIT_CONFIG_NOSYSTEM=1 openclaw update --tag main


│
◇  ✗ Updating via package manager (136.21s)
    npm error code 128
    npm error An unknown git error occurred
    npm error command git --no-replace-objects ls-remote ssh://git@github.com/openclaw/openclaw.git
    npm error git@github.com: Permission denied (publickey).
    npm error fatal: Could not read from remote repository.
    npm error
    npm error Please make sure you have the correct access rights
    npm error and the repository exists.
    npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-16T01_42_12_806Z-debug-0.log
│
◇  ✓ Running doctor checks (15.94s)

Update Result: ERROR
  Root: /usr/lib/node_modules/openclaw
  Reason: global update
  Before: 2026.4.14
  After: 2026.4.14

Total time: 152.75s

mystic salmonBOT Apr 16, 2026, 1:47 AM

#

Ah, got it, this explains the whole thing.

openclaw update --tag main is going through npm + a GitHub repo spec, and npm is trying to fetch openclaw/openclaw over SSH. So let’s skip npm entirely.

The clean workaround is a git install, which clones over HTTPS:

export GIT_CONFIG_GLOBAL=/dev/null
export GIT_CONFIG_NOSYSTEM=1
curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install-cli.sh | bash -s -- --install-method git --onboard

If you want it step-by-step instead:

export GIT_CONFIG_GLOBAL=/dev/null

#

export GIT_CONFIG_NOSYSTEM=1
curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install-cli.sh | bash -s -- --install-method git
openclaw --version
openclaw onboard --install-daemon

That should get you onto the current main checkout, which has the trim fix.

Docs: https://docs.openclaw.ai/install/installer

If openclaw still shows 2026.4.14 after that, run:

which openclaw
openclaw --version

#

and paste both.

radiant spindle Apr 16, 2026, 1:51 AM

#

OpenClaw 2026.4.14 (323493f)

mystic salmonBOT Apr 16, 2026, 1:52 AM

#

Yep, now the blocker is network reachability, not Git config.

This line:

fatal: unable to access 'https://github.com/openclaw/openclaw.git/': Failed to connect to github.com port 443

means that machine simply can’t reach GitHub over HTTPS, so it can’t pull the main fix. And since you’re still on 2026.4.14, the trim bug is still there.

So the practical options are:

Temporarily allow outbound HTTPS to github.com:443 and rerun the git install.
Wait for the next stable release that includes the fix.
Bypass onboarding and do a manual config on 2026.4.14.

If you want option 3, tell me which model provider you’re trying to use:

#help with onboard linux