#Arch

1 messages · Page 1 of 1 (latest)

soft elbow
#

Is OpenClaw only able to be installed on certain Linux distributions? I tried following install instructions on github and it instantly failed on Arch Linux. (maybe need a certain version? or a different distro? idk)

wanton falconBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

trail epochBOT
#

Nope — OpenClaw isn’t limited to Ubuntu/Debian. The Gateway is supported on Linux, and current installer code handles Arch-style pacman installs too.

Arch-specific gotchas are usually:

  • Node version: use Node 24 recommended or Node 22.14+. If Arch gives you a too-new/odd Node, try fnm/nvm and pin Node 24.
  • Missing build tools: make sure you have base-devel, python, make, cmake, gcc.
  • If install failed instantly, the exact first error matters a lot.

Can you paste:

cat /etc/os-release
node -v
npm -v
command -v openclaw && openclaw --version
soft elbow
#

first line = EndeavorOS
v19.1.0
bash: npm: command not found
[blank, no response to last command]

trail epochBOT
#

That explains it: Node v19.1.0 is too old, and npm isn’t installed. OpenClaw needs Node 24 recommended or Node 22.14+ minimum.

On EndeavourOS/Arch, fix Node first, then rerun OpenClaw install:

sudo pacman -Syu nodejs npm
node -v
npm -v

If pacman gives you something other than Node 24/22.14+, use a Node version manager instead, e.g. fnm/nvm, and install Node 24.

Then retry:

curl -fsSL https://openclaw.ai/install.sh | bash
soft elbow
#

just got a bunch of errors, seems mirrors are 404, and ended with target not found nodejs

trail epochBOT
#

Yep, that’s an Arch/EndeavourOS mirror/package-db issue, not OpenClaw yet.

nodejs and npm are real official Arch packages, so “target not found nodejs” usually means your pacman sync DB/mirrors are stale/broken or [extra] is disabled. ArchWiki calls out Target not found / Failed retrieving file as often being out-of-date package lists or mirror inconsistency. (wiki.archlinux.org)

Try this flow:

# 1. First fix/update EndeavourOS mirrors using the EndeavourOS mirror tool / Welcome app
#    (or reflector/eos-rankmirrors if you normally use those)

# 2. Then force-refresh package databases after the mirror change:
sudo pacman -Syyu

# 3. Then install Node + npm:
sudo pacman -S nodejs npm
Pacman
# 
node -v
npm -v

OpenClaw needs Node 24 recommended, or Node 22.14+ minimum, and Linux is supported. (docs.openclaw.ai)

If it still says target not found, check whether [extra] is enabled:

grep -nE '^\[(core|extra|multilib)\]' /etc/pacman.conf

Paste the pacman error if it continues — the key part will be whether it’s still mirror 404s, missing [extra], or a broken local package DB.

OpenClaw
Node.js - OpenClaw
soft elbow
#

82:[core]
85:[extra]
100:[multilib]

trail epochBOT
#

Good, [extra] is enabled — so this is almost certainly mirrors / pacman database, not OpenClaw.

nodejs lives in Arch’s official repos, so if pacman says target not found: nodejs, your package databases didn’t refresh correctly.

Try checking local search first:

pacman -Ss '^nodejs$'
pacman -Ss '^npm$'

If those show nothing, fix mirrors from EndeavourOS first — easiest path is the EndeavourOS Welcome app → Update Mirrors, then rerun:

sudo pacman -Syyu
sudo pacman -S nodejs npm
#

After that, confirm:

node -v
npm -v

You want Node 22.14+ minimum, ideally 24.x. Once that’s good, rerun the OpenClaw installer.

soft elbow
#

-Syyu failed, 404, even after updating mirrors.. GPME error: no data.. unable to install nodejs update or npm?

trail epochBOT
#

That’s pacman itself breaking now, not OpenClaw.

GPGME error: No data after 404s often means pacman got bad repo DB/signature data from a mirror — sometimes an HTML 404/redirect page gets saved where a .sig file should be. Arch folks have seen exactly that pattern. (lists.archlinux.org)

Try this pacman repair path:

# make sure your mirrorlist is using HTTPS mirrors near the top
grep -n '^Server' /etc/pacman.d/mirrorlist | head -10

If those are http://, rerun EndeavourOS mirror update and prefer HTTPS mirrors.

Then clear only pacman’s repo sync cache — this does not remove installed packages:

# 
sudo rm -f /var/lib/pacman/sync/*.db /var/lib/pacman/sync/*.db.sig
sudo pacman -Syyu

If that succeeds:

sudo pacman -S nodejs npm
node -v
npm -v

Don’t do a partial pacman -Sy nodejs; Arch explicitly expects full system upgrades (-Syu) to avoid stale package/version 404s. (lists.archlinux.org)

Once node -v is 22.14+ — ideally 24.x — OpenClaw install should be back on track. (docs.openclaw.ai)

OpenClaw
Node.js - OpenClaw
soft elbow
#

same errors appear

trail epochBOT
#

At that point I’d stop trying to install OpenClaw through pacman until pacman is healthy — this is still below OpenClaw.

Fast workaround: install Node via a version manager instead of Arch packages:

curl -fsSL https://fnm.vercel.app/install | bash
exec $SHELL -l

fnm install 24
fnm default 24
fnm use 24

node -v
npm -v

Then install OpenClaw without relying on pacman:

# 
npm install -g openclaw@latest
openclaw onboard --install-daemon

You should see Node v24.x and npm working first.

Separately, your EndeavourOS pacman/mirror setup still needs fixing — but fnm should unblock the OpenClaw install. If you want help with the pacman side, paste the first 15–30 lines of the actual sudo pacman -Syyu error, especially the first 404 URL and the GPGME line. “same errors” isn’t quite enough to tell which repo/mirror is poisoning it.

soft elbow
#

it worked, and is installed, on onboarding right now, what do I use for the discord bot token?

trail epochBOT
#

Nice, glad install worked 🎉

For the Discord bot token, use a token from your own Discord bot, not your Discord account token and not anything from this OpenClaw server.

Quick path:

  1. Go to Discord Developer Portal: https://discord.com/developers/applications
  2. New Application
  3. Left sidebar → Bot
  4. Enable Message Content Intent under Privileged Gateway Intents
  5. Click Reset Token / copy token
  6. Paste that into OpenClaw onboarding

Recommended: add that bot to your own private Discord server, not this support server.

Full Discord setup docs: https://docs.openclaw.ai/channels/discord

#

And don’t paste the token here — treat it like a password.

soft elbow
#

well, this has been a nightmare, and setting up the onboarding was more of a nightmare.. I cannot get it to work, so many errors, so fast.. can't see them, fix them, deal with them.. what an absolute mess, how are you supposed to actually use this/get this to work? I don't even know where to begin, there were so many errors

trail epochBOT
#

Ugh, yeah — that sounds miserable. Let’s slow it way down and stop chasing fast-scrolling errors.

Don’t try to debug Discord first. The sane path is:

  1. Get Node/npm valid.
  2. Get OpenClaw installed.
  3. Get the Gateway + dashboard working.
  4. Send one message in the dashboard.
  5. Only then add Discord/Telegram/etc.

Please run these and paste the output here — they’re designed to give us a stable snapshot instead of a blur of errors:

openclaw --version
node -v
npm -v
# 
openclaw status --all
openclaw gateway status

If onboarding is exploding too fast, capture only the output like this:

openclaw onboard --install-daemon 2>&1 | tee ~/openclaw-onboard.log

Then paste the first real error block, not the whole file. Also don’t paste Discord bot tokens/API keys if any appear.

My recommendation: if onboarding asks about Discord and it’s optional, skip it for now and just get the local dashboard working first:

soft elbow
#

I do not have discord on the computer I'm installing this on, so I cannot cut n paste back or forth, I've been doing this all manually. I think I'm done with this, it's too much for the payout which who knows if it's even worth it..

trail epochBOT
#

Totally fair. I wouldn’t blame you for calling it here — manually retyping fast-scrolling terminal errors into Discord is awful, and your Arch/EndeavourOS package setup was already fighting you before OpenClaw even got involved.

If you ever want to try again, I’d suggest not starting with Discord at all:

  1. Install Node/npm.
  2. Run onboarding.
  3. Skip Discord if it asks.
  4. Use the local dashboard first:
openclaw dashboard

That should open a browser UI on the same computer, so you can test OpenClaw without bot tokens, server IDs, Discord copy/paste, etc.

Also honestly: for the lowest-friction first install, a clean Ubuntu/Debian machine or VPS is usually less cursed than a currently-broken Arch mirror/pacman setup. Arch can work, but your environment made this way harder than it should’ve been.