error | Friends of the Crustacean 🦞🤝 | Page 1

fossil briarBOT Apr 14, 2026, 5:30 PM

#

hollow atlasBOT Apr 14, 2026, 5:30 PM

#

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

fossil briarBOT Apr 14, 2026, 5:30 PM

#

main chasmBOT Apr 14, 2026, 5:31 PM

#

Let me pull the actual docs paths first so I don't make up install steps.

#

Yeah, let’s make this boring and predictable.

Use one install path only. Don’t mix npm, git, Docker, Bun, etc. for the first try.

Recommended install

macOS / Linux / WSL2

curl -fsSL https://openclaw.ai/install.sh | bash
openclaw onboard --install-daemon
openclaw gateway status
openclaw dashboard

Windows (PowerShell)

#

iwr -useb https://openclaw.ai/install.ps1 | iex
openclaw onboard --install-daemon
openclaw gateway status
openclaw dashboard

What should happen

Installer runs
Onboarding asks for your model provider/API key
Gateway starts
Dashboard opens
You send a test message

If the normal installer keeps failing

Use the local-prefix installer instead, it avoids a lot of global npm / permission pain:

#

curl -fsSL https://openclaw.ai/install-cli.sh | bash -s -- --onboard

If `openclaw` says “command not found”

Run:

node -v
npm prefix -g
echo "$PATH"

If needed, add this to ~/.bashrc or ~/.zshrc:

export PATH="$(npm prefix -g)/bin:$PATH"

#

Then open a new terminal.

Important notes

Node 24 is recommended, Node 22.14+ also works
On Windows, WSL2 is usually more stable
If you build from source, use pnpm, not Bun

If it still breaks

Paste these 4 things here and I’ll walk through the exact failure:

openclaw --version
node --version
openclaw status --all
openclaw gateway status

#

And also tell me:

your OS
the exact install command you ran
the full error text

Docs:

teal mango Apr 17, 2026, 2:33 PM

#

showing "[*] Installing OpenClaw (openclaw@latest)..." for a long time

main chasmBOT Apr 17, 2026, 2:34 PM

#

I’m checking what that installer step actually does, so I can tell you whether it’s normal or stuck.

#

That line is the npm global install step. It should usually finish in 2 to 5 minutes. If it’s been sitting there for 10+ minutes with no new output, I’d treat it as stuck.

Do this next:

macOS / Linux / WSL2

Stop it with Ctrl+C, then rerun with verbose output:

curl -fsSL https://openclaw.ai/install.sh | bash -s -- --no-onboard --verbose

Windows PowerShell

If you’re on native Windows, tell me, the debug command is different. Also, WSL2 is usually the smoother path for OpenClaw.

Then paste these:

#

node --version
npm --version
openclaw --version

If openclaw says not found, that’s okay, just paste that too.

And most important, paste the last 30 to 50 lines from the verbose installer output after it hangs.

If you want, I can walk you through it live once you send:

your OS
those 3 version outputs
the last chunk of verbose output

Docs:

https://docs.openclaw.ai/help/faq

#

teal mango Apr 17, 2026, 2:35 PM

#

openclaw installed now how to make it work

main chasmBOT Apr 17, 2026, 2:35 PM

#

If anything fails, paste these here:

openclaw --version
openclaw status --all
openclaw gateway status

Docs:

#

Nice, you’re past the hard part 🎉

Now do this:

openclaw onboard --install-daemon

That setup wizard will:

ask you to choose a model provider
ask for your API key
set up the gateway/service

Then verify it’s running:

#

openclaw gateway status

Then open the dashboard:

openclaw dashboard

If that doesn’t open automatically, go to:

http://127.0.0.1:18789/

Then send a test message in the chat UI.

teal mango Apr 17, 2026, 2:40 PM

#

it says:

Model/auth provider
| > Anthropic (Claude CLI + API key)
| Arcee AI
| BytePlus
| Chutes
| Cloudflare AI Gateway
| Copilot Proxy
| Custom Provider
| DeepSeek
| Fireworks
| Gemini CLI OAuth
| GitHub Copilot
| Google
| Hugging Face
| Kilo Gateway
| LiteLLM
| LM Studio
| Microsoft Foundry
| MiniMax
| Mistral AI
| Moonshot AI (Kimi K2.5)
| Ollama
| OpenAI
| OpenAI Codex
| OpenCode
| ...

what now ic ant type anything

main chasmBOT Apr 17, 2026, 2:40 PM

#

I’m checking the wizard controls so I don’t tell you the wrong keys.

#

Yep, that screen is a menu, not a text box.

Do this:

Click into the terminal window
Use ↑ / ↓ arrow keys to move
Press Enter to choose

For Model/auth provider, pick the one you actually have access to:

OpenAI if you have an OpenAI API key
Anthropic if you have an Anthropic key / Claude setup
Google if you want Google auth
etc.

After you pick one, the wizard should move to the next step and start asking for details.

Easiest path

#

If you already have an API key, pick that provider, then:

paste the API key when asked
keep the default gateway settings
finish onboarding
then run:

openclaw dashboard

If the keys don’t work

Try:

Enter
arrow keys
if still nothing, press Ctrl+C and rerun openclaw onboard in a normal terminal app

If you want, tell me which provider you have and I’ll tell you exactly which option to pick next.

teal mango Apr 17, 2026, 4:43 PM

#

how to open openclaw again

main chasmBOT Apr 17, 2026, 4:44 PM

#

To open OpenClaw again:

openclaw dashboard

If the gateway isn’t running yet, start it first:

openclaw gateway start
openclaw dashboard

You can also open it directly in your browser:

#

http://127.0.0.1:18789/

Useful checks:

openclaw gateway status

If you want to go back into setup again:

openclaw onboard

teal mango Apr 17, 2026, 4:48 PM

#

i need to change my ai

main chasmBOT Apr 17, 2026, 4:49 PM

#

Got you. To change your AI, do this:

Change the default AI

Open terminal and run:

openclaw configure --section model

Then:

use arrow keys
pick the new AI/provider
press Enter
save/finish

After that, reopen OpenClaw:

#

openclaw dashboard

If you only want to change it in the current chat

Type this in the chat:

/model

If you want, tell me which AI you want to switch to and I’ll give you the exact next click.

teal mango Apr 17, 2026, 4:51 PM

#

it opens a dashboard but the link is invald. it says "This site can’t be reached"

main chasmBOT Apr 17, 2026, 4:52 PM

#

That usually means one of two things:

the gateway isn’t running, or
you’re opening the link on a different device even though your gateway is bound to 127.0.0.1.

Your setup showed:

Gateway bind: Loopback (127.0.0.1)

That means the dashboard only works on the same computer where OpenClaw is running.

Try this on that same computer

openclaw --version
openclaw gateway status

#

openclaw gateway start
openclaw dashboard

Then manually open:

http://127.0.0.1:18789/

If you are using another device

127.0.0.1 will not work there. It only points to that device itself.

If it still fails

Paste the output of:

#

openclaw --version
openclaw gateway status
openclaw status --all

and tell me:

are you opening it on the same PC or a different phone/laptop
what exact link it tried to open

Docs:

teal mango Apr 17, 2026, 4:53 PM

#

same PC and the link is: http://127.0.0.1:18789/

main chasmBOT Apr 17, 2026, 4:53 PM

#

Perfect, that helps.

If http://127.0.0.1:18789/ says site can’t be reached, that usually means the gateway is not running.

Run these exactly:

openclaw gateway status
openclaw gateway start
openclaw gateway status

Then refresh:

http://127.0.0.1:18789/

#

If it still doesn’t open, run:

openclaw status --all

and paste the output here.

So, next thing I need from you is the result of:

openclaw gateway status

teal mango Apr 22, 2026, 5:07 AM

#

why it takes soo long to respond

main chasmBOT Apr 22, 2026, 5:08 AM

#

I’m checking the docs for the main causes of slow replies so I can give you the shortest useful checklist.

#

Usually it’s one of these:

the model/provider is slow
you’re using a local model like Ollama/LM Studio
the gateway is unhealthy / reconnecting
the agent is using tools, which adds extra time

If you’re on a local model, that’s the big one. Local setups are often much slower unless you have pretty serious hardware.

Check these first

openclaw --version
openclaw status
openclaw models status

If you want the fastest fix

#

switch to a cloud provider instead of a local model
change to a faster provider/model in:

openclaw configure --section model

If it feels broken, not just slow

Run:

openclaw logs --follow

and send:

openclaw status
openclaw models status

If you paste those two outputs, I can usually tell pretty fast what’s slowing it down.

#

Docs:

teal mango Apr 22, 2026, 5:14 AM

#

after the model select

main chasmBOT Apr 22, 2026, 5:15 AM

#

Ah, got it, after you select the model.

That part can be slower because OpenClaw is:

switching to the new provider/model
checking auth
starting the first request with that model

So the first reply after a model change is often slower than normal.

Normal vs not normal

a few seconds to ~30s: can be normal
every reply takes forever: something’s off

Big clue

If you picked a local model like Ollama or LM Studio, slow replies are pretty normal on weaker hardware.

Check this

#

openclaw status
openclaw models status

And tell me which provider you selected.

If you paste those, I can tell you whether it’s normal slow or broken slow.

teal mango Apr 22, 2026, 5:16 AM

#

◇ Default model
│ Keep current (openai/gpt-5.4)
Error: Cannot find module 'axios'
Require stack:

C:\Users\Somegh\AppData\Roaming\npm\node_modules\openclaw\node_modules@larksuiteoapi\node-sdk\lib\index.js
PS C:\Users\Somegh> .\Downloads
.\Downloads\ : The term '.\Downloads' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

.\Downloads\

  + CategoryInfo          : ObjectNotFound: (.\Downloads\:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\Somegh>

main chasmBOT Apr 22, 2026, 5:17 AM

#

I’m checking whether that axios error is a known install packaging issue or just a broken global install, so I can give you the safest fix.

#

I found the package does depend on axios, so this smells like a broken/incomplete global install on Windows, not user error. I’m checking the published package metadata next.

#

That one looks like a broken package/install, not something you did.

openclaw is trying to load @larksuiteoapi/node-sdk, and that package wants axios, but axios is missing.

Try this first in PowerShell

openclaw --version
npm i -g axios@1.15.0
openclaw onboard

If it still breaks

Do a clean reinstall:

npm uninstall -g openclaw

#

npm install -g openclaw@latest
npm i -g axios@1.15.0
openclaw onboard

Small note

This part:

.\Downloads\

isn’t a valid command by itself. If you wanted to go there, use:

#

cd .\Downloads

If you run the 3 commands above, paste the output if it still fails.
Honestly, this smells like a packaging bug on Windows. If it keeps happening after that, please file a GitHub issue here:

https://github.com/openclaw/openclaw/issues

Docs:

teal mango Apr 22, 2026, 5:17 AM

#

How can I make this AI that will help me to setup server and setup discord bot in their dashboard, and Iso need to make it so that this bot can chat through Discord DMs

main chasmBOT Apr 22, 2026, 5:18 AM

#

I’m grabbing the Discord setup docs so I can give you the shortest path without making up config steps.

#

Yep, you can do that.

Short version: create a Discord bot in the Discord Developer Portal, connect it to OpenClaw, then approve DM pairing.

1) Create the Discord bot

In the Discord Developer Portal:

New Application
go to Bot
enable:
- Message Content Intent
- Server Members Intent (recommended)
copy the Bot Token
go to OAuth2
enable:
- bot
- applications.commands

#

give it permissions:
- View Channels
- Send Messages
- Read Message History
- Embed Links
- Attach Files
invite it to your own server

2) Copy your IDs

In Discord, turn on Developer Mode, then copy:

your Server ID
your User ID

3) Connect the bot to OpenClaw

On the PC running OpenClaw, in PowerShell:

#

$env:DISCORD_BOT_TOKEN="YOUR_BOT_TOKEN"
openclaw config set channels.discord.token --ref-provider default --ref-source env --ref-id DISCORD_BOT_TOKEN
openclaw config set channels.discord.enabled true --strict-json
openclaw gateway restart

Do not paste your bot token in Discord chat.

4) Enable DMs

In Discord:

right-click your server
Privacy Settings
turn on Direct Messages

5) Pair Discord DMs

Now DM your bot in Discord.

#

It should send you a pairing code.

Approve it on your PC:

openclaw pairing list discord
openclaw pairing approve discord YOUR_CODE

After that, the bot can chat with you in Discord DMs.

If you also want it to reply inside your server channels, I can give you the next step for the guild allowlist too.

Docs:

https://docs.openclaw.ai/channels/discord

#

https://docs.openclaw.ai/channels/pairing

teal mango Apr 22, 2026, 5:25 AM

#

openclaw : The term 'openclaw' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

openclaw config set channels.discord.token --ref-provider default --r ...

  + CategoryInfo          : ObjectNotFound: (openclaw:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

main chasmBOT Apr 22, 2026, 5:25 AM

#

That means PowerShell can’t find the OpenClaw command on your PATH.

Check where npm installed it

Run these:

node --version
npm --version
npm config get prefix
Get-ChildItem "$(npm config get prefix)\openclaw*"

If you see `openclaw.cmd`

Try running it directly:

#

& "$(npm config get prefix)\openclaw.cmd" --version

If that works, the fix is:

add the folder from npm config get prefix to your User PATH
close PowerShell
open a new PowerShell window
run:

openclaw --version

On Windows, that folder is usually:

#

%AppData%\npm

If you do not see `openclaw.cmd`

Reinstall it:

npm install -g openclaw@latest

Then run:

& "$(npm config get prefix)\openclaw.cmd" --version

#

If you want, paste the output of these two:

npm config get prefix
Get-ChildItem "$(npm config get prefix)\openclaw*"

Docs:

teal mango Apr 22, 2026, 5:28 AM

#

PS C:\Users\Somegh> node --version
v24.13.0
PS C:\Users\Somegh> npm --version
11.10.0
PS C:\Users\Somegh> npm config get prefix
C:\Users\Somegh\AppData\Roaming\npm
PS C:\Users\Somegh> Get-ChildItem "$(npm config get prefix)\openclaw*"
PS C:\Users\Somegh> & "$(npm config get prefix)\openclaw.cmd" --version
& : The term 'C:\Users\Somegh\AppData\Roaming\npm\openclaw.cmd' is not recognized as the name of a cmdlet, function,
script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:3

& "$(npm config get prefix)\openclaw.cmd" --version

+ CategoryInfo          : ObjectNotFound: (C:\Users\Somegh...pm\openclaw.cmd:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

main chasmBOT Apr 22, 2026, 5:28 AM

#

Nice, that tells us a lot.

Your Node/npm setup is fine.
The real issue is simpler: OpenClaw is not actually installed right now.

Get-ChildItem "$(npm config get prefix)\openclaw*" returned nothing, so there is no openclaw.cmd yet.

Install it now

Run:

npm install -g openclaw@latest

Then check:

#

Get-ChildItem "$(npm config get prefix)\openclaw*"
& "$(npm config get prefix)\openclaw.cmd" --version

If that works

Then continue with:

openclaw onboard

If install succeeds but onboarding later hits the `axios` error again

Run:

#

npm install -g axios@1.15.0

and retry:

openclaw onboard

Important

If npm install -g openclaw@latest throws any error, paste the full output here.
That’s the next thing we need.

So right now, just run:

#

npm install -g openclaw@latest

teal mango Apr 22, 2026, 6:50 AM

#

now what

main chasmBOT Apr 22, 2026, 6:51 AM

#

I’m checking the published package metadata for that Feishu dependency too. Also, your OpenAI key was pasted in public here, so I’m going to treat that as compromised.

#

First, important: your OpenAI API key was pasted in public here.
Please delete that message immediately and revoke/rotate the key in OpenAI before using it again. That key is now compromised.

For the actual error:

Cannot find module '@larksuiteoapi/node-sdk'

That’s a missing bundled plugin runtime dependency, not a bad OpenAI key.

Fix

Run:

openclaw doctor --fix
openclaw onboard

#

If openclaw still isn’t on PATH, use:

& "$(npm config get prefix)\openclaw.cmd" doctor --fix
& "$(npm config get prefix)\openclaw.cmd" onboard

Why

OpenClaw’s doctor can repair missing bundled plugin runtime deps, and the docs specifically call out this kind of issue.

If doctor --fix still fails, paste the full output here and I’ll help with the next step.

Docs:

#

Do these in order:

1) Revoke that leaked OpenAI key

In your OpenAI dashboard:

delete / revoke the key you pasted here
create a new key

Don’t paste the new one in Discord.

2) Repair OpenClaw

On your PC:

openclaw doctor --fix

If openclaw doesn’t work from PATH:

#

& "$(npm config get prefix)\openclaw.cmd" doctor --fix

3) Run setup again

openclaw onboard

or:

& "$(npm config get prefix)\openclaw.cmd" onboard

4) When it asks for the OpenAI key

Paste the new key there, locally on your PC.

#

5) After setup finishes

Open it:

openclaw dashboard

If doctor --fix throws another error, paste that output here and I’ll guide the next step.

teal mango Apr 22, 2026, 6:52 AM

#

nvm about that tell me how to make it on discord DMs

main chasmBOT Apr 22, 2026, 6:52 AM

#

Yep, for Discord DMs do this:

You need OpenClaw installed and the gateway running first.

1) Create a Discord bot

In the Discord Developer Portal:

make a New Application
go to Bot
enable:
- Message Content Intent
- Server Members Intent (recommended)
copy the Bot Token

2) Invite the bot to your own server

In OAuth2:

#

enable:
- bot
- applications.commands
give it permissions:
- View Channels
- Send Messages
- Read Message History
- Embed Links
- Attach Files

Then invite it to your private server.

3) Turn on Discord Developer Mode

In Discord settings, enable Developer Mode, then copy:

your Server ID
your User ID

#

4) Connect that bot token to OpenClaw

On the PC running OpenClaw, in PowerShell:

$env:DISCORD_BOT_TOKEN="YOUR_BOT_TOKEN"
openclaw config set channels.discord.token --ref-provider default --ref-source env --ref-id DISCORD_BOT_TOKEN
openclaw config set channels.discord.enabled true --strict-json
openclaw gateway restart

If openclaw is not on PATH, use:

& "$(npm config get prefix)\openclaw.cmd" config set channels.discord.token --ref-provider default --ref-source env --ref-id DISCORD_BOT_TOKEN
& "$(npm config get prefix)\openclaw.cmd" config set channels.discord.enabled true --strict-json
& "$(npm config get prefix)\openclaw.cmd" gateway restart

#

Do not paste your bot token in Discord.

5) Allow DMs

In Discord:

right-click your server
Privacy Settings
enable Direct Messages

6) Pair the DM

Now DM your bot.

It should reply with a pairing code.

Approve it on your PC:

#

openclaw pairing list discord
openclaw pairing approve discord YOUR_CODE

After that, your bot can chat with you in Discord DMs.

If you want, next I can give you the step for making it also reply in your server channels.

Docs:

teal mango Apr 22, 2026, 7:04 AM

#

PS C:\Users\Somegh> openclaw gateway restart

🦞 OpenClaw 2026.4.21 (f788c88) — Making 'I'll automate that later' happen now.

Gateway service missing.
Start with: openclaw gateway install
Start with: openclaw gateway
Start with: schtasks /Run /TN "OpenClaw Gateway"
PS C:\Users\Somegh> openclaw pairing list discord
12:29:29 [plugins] discord installed bundled runtime deps: @buape/carbon@0.16.0, @discordjs/voice@^0.19.2, discord-api-types@^0.38.47, opusscript@^0.0.8

🦞 OpenClaw 2026.4.21 (f788c88) — Deployed locally, trusted globally, debugged eternally.

No pending discord pairing requests.
PS C:\Users\Somegh> openclaw pairing approve discord f788c88

🦞 OpenClaw 2026.4.21 (f788c88) — I speak fluent bash, mild sarcasm, and aggressive tab-completion energy.

[openclaw] Failed to start CLI: Error: No pending pairing request found for code: f788c88
at Command.<anonymous> (file:///C:/Users/Somegh/AppData/Roaming/npm/node_modules/openclaw/dist/pairing-cli-DZGSdXcv.js:108:24)
at async Command.parseAsync (C:\Users\Somegh\AppData\Roaming\npm\node_modules\openclaw\node_modules\commander\lib\command.js:1122:5)
at async runCli (file:///C:/Users/Somegh/AppData/Roaming/npm/node_modules/openclaw/dist/run-main-CTb0YOht.js:473:4)
PS C:\Users\Somegh>

main chasmBOT Apr 22, 2026, 7:05 AM

#

You’re close. Two important things:

f788c88 is not the pairing code
that’s just the OpenClaw build/commit shown in the banner.
There are no pending pairing requests yet
because your gateway is not running right now.

Do this instead

1) Start the gateway

For now, easiest is to run it in the foreground:

openclaw gateway

#

Leave that window open.

2) DM your Discord bot

Go to Discord and send your bot a message.

That should create a real pairing request and the bot should send you a pairing code.

3) In another PowerShell window

Run:

openclaw pairing list discord

Now you should see a pending code.

4) Approve the real code

#

openclaw pairing approve discord YOUR_REAL_CODE

Important

Do not use f788c88. That is not the code.

If you want it to keep running in the background later

You can install the service with:

openclaw gateway install

But for now, just use:

#

openclaw gateway

If you DM the bot and it still doesn’t reply, send me the output of:

openclaw status

teal mango Apr 22, 2026, 7:07 AM

#

The bot is not sending anything

main chasmBOT Apr 22, 2026, 7:07 AM

#

Okay, then we need to check whether the bot is actually connected, not guess.

Run these and paste the output:

openclaw status
openclaw gateway status
openclaw channels status --probe

Also tell me:

does the bot show online in Discord?
are you DMing the bot account itself, not the app page?
in the Discord Developer Portal, is Message Content Intent turned on?

Most likely it’s one of these:

#

gateway not running
Discord token not loaded
bot not connected to Discord
Message Content Intent disabled

Paste those 3 command outputs and I’ll tell you the exact next fix.

teal mango Apr 22, 2026, 7:13 AM

#

PS C:\Users\Somegh> openclaw status

🦞 OpenClaw 2026.4.21 (f788c88) — We ship features faster than Apple ships calculator updates.

│
◇
│
◇
Secret diagnostics:

status: gateway secrets.resolve unavailable (gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: C:\Users\Somegh.openclaw\openclaw.json
Bind: loopback

Possible causes:

Gateway not yet ready to accept connections (retry after a moment)
TLS mismatch (connecting with ws:// to a wss:// gateway, or vice versa)
Gateway crashed or was terminated unexpectedly
Run openclaw doctor for diagnostics.); resolved command secrets locally.

OpenClaw status

Overview
┌──────────────────────┬───────────────────────────────────────────────────────────────────────────────────────────────┐
│ Item │ Value │
├──────────────────────┼───────────────────────────────────────────────────────────────────────────────────────────────┤
│ OS │ windows 10.0.26200 (x64) · node 24.13.0 │
│ Dashboard │ http://127.0.0.1:18789/ │
│ Tailscale │ off │
│ Channel │ stable (default) │
│ Update │ pnpm · up to date · npm latest 2026.4.21 │
│ Gateway │ local · ws://127.0.0.1:18789 (local loopback) · unreachable (connect ECONNREFUSED 127.0.0. │
│ │ 1:18789) │
│ Gateway service │ Scheduled Task not installed │
│ Node service │ Scheduled Task not installed │
│ Agents │ 1 · no bootstrap files · sessions 0 · default main active unknown │
│ Memory │ enabled (plugin memory-core) · unavailable │
│ Plugin compatibility │ none │
│ Probes │ skipped (use --deep) │
│ Events │ none │
│ Tasks │ none │
│ Heartbeat │ 30m (main) │
│ Sessions │ 0 active · default gpt-5.4 (200k ctx) · ~.openclaw\agents\main\sessions\sessions.json │
└──────────────────────┴───────────────────────────────────────────────────────────────────────────────────────────────┘

#

Security audit
Summary: 2 critical · 1 warn · 1 info
CRITICAL Gateway auth missing on loopback
gateway.bind is loopback but no gateway auth secret is configured. If the Control UI is exposed through a reverse proxy, unauthenticated access is possible.
Fix: Set gateway.auth (token recommended) or keep the Control UI local-only.
CRITICAL Discord security warning
Discord guilds: groupPolicy="open" with no guild/channel allowlist; any channel can trigger (mention-gated). Set channels.discord.groupPolicy="allowlist" and c…
WARN Reverse proxy headers are not trusted
gateway.bind is loopback and gateway.trustedProxies is empty. If you expose the Control UI through a reverse proxy, configure trusted proxies so local-client c…
Fix: Set gateway.trustedProxies to your proxy IPs or keep the Control UI local-only.
Full report: openclaw security audit
Deep probe: openclaw security audit --deep

Channels
┌──────────┬─────────┬────────┬────────────────────────────────────────────────────────────────────────────────────────┐
│ Channel │ Enabled │ State │ Detail │
├──────────┼─────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ Discord │ ON │ OK │ token config (MTQ5…Oh94 · len 72) · accounts 1/1 │
└──────────┴─────────┴────────┴────────────────────────────────────────────────────────────────────────────────────────┘

Sessions
┌─────────────────────────────────────────────────────────────────────┬──────┬─────────┬──────────────┬────────────────┐
│ Key │ Kind │ Age │ Model │ Tokens │
├─────────────────────────────────────────────────────────────────────┼──────┼─────────┼──────────────┼────────────────┤
│ no sessions yet │ │ │ │ │
└─────────────────────────────────────────────────────────────────────┴──────┴─────────┴──────────────┴────────────────┘

FAQ: https://docs.openclaw.ai/faq
Troubleshooting: https://docs.openclaw.ai/troubleshooting
Next steps:
Need to share? openclaw status --all
Need to debug live? openclaw logs --follow
Fix reachability first: openclaw gateway probe
PS C:\Users\Somegh> openclaw gateway status

🦞 OpenClaw 2026.4.21 (f788c88) — I'm the middleware between your ambition and your attention span.

│
◇
Service: Scheduled Task (missing)
File logs: ~\AppData\Local\Temp\openclaw\openclaw-2026-04-22.log

Config (cli): ~.openclaw\openclaw.json
Config (service): ~.openclaw\openclaw.json

Gateway: bind=loopback (127.0.0.1), port=18789 (env/config)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: stopped (ERROR: The system cannot find the file specified.)
Connectivity probe: failed
Probe target: ws://127.0.0.1:18789
connect ECONNREFUSED 127.0.0.1:18789
Capability: unknown

Service unit not found.
Service not installed. Run: openclaw gateway install
File logs: C:\Users\Somegh\AppData\Local\Temp\openclaw\openclaw-2026-04-22.log
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting
PS C:\Users\Somegh> openclaw channels status --probe

🦞 OpenClaw 2026.4.21 (f788c88) — Deployed locally, trusted globally, debugged eternally.

│
◇
Gateway not reachable: Error: gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: C:\Users\Somegh.openclaw\openclaw.json
Bind: loopback

#

Possible causes:

Gateway not yet ready to accept connections (retry after a moment)
TLS mismatch (connecting with ws:// to a wss:// gateway, or vice versa)
Gateway crashed or was terminated unexpectedly
Run openclaw doctor for diagnostics.); resolved command secrets locally.
Gateway not reachable; showing config-only status.
Config: C:\Users\Somegh.openclaw\openclaw.json
Mode: local
Discord default: enabled, configured, token:config

Tip: status --deep adds gateway health probes to status output (requires a reachable gateway).

main chasmBOT Apr 22, 2026, 7:13 AM

#

That’s the problem right there.

Your status says:

Gateway: unreachable
Gateway service: Scheduled Task not installed

So the bot can’t reply because the gateway is not running.

Do this now

Easiest way

Open a PowerShell window and run:

openclaw gateway

#

Leave that window open.

Then in a second PowerShell window

Run:

openclaw status

You want the gateway to show as reachable, not ECONNREFUSED.

After that

DM the bot again in Discord.

If `openclaw gateway` crashes or exits

#

Run:

openclaw doctor

and paste the output here.

If you want it to run in the background later

You can install the Windows service/task with:

openclaw gateway install

But for now, just do:

#

openclaw gateway

That’s the next step.

#

You’re still only checking status. The gateway is not started yet.

This line is the key:

Runtime: stopped
Service not installed

So, don’t run openclaw gateway status right now.
Run the actual gateway:

openclaw gateway

Leave that PowerShell window open.

Then in a second PowerShell window

#

Run:

openclaw status

Now it should show the gateway as reachable.

Then

DM the bot in Discord.

Important

openclaw gateway restart won’t help yet because there is no installed service
openclaw gateway status only tells you it’s stopped
the security audit warnings are not what’s blocking replies right now

#

If `openclaw gateway` immediately exits or throws an error

Paste the full output of openclaw gateway here.
That’s the next thing we need.

#

That’s still status output, not the actual gateway starting.

We need the output from this exact command:

openclaw gateway

Not:

openclaw status
openclaw gateway status
openclaw gateway restart

Just:

#

openclaw gateway

What to do

open a fresh PowerShell window
run:

openclaw gateway

copy everything it prints
paste that here

If it instantly closes or prints nothing useful, then run:

#

openclaw doctor

and paste that output too.

Right now we’re missing the one output that actually matters: what happens when the gateway tries to start.

teal mango Apr 22, 2026, 7:22 AM

#

PS C:\Users\Somegh> openclaw doctor

🦞 OpenClaw 2026.4.21 (f788c88) — You had me at 'openclaw gateway start.'

▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
██░▄▄▄░██░▄▄░██░▄▄▄██░▀██░██░▄▄▀██░████░▄▄▀██░███░██
██░███░██░▀▀░██░▄▄▄██░█░█░██░█████░████░▀▀░██░█░█░██
██░▀▀▀░██░█████░▀▀▀██░██▄░██░▀▀▄██░▀▀░█░██░██▄▀▄▀▄██
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
🦞 OPENCLAW 🦞

┌ OpenClaw doctor
│
◇ Gateway ──────────────────────────────────────────────────────────╮
│ │
│ gateway.mode is unset; gateway start will be blocked. │
│ Fix: run openclaw configure and set Gateway mode (local/remote). │
│ Or set directly: openclaw config set gateway.mode local │
│ │
├────────────────────────────────────────────────────────────────────╯
│
◇ Gateway auth ──────────────────────────────────────────────────────────────────────╮
│ │
│ Gateway auth is off or missing a token. Token auth is now the recommended default │
│ (including loopback). │
│ │
├─────────────────────────────────────────────────────────────────────────────────────╯
│
◇ Generate and configure a gateway token now?
│ Yes
│
◇ Gateway auth ──────────────╮
│ │
│ Gateway token configured. │
│ │
├─────────────────────────────╯
│
◇ Create Session store dir at ~.openclaw\agents\main\sessions?
│ Yes
│
◇ State integrity ───────────────────────────────────────────────────────────╮
│ │
│ - CRITICAL: Session store dir missing (~.openclaw\agents\main\sessions). │
│ │
├─────────────────────────────────────────────────────────────────────────────╯
│
◇ Doctor changes ────────────────────────────────────────────────╮
│ │
│ - Created Session store dir: ~.openclaw\agents\main\sessions │
│ │
├─────────────────────────────────────────────────────────────────╯
│
◇ Security ─────────────────────────────────╮
│ │
│ - No channel security warnings detected. │
│ - Run: openclaw security audit --deep │
│ │
├────────────────────────────────────────────╯
│
◇ Skills status ────────────╮
│ │
│ Eligible: 7 │
│ Missing requirements: 45 │
│ Blocked by allowlist: 0 │
│ │
├────────────────────────────╯
│
◇ Plugins ──────╮
│ │
│ Loaded: 59 │
│ Imported: 59 │
│ Disabled: 40 │
│ Errors: 0 │
│ │
├────────────────╯
│
◇ Enable zsh shell completion for openclaw?
│ Yes
│
◇ Shell completion ───────────────────────────────────────────────────────╮
│ │
│ Shell completion installed. Restart your shell or run: source ~/.zshrc │
│ │
├──────────────────────────────────────────────────────────────────────────╯
│

#

◇
│
◇ Gateway ──────────────╮
│ │
│ Gateway not running. │
│ │
├────────────────────────╯
│
◇ Gateway connection ──────────────────────────────╮
│ │
│ Gateway target: ws://127.0.0.1:18789 │
│ Source: local loopback │
│ Config: C:\Users\Somegh.openclaw\openclaw.json │
│ Bind: loopback │
│ │
├───────────────────────────────────────────────────╯
│
◇ Gateway ────────────────────────╮
│ │
│ Gateway service not installed. │
│ │
├──────────────────────────────────╯
│
◇ Install gateway service now?
│ Yes
│
◇ Gateway service runtime
│ Node (recommended)

Installed Windows login item: C:\Users\Somegh\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\OpenClaw Gateway.cmd
Task script: C:\Users\Somegh.openclaw\gateway.cmd
Config overwrite: C:\Users\Somegh.openclaw\openclaw.json (sha256 d1ccacd7493d37e583280e982e70c31649e9ae2aa7a55c74ea9a8e161dca5a49 -> 9e7d9d5a4e2d282e2f5f8dca81148ae054351e97274ad6b29e19f6511c415546, backup=C:\Users\Somegh.openclaw\openclaw.json.bak)
Updated ~.openclaw\openclaw.json
Backup: ~.openclaw\openclaw.json.bak
│
└ Doctor complete.

#

who are you?

main chasmBOT Apr 22, 2026, 7:23 AM

#

Nice, doctor found the real blocker.

The issue

gateway.mode is unset; gateway start will be blocked.

Fix it

Run this:

openclaw config set gateway.mode local

Then start the gateway:

openclaw gateway

#

Leave that window open.

In a second PowerShell window

Check it:

openclaw status

Now the gateway should be reachable.

Then

DM your Discord bot again.

So the exact order is:

#

openclaw config set gateway.mode local
openclaw gateway

If openclaw gateway still errors after that, paste its output here.

#

If there’s a real OpenClaw bug here, please put it in a GitHub issue with the repro steps and output. We don’t forward random invite links to the team from support threads.

Issue tracker: https://github.com/openclaw/openclaw/issues

For the Windows install case above, the concrete next step is still:

openclaw config set gateway.mode local
openclaw gateway

#

Nice, that part worked, doctor installed the gateway startup stuff.

Now start the gateway

Run:

openclaw gateway start

Then check:

openclaw gateway status

You want it to show the gateway as running.

#

After that

DM your Discord bot again.

If `openclaw gateway start` doesn’t work

Just run it directly in a window:

openclaw gateway

and leave that window open.

So the next exact commands are:

openclaw gateway start

#

openclaw gateway status

#

I’m Krill 🦐, the OpenClaw support crustacean in here.

I help people get OpenClaw working, especially when setup gets messy like this. Right now I’m just trying to get your gateway running so your Discord bot can actually reply.

teal mango Apr 22, 2026, 7:31 AM

#

i got the pair key and i am now pairing yahh!!!!

main chasmBOT Apr 22, 2026, 7:31 AM

#

Hell yeah, nice 🎉

If you haven’t approved the pairing yet, do this on your PC:

openclaw pairing approve discord YOUR_CODE

If the bot is already replying in your Discord DMs, then you’re basically in ✅

If you want, next I can help you:

make it reply in your server channels too
change the AI/model
lock down the Discord security settings a bit

Glad we got it unstuck 😌

#

If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it for future people.

#

Let’s gooo 🎉

That means it’s finally connecting.

Next step: approve that pairing code on your PC:

openclaw pairing approve discord YOUR_CODE

After that, your bot should work in Discord DMs.

And yeah, don’t post the actual pairing code publicly. Keep it private.

If it replies after approval, you’re done ✅

teal mango Apr 22, 2026, 7:35 AM

#

now its not replying

main chasmBOT Apr 22, 2026, 7:35 AM

#

Okay, two likely causes:

the gateway window closed
the pairing didn’t fully approve

First

Make sure this is still running in a PowerShell window:

openclaw gateway

If that window closes, the bot stops replying.

Then run these and paste the output

#

openclaw status
openclaw pairing list discord
openclaw channels status --probe

Also tell me:

are you messaging it in a Discord DM or in a server channel?
did you already run:

openclaw pairing approve discord YOUR_CODE

If you paste those outputs, I can tell you exactly what’s missing.

#error

Recommended install

macOS / Linux / WSL2

Windows (PowerShell)

What should happen

If the normal installer keeps failing

If openclaw says “command not found”

Important notes

If it still breaks

macOS / Linux / WSL2

Windows PowerShell

Easiest path

If the keys don’t work

Change the default AI

If you only want to change it in the current chat

Try this on that same computer

If you are using another device

If it still fails

Check these first

If you want the fastest fix

If it feels broken, not just slow

Normal vs not normal

Big clue

Check this

Try this first in PowerShell

If it still breaks

Small note

1) Create the Discord bot

2) Copy your IDs

3) Connect the bot to OpenClaw

4) Enable DMs

5) Pair Discord DMs

Check where npm installed it

If you see openclaw.cmd

If you do not see openclaw.cmd

Install it now

If that works

If install succeeds but onboarding later hits the axios error again

Important

Fix

Why

1) Revoke that leaked OpenAI key

2) Repair OpenClaw

3) Run setup again

4) When it asks for the OpenAI key

5) After setup finishes

1) Create a Discord bot

2) Invite the bot to your own server

3) Turn on Discord Developer Mode

4) Connect that bot token to OpenClaw

5) Allow DMs

6) Pair the DM

Do this instead

1) Start the gateway

2) DM your Discord bot

3) In another PowerShell window

4) Approve the real code

Important

If you want it to keep running in the background later

Do this now

Easiest way

Then in a second PowerShell window

After that

If openclaw gateway crashes or exits

If you want it to run in the background later

Then in a second PowerShell window

Then

Important

If openclaw gateway immediately exits or throws an error

What to do

The issue

Fix it

In a second PowerShell window

Then

Now start the gateway

After that

If openclaw gateway start doesn’t work

First

Then run these and paste the output

If `openclaw` says “command not found”

If you see `openclaw.cmd`

If you do not see `openclaw.cmd`

If install succeeds but onboarding later hits the `axios` error again

If `openclaw gateway` crashes or exits

If `openclaw gateway` immediately exits or throws an error

If `openclaw gateway start` doesn’t work