Cant get into dashboard

[frank tide]

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

[hot knoll]

That usually means the gateway/dashboard server is not running anymore, or the saved URL points at the wrong host/port.

First, please run:

openclaw --version
openclaw gateway status
openclaw status

Then try reopening it through the CLI instead of the old browser bookmark:

openclaw dashboard

For a local install, the dashboard should normally be at:

http://127.0.0.1:18789/

If openclaw gateway status says it is not running, start it with:

openclaw gateway

Then refresh the dashboard. If it still says “This site can’t be reached”, paste the output of openclaw --version and openclaw gateway status here.

Docs refs: https://docs.openclaw.ai/web/dashboard and https://docs.openclaw.ai/help/faq#first-60-seconds-if-something-is-broken

[quasi bear]

Service: systemd user (enabled)
File logs: /tmp/openclaw/openclaw-2026-05-20.log
Command: /usr/bin/node /home/jdely3/.npm-global/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789

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

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
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: running (pid 415, state active, sub running, last exit 0, reason 0)
Warm-up: launch agents can take a few seconds. Try again shortly.
Connectivity probe: failed
Probe target: ws://127.0.0.1:18789
connect ECONNREFUSED 127.0.0.1:18789
Capability: unknown

Gateway port 18789 is not listening (service appears running).
Logs: journalctl --user -u openclaw-gateway.service -n 200 --no-pager
Restart log: ~/.openclaw/logs/gateway-restart.log

[hot knoll]

That output narrows it down: systemd thinks the service is running, but nothing is actually listening on 127.0.0.1:18789. So the browser error makes sense.

Please grab the version plus the gateway logs next:

openclaw --version
journalctl --user -u openclaw-gateway.service -n 200 --no-pager
tail -n 200 ~/.openclaw/logs/gateway-restart.log
tail -n 200 /tmp/openclaw/openclaw-2026-05-20.log

Also try a clean restart and then re-check:

openclaw gateway restart
sleep 5

[hot knoll]

openclaw gateway status

If the status still says Runtime: running but connect ECONNREFUSED, paste the first actual error/stack trace from the journal or log tail. The important bit is above/before the “not listening” symptom.

[quasi bear]

Service: systemd user (enabled)
File logs: /tmp/openclaw/openclaw-2026-05-20.log
Command: /usr/bin/node /home/jdely3/.npm-global/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789

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

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
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.

CLI version: 2026.5.12 (~/.npm-global/bin/openclaw)
Gateway version: 2026.5.12

Runtime: running (pid 825, state active, sub running, last exit 0, reason 0)
Connectivity probe: ok
Capability: read-only

Listening: 127.0.0.1:18789
OpenClaw 2026.5.12 (f066dd2)

[hot knoll]

Good, the gateway is healthy now:

• Connectivity probe: ok
• Listening: 127.0.0.1:18789

Open this on the same computer that is running OpenClaw:

http://127.0.0.1:18789/

Or run:

openclaw dashboard

One catch: your gateway is bind=loopback, so it only works from that same machine. If you’re trying from another computer/phone, it will still show “site can’t be reached” unless you use Tailscale/SSH tunnel/remote access setup.

[hot knoll]

If the dashboard opens now, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow indexes it for the next person.

[quasi bear]

no im not in

[hot knoll]

Got it. Since the gateway is listening now, the next split is what the browser is seeing.

Please try this exact URL on the same computer that ran openclaw gateway status:

http://127.0.0.1:18789/

Then tell me which one happens:

1. Still “This site can’t be reached”
2. Page loads but says disconnected / unauthorized / pairing required
3. Page loads but asks for a token/password

If it’s #1, run this and paste the output:

curl -v http://127.0.0.1:18789/

[hot knoll]

If it’s #2 and says pairing required:

openclaw devices list

If it’s #3, get the token with:

openclaw config get gateway.auth.token

Then paste it into the dashboard’s Gateway Token field.

[hot knoll]

That curl output is actually good news: OpenClaw is serving the dashboard HTML successfully.

So now there are two likely cases:

If your browser shows “This site can’t be reached”
You’re probably opening the browser outside the environment where OpenClaw is bound. Your prompt says DESKTOP-I238VPJ, so if this is WSL and you’re using a Windows browser, try opening it from WSL with:

explorer.exe http://127.0.0.1:18789/

If Windows still can’t reach it but WSL curl can, restart the WSL bridge:

wsl --shutdown

[hot knoll]

Then reopen WSL and run:

openclaw gateway restart
openclaw dashboard

If the page loads but says “Control UI did not start” or is blank
That points to the app bundle being blocked in the browser. Try a private/incognito window, or disable extensions for 127.0.0.1, then hard refresh.

The key detail: curl got HTTP/1.1 200 OK, so the gateway itself is no longer the broken part.

[quasi bear]

jdely3@DESKTOP-I238VPJ:~$ wsl --shutdown
Unknown command: --shutdown
WSL
Wsman Shell commandLine, version 0.2.1

USAGE: wsl COMMAND [PARAMS...]

COMMANDS:
identify - WS-Identify
enum - WS-Enumerate
get - WS-Get
put - WS-Put
invoke - WS-Invoke
xclean - Delete all files generated by this tool set
xcred - Create or display credential file
xcert - Get server certificate (saved to <IPADDRESS>.crt)

PARAMS specification is specific to a COMMAND.

Output will be saved to ./response.xml. If you want to run parallel
executions in the same directory, define RTFILEPREFIX in the environment.
Doing so may significantly increase files generated.

Requires: curl, xmllint, GNU core utilities.
Optional: xsltproc for output formatting, gpg for encrypted credential.
Optional: wget as alternate for curl when not available.

[hot knoll]

Ah, that wsl --shutdown needs to be run from Windows PowerShell or Command Prompt, not inside the Linux shell. Inside Linux, wsl is a different tool on your PATH, which is why you got the Wsman output.

From your current Linux terminal, try this first:

explorer.exe http://127.0.0.1:18789/

If that still does not open the dashboard, open Windows PowerShell and run:

wsl --shutdown

Then reopen your Ubuntu/WSL terminal and run:

[hot knoll]

openclaw gateway restart
openclaw dashboard

Small correction from me: I should have explicitly said the shutdown command goes in Windows PowerShell.

[quasi bear]

It brings me to it on explorer. I need it on google

[hot knoll]

Got it — you mean Google Chrome.

From the WSL/Linux terminal, run:

powershell.exe -NoProfile -Command "Start-Process chrome 'http://127.0.0.1:18789/'"

If Chrome opens but still shows the old “site can’t be reached” page, hard refresh it with Ctrl+Shift+R, or open an incognito Chrome window and paste:

http://127.0.0.1:18789/

If the command says it can’t find Chrome, try this from Windows PowerShell instead:

Start-Process "C:\Program Files\Google\Chrome\Application\chrome.exe" "http://127.0.0.1:18789/"

[quasi bear]

I opened it on incognito and it still brings me to “site can’t be reached”

[hot knoll]

If Edge/Explorer can open it but Chrome incognito cannot, OpenClaw is reachable — this is probably Chrome using a proxy/VPN/security setting or trying the wrong URL.

In Chrome, type the full URL directly in the address bar, including http://:

http://127.0.0.1:18789/

Also try:

http://localhost:18789/

If both fail in Chrome, launch a clean Chrome with proxy disabled from Windows PowerShell:

Start-Process chrome --args "--no-proxy-server" "http://127.0.0.1:18789/"

If that works, Chrome has a proxy/VPN/extension setting intercepting localhost. If it still fails, paste the exact Chrome error code under “site can’t be reached” — usually something like ERR_CONNECTION_REFUSED, ERR_ADDRESS_UNREACHABLE, or ERR_TUNNEL_CONNECTION_FAILED.

[quasi bear]

the second one worked now I need to get into the dashbaord

[hot knoll]

Nice — use the one that worked, probably:

http://localhost:18789/

Now what do you see on the page?

If it asks for Gateway Token, run this in your OpenClaw terminal:

openclaw config get gateway.auth.token

Paste that value into the dashboard’s Gateway Token field, then click Connect.

If it says pairing required, run:

[hot knoll]

openclaw devices list
openclaw devices approve <requestId>

Use the request id shown by devices list.

If you’re not sure which screen you’re on, send a screenshot or paste the exact dashboard message.

[quasi bear]

jdely3@DESKTOP-I238VPJ:~$ openclaw config get gateway.auth.token

🦞 OpenClaw 2026.5.12 (f066dd2) — The lobster in your shell. 🦞

OPENCLAW_REDACTED

[hot knoll]

That __OPENCLAW_REDACTED__ is not the token — it’s OpenClaw protecting the secret in terminal output. Don’t paste tokens here.

Try the built-in dashboard opener first:

openclaw dashboard --no-open

Copy the URL it prints into Chrome. If it prints 127.0.0.1 and Chrome is being weird, change just that part to localhost.

If the page still needs a token and you can’t reveal the old one, rotate it to a new one you can paste locally:

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

[hot knoll]

openclaw gateway restart
printf "Paste this into Gateway Token: %s
" "$TOKEN"

Paste that printed value into the dashboard’s Gateway Token field, then Connect. Keep that token private.

[quasi bear]

Token auto-auth included in browser/clipboard URL.
Copied to clipboard.
it copied it to my clippboard and I pasted it in google and i got site cant be reached

[hot knoll]

That copied URL is probably using 127.0.0.1, and we already found Chrome only works for you with localhost.

Do this carefully:

1. Paste the copied URL into Notepad, not Discord.
2. Change only this part:

http://127.0.0.1:18789/

to:

http://localhost:18789/

[hot knoll]

3. Keep everything after it exactly the same, especially the #token=... part.
4. Paste that edited full URL into Chrome.

Example shape:

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

Don’t paste the full token URL here. It’s secret.

[quasi bear]

im in teh dashboard. but everytime i come back to my computer I have to go throughn this process with you to open it again. How can i make it so i cant easily open it everytime

[hot knoll]

Glad you’re in. For your setup, the annoying part is that openclaw dashboard copies a 127.0.0.1 URL, but Chrome on your machine needs localhost.

Easiest repeatable fix: make a tiny shortcut command in WSL:

echo 'alias dashboard="openclaw dashboard --no-open >/dev/null && powershell.exe -NoProfile -Command '"'"'$u=(Get-Clipboard).Replace("127.0.0.1","localhost"); Set-Clipboard $u; Start-Process chrome $u'"'"'"' >> ~/.bashrc
source ~/.bashrc

After that, whenever you want the dashboard, run:

dashboard

That will:

• ask OpenClaw for the proper tokenized dashboard URL

[hot knoll]

• swap 127.0.0.1 to localhost
• open it in Chrome

Don’t share the copied URL, because it may include #token=....

Once this is working, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow indexes the fix.

[quasi bear]

jdely3@DESKTOP-I238VPJ:~$ dashboard
At line:1 char:36

• =(Get-Clipboard).Replace(127.0.0.1,localhost); Set-Clipboard ; Start- ...

•                                ~
  

Missing expression after ','.
At line:1 char:45

• =(Get-Clipboard).Replace(127.0.0.1,localhost); Set-Clipboard ; Start- ...

•                                         ~
  

Unexpected token ')' in expression or statement.
+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingExpressionAfterToken

[hot knoll]

Yep, my quoting got mangled there. Sorry — PowerShell ate the quotes.

Run this in your WSL terminal to replace the bad shortcut with a cleaner function:

sed -i.bak '/alias dashboard=/d' ~/.bashrc

cat >> ~/.bashrc <<'EOF'
dashboard() {
  openclaw dashboard --no-open >/dev/null
  powershell.exe -NoProfile -Command '$u=(Get-Clipboard) -replace "127.0.0.1","localhost"; Set-Clipboard -Value $u; Start-Process chrome $u'
}
EOF

source ~/.bashrc
dashboard

[hot knoll]

That removes only the broken alias dashboard=... line, saves a backup at ~/.bashrc.bak, then adds a proper dashboard function.

[quasi bear]

jdely3@DESKTOP-I238VPJ:~$ sed -i.bak '/alias dashboard=/d' ~/.bashrc

cat >> ~/.bashrc <<'EOF'
dashboard() {
openclaw dashboard --no-open >/dev/null
powershell.exe -NoProfile -Command '$u=(Get-Clipboard) -replace "127.0.0.1","localhost"; Set-Clipboard -Value $u; Start-Process chrome $u'
}
EOF

source ~/.bashrc
dashboard
-bash: /home/jdely3/.bashrc: line 126: syntax error near unexpected token (' -bash: /home/jdely3/.bashrc: line 126: dashboard() {'
At line:1 char:36

• =(Get-Clipboard).Replace(127.0.0.1,localhost); Set-Clipboard ; Start- ...

•                                ~
  

Missing expression after ','.
At line:1 char:45

• =(Get-Clipboard).Replace(127.0.0.1,localhost); Set-Clipboard ; Start- ...

•                                         ~
  

Unexpected token ')' in expression or statement.
+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingExpressionAfterToken

[hot knoll]

The bad first shortcut left your .bashrc in a broken state, so source ~/.bashrc is still hitting it. Let’s clean that out and avoid putting the dashboard command in .bashrc at all.

Run this whole block in WSL:

cp ~/.bashrc ~/.bashrc.broken-dashboard

awk '/alias dashboard=|^dashboard\(\) \{/ { exit } { print }' ~/.bashrc > ~/.bashrc.clean
mv ~/.bashrc.clean ~/.bashrc

mkdir -p ~/.local/bin

cat > ~/.local/bin/dashboard <<'EOF'
#!/usr/bin/env bash
set -e
openclaw dashboard --no-open >/dev/null

[hot knoll]

powershell.exe -NoProfile -Command '$u=(Get-Clipboard) -replace "127\.0\.0\.1","localhost"; Set-Clipboard -Value $u; Start-Process chrome $u'
EOF

chmod +x ~/.local/bin/dashboard
~/.local/bin/dashboard

If that opens Chrome correctly, you can use this anytime:

~/.local/bin/dashboard

If you want just dashboard later, we can add ~/.local/bin to PATH after your .bashrc is clean.

[quasi bear]

How do i save that command and have it on my homescreen to click on it like an app to run it

[hot knoll]

Yep. Make a Windows desktop shortcut that runs your WSL dashboard script.

First make sure this works from WSL:

~/.local/bin/dashboard

Then create the desktop shortcut from Windows:

1. Right-click your Windows desktop → New → Shortcut
2. For the location, paste:

C:\Windows\System32\wsl.exe bash -lc "~/.local/bin/dashboard"

[hot knoll]

3. Name it:

OpenClaw Dashboard

4. Click Finish

Now double-clicking that desktop icon should run the WSL command and open Chrome to the dashboard.

If the shortcut window opens and closes too fast or does nothing, use this location instead so it stays open long enough to show errors:

C:\Windows\System32\wsl.exe bash -lc "~/.local/bin/dashboard; read -p 'Press Enter to close...'"

[quasi bear]

I also need to update openclaw dashboard will that mess up the command? Update available: v2026.5.19 (running v2026.5.12). and when i select update now it loads and then stops with out updating

[hot knoll]

Updating should not mess up the desktop shortcut/script. The shortcut runs openclaw dashboard --no-open, so after OpenClaw updates it will keep using the current openclaw command.

The dashboard’s Update now may be failing because your gateway showed Capability: read-only earlier. Do the update from the WSL terminal instead:

openclaw update
openclaw gateway restart
openclaw --version
openclaw gateway status

If openclaw update fails, paste the error. Since your install path is ~/.npm-global/.../openclaw, the manual fallback is usually:

npm install -g openclaw@latest
openclaw gateway restart

[hot knoll]

openclaw --version

After that, your desktop shortcut should still work. If it opens 127.0.0.1 again, the ~/.local/bin/dashboard script still handles swapping it to localhost.

Docs: https://docs.openclaw.ai/install/updating

[quasi bear]

It worked now how do i keep the command on my home screen like i asked befpre

[hot knoll]

Yep — now that ~/.local/bin/dashboard works, make a Windows desktop shortcut for it:

1. Go to your Windows desktop.
2. Right-click empty space → New → Shortcut.
3. In “Type the location of the item”, paste this:

C:\Windows\System32\wsl.exe bash -lc "~/.local/bin/dashboard"

4. Click Next.
5. Name it:

OpenClaw Dashboard

[hot knoll]

6. Click Finish.

Now you should have an icon on your desktop/home screen. Double-click it whenever you want the dashboard.

If it opens and closes without doing anything, edit the shortcut location to this debug version:

C:\Windows\System32\wsl.exe bash -lc "~/.local/bin/dashboard; read -p 'Press Enter to close...'"

Also: glad the update worked. Once the shortcut works too, please right-click the message that solved it → Apps → ✅ Mark Solution so it gets indexed for future users.

[quasi bear]

when i click new the only option is folder

[hot knoll]

No problem — make the shortcut from PowerShell instead.

Open Windows PowerShell and paste this:

$Desktop = [Environment]::GetFolderPath("Desktop")
$ShortcutPath = Join-Path $Desktop "OpenClaw Dashboard.lnk"
$Wsh = New-Object -ComObject WScript.Shell
$Shortcut = $Wsh.CreateShortcut($ShortcutPath)
$Shortcut.TargetPath = "C:\Windows\System32\wsl.exe"
$Shortcut.Arguments = 'bash -lc "~/.local/bin/dashboard"'
$Shortcut.WorkingDirectory = $Desktop
$Shortcut.IconLocation = "C:\Windows\System32\wsl.exe,0"
$Shortcut.Save()

That should create OpenClaw Dashboard on your desktop.

[hot knoll]

If you want it pinned too: right-click the new shortcut → Show more options → Pin to taskbar or Pin to Start.

[quasi bear]

it works now how do i change the icon to something cooler

[hot knoll]

Nice. Easiest way:

1. Right-click OpenClaw Dashboard shortcut
2. Click Properties
3. Click Change Icon...
4. Pick an icon, then OK → Apply

If you want a lobster/OpenClaw-style icon, use an .ico file. Put it somewhere permanent like:

C:\Users\YOUR_WINDOWS_USERNAME\Pictures\openclaw.ico

Then in Change Icon..., browse to that file.

Quick built-in option: in the Change Icon box, paste this path and press Enter:

[hot knoll]

C:\Windows\System32\shell32.dll

That gives you a bunch of Windows icons to choose from. Not lobster-tier, but better than the default WSL icon.

[quasi bear]

will this change if i switch models

[hot knoll]

No — switching models should not change this shortcut.

The shortcut only does:

wsl.exe bash -lc "~/.local/bin/dashboard"

And that script just runs openclaw dashboard --no-open, changes 127.0.0.1 to localhost, then opens Chrome. Model settings live inside OpenClaw config/dashboard, separate from the Windows shortcut.

The only times you’d need to fix the shortcut are if you delete ~/.local/bin/dashboard, change WSL distros/users, or reinstall OpenClaw somewhere very differently.

[quasi bear]

what is WSL distros/users