cant get messages on openclaw dashboard

[flint torrent]

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

[odd meteor]

Yeah, that Java error is very often caused by a $ in a regex replacement string.

In Java, if some code is doing replaceAll(...) / replaceFirst(...), the replacement treats $1, $2, etc. as “capture group references”. So a literal $ (or $ followed by something that isn’t a valid group number) can throw:

java.lang.IllegalArgumentException: Illegal group reference

Fix (if you control the code)

Prefer one of these:

// If you don't need regex:
out = in.replace(oldLiteral, newLiteral);

// If you do need regex, but replacement should be literal:

out = in.replaceAll(pattern, java.util.regex.Matcher.quoteReplacement(replacement));

Or escape $ in the replacement:

replacement = replacement.replace("$", "\\$");

To confirm

Where exactly are you seeing this 500? (OpenClaw itself is Node/TS, so a Java exception usually means some other service in the chain is doing regex replacement.) If you paste:

• the full error (or stack trace),
• what input string contained the $,
• and what operation you were doing (sending a message? template variable? etc.)

…I can point to the exact spot that needs escaping.

[dapper kayak]

im seeing the error in the openclaw gateway dashboard

[odd meteor]

If you’re seeing 500 java.lang.IllegalArgumentException: Illegal group reference in the OpenClaw dashboard, that’s a big clue: OpenClaw itself is Node/TS, so the dashboard is almost certainly just surfacing the error text returned by something else (some upstream service / integration your gateway is calling), not “a Java error inside OpenClaw”.

$ can trigger that exact Java exception, but only when some Java code is doing a regex replacement (replaceAll/replaceFirst) with an unescaped $ in the replacement string.

To pinpoint where it’s coming from, can you grab one of these two (either is fine):

1. Browser DevTools (fastest)

• Open dashboard → DevTools → Network
• Reproduce the error
• Click the failing request (the one returning 500) and paste:
  • the Request URL / path (e.g. /api/...)
  • the Response body (or screenshot)

2. Gateway diagnostics (safe to paste; tokens redacted)
   On the gateway host run:

openclaw --version
openclaw status --all

…and paste the output around the failure.

If you can also tell me what you clicked in the dashboard right before it 500’d (loading messages list? sending a message? connecting a channel?), I can usually tell which integration is throwing the Java regex error and what needs escaping.

[dapper kayak]

i dont see what you are talking about for number 1.

[odd meteor]

No worries — “DevTools → Network” is a browser thing, and it’s easy to miss if you haven’t used it before.

If you’re on a computer (Chrome / Edge)

1. Open the OpenClaw dashboard tab.
2. Open DevTools:
   • Windows/Linux: press F12 or Ctrl + Shift + I
   • Mac: Cmd + Option + I
   • Or right-click anywhere on the page → Inspect
3. In the DevTools panel that opens, click the Network tab.
   • If you don’t see it, click the » overflow menu to find Network.
4. With Network open, reproduce the error in the dashboard.
5. You should see a new row appear with Status = 500 (often colored red).
6. Click that row → on the right, click Response (or Preview) and paste what it shows (and/or the request URL under Headers).

If you’re on a phone/tablet

You probably won’t have Network/DevTools. In that case, do this instead on the gateway host and paste the output:

openclaw --version
openclaw status --all

Also: what browser/OS are you using (Chrome on Windows, Safari on Mac, etc.)? That changes where those menus live.

[dapper kayak]

Gateway logs (tail, summarized): /Users/djryan/.openclaw/logs

stderr: /Users/djryan/.openclaw/logs/gateway.err.log

2026-03-07T18:38:57.557-05:00 Config write audit: /Users/djryan/.openclaw/logs/config-audit.jsonl
2026-03-07T18:38:59.418-05:00 Gateway start blocked: set gateway.mode=local (current: unset) or pass --allow-unconfigured.
2026-03-07T18:38:59.423-05:00 Config write audit: /Users/djryan/.openclaw/logs/config-audit.jsonl
2026-03-07T23:39:47.209Z [ws] unauthorized conn=1712933d-e24d-4155-b784-c23b6f1bfda1 remote=127.0.0.1 client=openclaw-control-ui webchat vdev reason=token_mismatch
2026-03-07T23:39:47.213Z [ws] closed before connect conn=1712933d-e24d-4155-b784-c23b6f1bfda1 remote=127.0.0.1 fwd=n/a origin=http://127.0.0.1:18789 host=127.0.0.1:18789 ua=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 code=4008 reason=connect failed
2026-03-07T23:39:53.204Z [diagnostic] lane task error: lane=main durationMs=14 error="Error: No API key found for provider "anthropic". Auth store: /Users/djryan/.openclaw/agents/main/agent/auth-profiles.json (agentDir: /Users/djryan/.openclaw/agents/main/agent). Configure auth for this agent (openclaw

[odd meteor]

The log snippet you pasted doesn’t show that Java exception at all — it shows three separate, very fixable problems that will make the dashboard misbehave:

1. Gateway auth token mismatch (Control UI can’t connect)

[ws] unauthorized ... reason=token_mismatch

Fix:

• On the gateway machine, run:

  openclaw config get gateway.auth.token
  

• In the dashboard go to Control → Overview → Gateway Access and paste that value into Gateway Token (not the Password box), then Connect.

2. No model credentials (agent can’t run)

No API key found for provider "anthropic"

Fix (Anthropic API key path, from docs):

• Run:

  openclaw onboard
  

  and choose Anthropic API key, or do it non-interactively:

  openclaw onboard --anthropic-api-key "$ANTHROPIC_API_KEY"
  

Docs: https://docs.openclaw.ai/providers/anthropic

Then verify:

openclaw models status

3. At some point the gateway was “unconfigured”

Gateway start blocked: set gateway.mode=local (current: unset) ...

openclaw onboard should also take care of this. After onboarding, do:

openclaw gateway restart

---

About the “500 … Illegal group reference” you originally saw

That error still might be real, but it’s not in the log lines you pasted.