#Dashboard link is not working for installing OpenClaw on MacOS version 23+

1 messages · Page 1 of 1 (latest)

rustic joltBOT
#

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

heady burrow
#

True

vague hamlet
#

Help

wanton fableBOT
#

Most commonly this happens for one of these reasons:

  1. 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:// or wss://, that’s for the TUI/clients, not the browser UI.
  2. 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 --all is designed to be shareable; it redacts tokens.)

  3. You’re opening the link on a different device than the machine running the Gateway
    If the URL is http://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):
    ssh -N -L 18789:127.0.0.1:18789 user@<gateway-host>
    
    then open 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):

  1. The URL you’re pasting (redact anything after # if present), and say whether it starts with http:// or ws://
  2. The exact browser error text (e.g. “connection refused”, “site can’t be reached”, “unauthorized”)
  3. 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.token on the gateway host.

Docs for this exact issue:

vague hamlet
#

I have a MacOS 26 version but I'm not able to open OpenClaw. What happened?

wanton fableBOT
#

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 status shows 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.

vague hamlet
#

I can't open it in my browser

wanton fableBOT
#

If you can’t open it in the browser, we need to know what error you’re getting and whether the gateway is listening.

  1. What exact URL are you trying to open? (Paste it, but remove anything after # if present.)

  2. What does the browser say? (e.g. “This site can’t be reached”, “ERR_CONNECTION_REFUSED”, “unauthorized”, etc.)

  3. 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
vague hamlet
#

Despite troubleshooting, the link in my browser still won't open

wanton fableBOT
#

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.

vague hamlet
#

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.

wanton fableBOT
#

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:

vague hamlet
#

⚠️ Agent failed before reply: No API key found for provider "anthropic".

What happened?

wanton fableBOT
#

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

  1. Put it in the gateway host’s env (service-safe place):
    • create/edit ~/.openclaw/.env and add:
      ANTHROPIC_API_KEY=sk-ant-...
      
  2. Restart:
    openclaw gateway restart
    
  3. Verify:
#
   openclaw models status

B) If you use Claude subscription auth (setup-token)

  • Run:
    openclaw models auth setup-token --provider anthropic
    
    (or generate claude setup-token elsewhere and paste it with openclaw 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