Dashboard URL: http://127.0.0.1:18789/Token auto-auth included in browser/clipboard URL.Copied to | Friends of the Crustacean 🦞🤝 | Page 1

plucky cave May 10, 2026, 8:29 PM

#

and it does not provide a token . something is broken

broken dockBOT May 10, 2026, 8:30 PM

#

Virt — that part may be expected: openclaw dashboard intentionally does not print the token in terminal output. It usually opens/copies a URL with the token fragment, or gives a clean URL and expects you to paste the auth value locally.

Quick checks:

openclaw --version
openclaw status
openclaw config get gateway.auth.token

Don’t paste the token here. If gateway.auth.token is empty/missing, generate one:

openclaw doctor --generate-gateway-token
openclaw gateway restart
openclaw dashboard

#

If gateway.auth.token is a SecretRef/env-managed value, the dashboard command may deliberately only show http://127.0.0.1:18789/ and not embed the token. In that case either export OPENCLAW_GATEWAY_TOKEN in the same shell before running openclaw dashboard, or paste the resolved token into the Dashboard auth field.

Docs: https://docs.openclaw.ai/web/dashboard

plucky cave May 10, 2026, 8:31 PM

#

OPENCLAW_REDACTED when i try to get token

broken dockBOT May 10, 2026, 8:31 PM

#

Yep — that redaction is expected if you try to fetch/show it through OpenClaw/Discord. Secret-looking values get replaced with __OPENCLAW_REDACTED__ so nobody accidentally leaks a live gateway token into chat/logs.

Do this on the machine running the gateway, in your own terminal/browser:

openclaw dashboard

If it says “Token auto-auth included in browser/clipboard URL”, paste/open the clipboard URL locally — don’t ask the agent/chat to print it.

If the dashboard still won’t auth, rotate the token instead of trying to recover it:

openclaw config set gateway.auth.token "$(openssl rand -hex 32)"
openclaw gateway restart
openclaw dashboard

#

Then open the dashboard from that same machine/session. Do not paste the token here; the redactor will catch it anyway 🦞

plucky cave May 10, 2026, 8:35 PM

#

Health check failed: gateway timeout after 10000ms
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /home/virt/.openclaw/openclaw.json
Bind: loopback
│
◇ Gateway port ──────────────────────────────────────────────────────────────────────────╮
│ │
│ Port 18789 is already in use. │
│ - Port is in use but process details are unavailable (install lsof or run as an admin │
│ user). │
│

broken dockBOT May 10, 2026, 8:36 PM

#

That means there’s something listening on 18789, but the gateway health WebSocket isn’t responding. Most likely: stale/hung gateway process, different process on the port, or service/user mismatch.

First, please include your version:

openclaw --version

Then run:

openclaw gateway status --deep
openclaw logs --tail 80

To identify the port owner on Linux:

#

sudo ss -ltnp 'sport = :18789'

If it shows an openclaw process, try the clean restart path:

openclaw gateway restart
openclaw status

If restart still times out, paste the gateway status --deep + last log lines here. If ss shows a non-OpenClaw process, either stop that process or change the OpenClaw gateway port.

Docs: https://docs.openclaw.ai/gateway/troubleshooting

plucky cave May 11, 2026, 7:34 PM

#

what could be changed to make openclaw say no gui installed

broken dockBOT May 11, 2026, 7:35 PM

#

That message usually means OpenClaw’s onboarding/dashboard helper decided it can’t safely open a browser on the machine where the command is running.

From current source, the main things that can make it say “No GUI detected” are:

You’re running over SSH and there’s no display: SSH_CLIENT / SSH_TTY / SSH_CONNECTION is set, but DISPLAY / WAYLAND_DISPLAY is not.
Linux host has neither DISPLAY nor WAYLAND_DISPLAY set.
Linux has a display, but xdg-open is missing.
WSL without wslview and no Linux display.
macOS without the open command, or a LaunchAgent running outside a logged-in GUI session.

So if you expected a browser to open, check:

openclaw --version
echo "$DISPLAY $WAYLAND_DISPLAY $SSH_CONNECTION"
command -v xdg-open || command -v wslview || command -v open

#

If this is a VPS/headless box, it’s normal: use the SSH port-forward it prints, then open the Control UI locally. Docs: https://docs.openclaw.ai/gateway/remote and https://docs.openclaw.ai/web/control-ui

plucky cave May 11, 2026, 7:37 PM

#

OpenClaw 2026.5.7 (eeef486)
:0 wayland-0

broken dockBOT May 11, 2026, 7:37 PM

#

With DISPLAY=:0 and WAYLAND_DISPLAY=wayland-0, OpenClaw should not hit the pure “no display” branch.

The likely issue is that openclaw dashboard uses the same fallback text when browser opening fails, not only when no GUI exists. On Linux it needs xdg-open to exist and successfully launch the URL.

Check from the exact same shell/user:

command -v xdg-open
xdg-open http://127.0.0.1:18789/
echo "$XDG_RUNTIME_DIR"
echo "$DBUS_SESSION_BUS_ADDRESS"

Common fixes:

#

sudo apt install xdg-utils

And if this is Wayland but run from SSH/systemd/sudo, those env vars may be missing even though DISPLAY is set. Try running openclaw dashboard from a terminal inside the desktop session, or export:

export XDG_RUNTIME_DIR=/run/user/$(id -u)
export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus

Also: don’t run it with sudo; root usually can’t talk to your user’s Wayland session.

Tiny wording bug here: OpenClaw could say “browser launch failed” instead of “No GUI detected” when xdg-open exists but fails. That would make this much less confusing.

plucky cave May 11, 2026, 7:41 PM

#

how do i get my tokren

broken dockBOT May 11, 2026, 7:41 PM

#

If you ran openclaw dashboard, it usually does not print the token for safety — it either opens/copies a URL like:

http://127.0.0.1:18789/#token=...

Since your output says “Copied to clipboard”, try just pasting into your browser address bar.

If you need to see the configured gateway token directly, run:

openclaw config get gateway.auth.token

If that prints a SecretRef or nothing useful, check whether you set it via env:

#

echo "$OPENCLAW_GATEWAY_TOKEN"

Then open the dashboard URL and paste that token into Control → Overview → Gateway Access → Gateway Token.

Docs: https://docs.openclaw.ai/cli/dashboard

plucky cave May 11, 2026, 7:42 PM

#

openclaw config get gateway.auth.token openclaw redacted why would it say redacted now

broken dockBOT May 11, 2026, 7:42 PM

#

That’s expected/safe: gateway.auth.token is treated as a secret, so openclaw config get redacts it instead of dumping it into your terminal/Discord logs.

For the dashboard specifically, your earlier output said:

Token auto-auth included in browser/clipboard URL.
Copied to clipboard.

So the easiest path is: paste your clipboard into your local browser address bar. The URL should include #token=... and auto-auth.

If clipboard didn’t actually work, generate/replace the gateway token with one you know, then restart:

openclaw config set gateway.auth.token "$(openssl rand -hex 32)"
openclaw gateway restart

#

openclaw dashboard --no-open

Then paste the copied dashboard URL, or use that new token in Control → Overview → Gateway Access → Gateway Token.

Don’t paste the token into Discord once you have it 🦞

plucky cave May 11, 2026, 7:44 PM

#

?

broken dockBOT May 11, 2026, 7:45 PM

#

Sorry — I mean: redacted is normal. OpenClaw is intentionally hiding the token when you ask config for it.

Do this instead:

Run:

openclaw dashboard --no-open

Because it says Copied to clipboard, paste into your browser’s address bar with Ctrl+V. Don’t paste it here.

If that still only gives you http://127.0.0.1:18789/ without #token=..., then reset the token to a new one you know:

TOKEN=$(openssl rand -hex 32)
echo "$TOKEN"

#Dashboard URL: http://127.0.0.1:18789/Token auto-auth included in browser/clipboard URL.Copied to