#Dashboard link is not working for installing OpenClaw on MacOS version 23+
1 messages · Page 1 of 1 (latest)
True
Help
Most commonly this happens for one of these reasons:
-
The link you’re pasting is a WebSocket URL (
ws://…), not the dashboard URL- A normal browser tab must use HTTP:
http://127.0.0.1:18789/ - If your link starts with
ws://orwss://, that’s for the TUI/clients, not the browser UI.
- A normal browser tab must use HTTP:
-
The Gateway isn’t actually running, so every browser shows “can’t connect / refused”
Run these on the same machine where you installed OpenClaw and paste the output here:openclaw --version openclaw gateway status openclaw status --all(
status --allis designed to be shareable; it redacts tokens.) -
You’re opening the link on a different device than the machine running the Gateway
If the URL ishttp://127.0.0.1:18789/, that only works on the same computer (127.0.0.1 = “this computer”).
If the Gateway is on another machine/VPS, you usually want either:
- SSH tunnel (quickest):
then openssh -N -L 18789:127.0.0.1:18789 user@<gateway-host>http://127.0.0.1:18789/locally, or - Tailscale Serve (recommended for remote):
see https://docs.openclaw.ai/web/dashboard and the FAQ section “authenticate the dashboard token on localhost vs remote”.
One important safety note: don’t paste/share your gateway token in the thread. If a command prints a tokenized URL, redact the token part before posting.
Which part is “true” for you?
Can you paste just these three things (and redact any token if you see one):
- The URL you’re pasting (redact anything after
#if present), and say whether it starts withhttp://orws:// - The exact browser error text (e.g. “connection refused”, “site can’t be reached”, “unauthorized”)
- Output of:
openclaw --version
openclaw gateway status
That’ll tell us immediately whether it’s (a) wrong URL type, (b) gateway not running/listening, or (c) trying to open 127.0.0.1 from the wrong machine.
If the dashboard link doesn’t open in any browser, it’s almost always because the Gateway isn’t running / not listening on the port, or you’re trying to open a ws://… link in a browser.
On your Mac, run these exact commands and paste the output here:
openclaw --version
openclaw gateway status
Then try opening the dashboard the “clean” way:
openclaw dashboard
Or manually in any browser:
What the results mean:
-
Browser says “site can’t be reached / connection refused” → Gateway isn’t listening. Fix is usually:
openclaw gateway restart(and re-check
openclaw gateway status) -
Browser opens, but UI says “unauthorized” → you need to paste your token into the Control UI settings (don’t post the token in Discord). The token lives at
gateway.auth.tokenon the gateway host.
Docs for this exact issue:
I have a MacOS 26 version but I'm not able to open OpenClaw. What happened?
macOS version (even “26”) isn’t usually the blocker here — what matters is whether the OpenClaw Gateway is actually running on your Mac. The “dashboard link” only works if something is listening on 127.0.0.1:18789.
On your Mac, please run these and paste the output:
openclaw --version
openclaw gateway status
Then try:
openclaw dashboard
Quick interpretation:
-
If
openclaw gateway statusshows not running (or the probe fails), start/restart it:openclaw gateway restart(or if you haven’t done the setup yet:
openclaw onboard --install-daemon) -
If the gateway is running, open this in your browser on the same Mac:
http://127.0.0.1:18789/
Also: don’t paste any token values into Discord. If you tell me what error the browser shows (“connection refused” vs “unauthorized”), I can point you to the exact fix.
I can't open it in my browser
If you can’t open it in the browser, we need to know what error you’re getting and whether the gateway is listening.
-
What exact URL are you trying to open? (Paste it, but remove anything after
#if present.) -
What does the browser say? (e.g. “This site can’t be reached”, “ERR_CONNECTION_REFUSED”, “unauthorized”, etc.)
-
In Terminal on the same Mac, run and paste the output (even if it shows an error):
openclaw gateway status
That output will tell us the key thing: is OpenClaw actually running, and on what address/port.
If you haven’t run onboarding yet, do this once (it installs/starts the service and normally opens the dashboard):
openclaw onboard --install-daemon
Despite troubleshooting, the link in my browser still won't open
At this point “tried multiple browsers” doesn’t narrow it down — if the URL won’t open, it’s almost always one of:
- nothing is listening on that address/port (gateway not running, crashed, wrong port/bind), or
- you’re opening the wrong kind of URL (e.g.
ws://…), or - you’re opening 127.0.0.1 on the wrong machine.
We can’t guess which one without the gateway’s view of reality. Please paste the output of one command (it’s safe to share; tokens get redacted):
openclaw status --all
If you’d rather keep it shorter, paste just:
openclaw gateway status
and also paste the URL you’re trying to open up to the port only (example: http://127.0.0.1:18789/), plus the exact browser error text (“ERR_CONNECTION_REFUSED” vs “unauthorized” are totally different fixes).
Once I see gateway status (especially the “Listening:” / “Probe target:” lines), I can tell you the exact next step.
Gateway port 18789 is not listening (service appears running).
Last gateway error: 2026-03-13T13:34:39.370-04:00 Gateway start blocked: set gateway.mode=local (current: unset) or pass --allow-unconfigured.
That error explains it: the service is up, but the Gateway refuses to start, so nothing is listening on port 18789 → the dashboard URL can’t load.
Fix (on the Mac where you installed OpenClaw):
openclaw config set gateway.mode "local"
openclaw gateway restart
Then verify it’s actually listening:
openclaw gateway status
Once you see it listening, open:
http://127.0.0.1:18789/
or just run:
openclaw dashboard
Docs reference for this exact signature: https://docs.openclaw.ai/gateway/troubleshooting (search for “Gateway start blocked: set gateway.mode=local”).
⚠️ Agent failed before reply: No API key found for provider "anthropic".
What happened?
That means the Gateway is now running, but when it tries to generate a reply it can’t call the model because Anthropic credentials aren’t configured.
So OpenClaw is basically saying: “my default provider is anthropic, but I don’t have an API key / token for it.”
Fix (pick one)
A) If you have an Anthropic API key
- Put it in the gateway host’s env (service-safe place):
- create/edit
~/.openclaw/.envand add:ANTHROPIC_API_KEY=sk-ant-...
- create/edit
- Restart:
openclaw gateway restart - Verify:
openclaw models status
B) If you use Claude subscription auth (setup-token)
- Run:
(or generateopenclaw models auth setup-token --provider anthropicclaude setup-tokenelsewhere and paste it withopenclaw models auth paste-token --provider anthropic) - Then restart the gateway.
C) Re-run the wizard and choose a provider you do have credentials for
openclaw onboard
Docs:
- https://docs.openclaw.ai/providers/anthropic
- https://docs.openclaw.ai/help/faq (search “No API key found for provider anthropic” / “setup-token”)
If you paste the output of openclaw models status here (it’s safe), I can tell you exactly what it’s currently trying to use and what’s missing.