Common OpenClaw installation errors and how to fix them

OpenClaw installation troubleshooting guide

A recent post on r/openclaw addresses recurring installation and runtime errors for the OpenClaw tool, providing specific commands and fixes.

Key issues and fixes

"installed but openclaw is not discoverable"

This occurs when npm's global bin directory is not in your PATH. The binary exists but cannot be found.

• Run npm prefix -g to find your global prefix.
• Add <prefix>/bin to your $PATH in .bashrc or .zshrc.
• Reload your shell, then openclaw --version should work.

"EACCES: permission denied" on install

This is a permissions issue with npm's default global directory, often owned by root.

• Do not use sudo.
• Configure a user-owned prefix instead:

  mkdir -p ~/.npm-global
  npm config set prefix '~/.npm-global'
  export PATH="$HOME/.npm-global/bin:$PATH"

• Add the export to your shell config and re-run the install without sudo.

Old Node.js silent failures

OpenClaw requires Node.js 22+. Older versions may install without error but produce a binary that breaks at runtime.

• Always check node --version first.

"inappropriate ioctl for device"

This is a TTY issue, common in Docker containers or CI environments without a real terminal.

• Run openclaw onboard --non-interactive --accept-risk to skip the interactive wizard.

Telegram plugin stuck as "not available"

If a previous broken install left the Telegram plugin in a partially configured state, it can get stuck.

• Run openclaw doctor --fix to clear the state.

Note on "gateway connect pairing required"

This message is not an installation error. It relates to DM policy, where OpenClaw requires manual pairing before responding to DMs by default. Refer to the OpenClaw documentation on channel configuration.