Fix OpenClaw Node Version Too Old

Quick diagnosis

Run these from the same user account that starts OpenClaw:

node -v
which node
openclaw doctor

If OpenClaw runs through a service, also inspect what the service actually starts:

systemctl cat openclaw

Likely causes

• Your interactive shell uses one Node version, but the service uses another.
• A version manager works in SSH but is not loaded inside systemd.
• The VPS still has an older distro-packaged Node binary earlier in PATH.
• OpenClaw was installed before the expected runtime was configured.

Good output vs bad output

Good output shows the expected Node runtime and the same binary path for the user or service that starts OpenClaw.

Bad output shows an old Node version, different paths between SSH and systemd, or openclaw doctor failing before Gateway starts.

Fix steps

1. Confirm the runtime expected by the current OpenClaw install guide.
2. Install the expected Node version using one consistent method.
3. Restart your shell and confirm node -v again.
4. If using systemd, update the service so it uses the same Node binary path.
5. Restart OpenClaw and run the doctor command before changing firewall or Gateway access.

Safety warning

Do not open Gateway or port 18789 publicly to “test faster” while fixing a runtime issue. Node errors are local runtime problems, not a reason to weaken access controls.

When to ask for help

Ask for help if node -v looks correct in SSH but OpenClaw still fails from systemd, PM2, or another process manager. Share only redacted logs and command output.

Sources

• https://docs.openclaw.ai/
• https://docs.openclaw.ai/gateway/troubleshooting