fresh clawdbot install is hanging | Friends of the Crustacean 🦞🤝 | Page 1

unreal crane Jan 25, 2026, 7:32 PM

#

the newest clawdbot is working for everyone? Tried a fresh install and it "hangs" while setting
Tried both ways:

clawd@neat jaybot:~$ npm install -g clawdbot@latest
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Use your platform's native DOMException instead
npm warn deprecated [email protected]: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exhorbitant rates) by contacting [email protected]
⠧

clawd@neat jaybot:~$ curl -fsSL https://clawd.bot/install.sh | bash

🦞 Clawdbot Installer
End-to-end encrypted, Zuck-to-Zuck excluded.

✓ Detected: linux
✓ Node.js v22.22.0 found
✓ Git already installed
→ Installing Clawdbot 2026.1.24-3...

#

@mortal bane ?

mortal baneBOT Jan 25, 2026, 7:35 PM

#

Hey Animizio! 👋 Happy to help! 🦐

A few quick questions to get started:

What's your Clawdbot version? Run: clawdbot --version
- Version mismatch is the #1 cause of weird issues!
What specifically is hanging?
- Gateway start? Node connection? WhatsApp login?
- Any error messages in the output?
What have you tried so far?
- clawdbot gateway status?
- Any logs you can share?

In the meantime, a few common fixes:

Make sure Docker is running (if using Docker)

#

Check that ports 3080/ONNXRUNTIME_PORT aren't blocked
Try clawdbot gateway restart

Let me know what you're seeing and we'll get this sorted! 🎉

mortal baneBOT Jan 25, 2026, 7:35 PM

#

unreal crane <@1457407575476801641> ?

Done! I've asked for their version and what specifically is hanging. Version info is critical for troubleshooting - it's amazing how often that resolves things!

Let me know when they respond with more details and I can help dig deeper. 🦐

unreal crane Jan 25, 2026, 7:36 PM

#

I cant test any command because its hanging in the install script

mortal baneBOT Jan 25, 2026, 7:37 PM

#

unreal crane I cant test any command because its hanging in the install script

Ah, got it! The install script itself is hanging - that's different. 🦐

A few quick things:

What to check:

OS? (Linux/Docker, Windows w/WSL, Mac?)
Where exactly is it hanging? (Docker pull? npm install? Somewhere else?)
Can you share the last line/area you see before it freezes?

Quick fixes to try:

Ctrl+C to break out, then run the install with more verbose output
Check if Docker is actually installed and running: docker --version
If using the one-liner script, try the manual install steps instead

Common hang spots:

Docker image pulls (can be slow or blocked by firewall)
npm/pnpm install (network or disk space issues)

#

pnpm install --frozen-lockfile if dependencies changed

What OS are you on? I'll help you get unstuck! 💪

unreal crane Jan 25, 2026, 7:38 PM

#

Debian 13 as VM on Promox

#

I have already showed you the last lines

mortal baneBOT Jan 25, 2026, 7:39 PM

#

unreal crane Debian 13 as VM on Promox

Nice - Debian on Proxmox is a solid choice! 🦐

A few more questions:

How much RAM/disk does the VM have? (Clawdbot needs at least 2GB RAM, preferably more)
Where exactly is it hanging? (Need to see the last output before freeze)
Docker or native install?

Quick things to check on the VM:

# Check resources
free -h
df -h

# Check Docker if using it
docker --version

#

docker ps

# If you used the install script, check what's running
ps aux | grep clawdbot

If it's stuck at Docker image pull, try:

docker pull clawdbot/entrypoint:latest

Let me know what you see - especially the last line before it froze and your VM specs!

#

Ah, I apologize! I'm in a fresh session and don't have the earlier conversation history. 📋

Could you paste those last lines again? Or just share:

What command you ran to start the install
What the last visible output was before it froze

That'll help me pinpoint exactly where it's getting stuck! 🦐

unreal crane Jan 25, 2026, 7:39 PM

#

the newest clawdbot is working for everyone? Tried a fresh install and it "hangs" while setting
Tried both ways:

clawd@neat jaybot:~$ npm install -g clawdbot@latest
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Use your platform's native DOMException instead
npm warn deprecated [email protected]: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exhorbitant rates) by contacting [email protected]
⠧

clawd@neat jaybot:~$ curl -fsSL https://clawd.bot/install.sh | bash

🦞 Clawdbot Installer
End-to-end encrypted, Zuck-to-Zuck excluded.

✓ Detected: linux
✓ Node.js v22.22.0 found
✓ Git already installed
→ Installing Clawdbot 2026.1.24-3...

mortal baneBOT Jan 25, 2026, 7:40 PM

#

unreal crane the newest clawdbot is working for everyone? Tried a fresh install and it "hangs...

Ah, now I can see the issue! Both methods are hanging at the package installation phase:

npm install stuck at ⠧ (extracting packages)
Installer stuck at → Installing Clawdbot 2026.1.24-3...

Quick troubleshooting:

# Check disk space (common culprit!)
df -h

# Check available RAM
free -h

# Try clearing npm cache
npm cache clean --force

#


# Try installing just the CLI to test npm
npm install -g --verbose clawdbot@latest 2>&1 | tee /tmp/npm-debug.log

Most likely causes:

Disk full or inodes exhausted (df -i)
Slow npm registry or network issues
npm cache corruption

Quick fixes to try:

# Clear cache and retry
npm cache clean --force
npm install -g clawdbot@latest

#

Or try with pnpm (often faster/more reliable):

npm install -g pnpm
pnpm add -g clawdbot

Can you run those diagnostic commands and share the output? Especially df -h and free -h! 🦐

unreal crane Jan 25, 2026, 7:50 PM

#

npm http fetch GET 200 https://registry.npmjs.org/balanced-match 222ms (cache miss)
npm verbose stack Error: ENOTEMPTY: directory not empty, rename '/home/clawd/.npm-global/lib/node_modules/clawdbot' -> '/home/clawd/.npm-global/lib/node_modules/.clawdbot-DihjDigb'
npm verbose stack at async Object.rename (node:internal/fs/promises:781:10)
npm verbose stack at async moveFile (/usr/lib/node_modules/npm/node_modules/@npmcli/fs/lib/move-file.js:30:5)
npm verbose stack at async Promise.allSettled (index 0)
npm verbose stack at async [reifyPackages] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:325:11)
npm verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:142:5)
npm verbose stack at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:150:5)
npm verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:207:9)
npm verbose stack at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:74:5)
npm error code ENOTEMPTY
npm error syscall rename
npm error path /home/clawd/.npm-global/lib/node_modules/clawdbot
npm error dest /home/clawd/.npm-global/lib/node_modules/.clawdbot-DihjDigb
npm error errno -39
npm error ENOTEMPTY: directory not empty, rename '/home/clawd/.npm-global/lib/node_modules/clawdbot' -> '/home/clawd/.npm-global/lib/node_modules/.clawdbot-DihjDigb'
npm verbose cwd /home/clawd
npm verbose os Linux 6.12.63+deb13-amd64
npm verbose node v22.22.0
npm verbose npm v10.9.4
npm verbose exit -39
npm verbose code -39
npm error A complete log of this run can be found in: /home/clawd/.npm/_logs/2026-01-25T19_46_02_730Z-debug-0.log

mortal baneBOT Jan 25, 2026, 7:50 PM

#

unreal crane npm http fetch GET 200 https://registry.npmjs.org/balanced-match 222ms (cache mi...

Found it! 🎯 That's the classic ENOTEMPTY npm bug - corrupted install directory.

The fix is simple:

# 1. Remove the corrupted install
rm -rf /home/clawd/.npm-global/lib/node_modules/clawdbot
rm -rf /home/clawd/.npm-global/lib/node_modules/.clawdbot-*

# 2. Clear npm cache
npm cache clean --force

# 3. Retry the install
npm install -g clawdbot@latest

Or if you prefer a nuclear option:

#fresh clawdbot install is hanging