#No response on UI

1 messages · Page 1 of 1 (latest)

trail bison
#

Hi Krill, please can you help me troubleshoot, I am not getting any responses on the browser UI. Full message is attached as file.

stable ploverBOT
reef pulsarBOT
#

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

fast egretBOT
#

Let me pull the actual support context and check the docs before I steer you wrong.

#

I couldn’t see the attachment on my side, so I’m checking the relevant docs/code paths and then I’ll give you the shortest useful next steps.

#

I can help, but I can’t see the attached file from this side.

First, please paste these:

openclaw --version
openclaw status --all
openclaw gateway status

Then tell me the exact UI symptom:

  • does it say unauthorized
  • disconnected (1008): pairing required
  • endless reconnecting
  • or chat sends but gets no reply / tokens stay at 0
#

If chat sends but nothing answers, also run this while reproducing once:

openclaw logs --follow

A few common cases:

  • pairing required → run:
    openclaw devices list
    openclaw devices approve <requestId>
    
  • unauthorized / reconnect loop → token or auth mode mismatch. Fastest reset is often:
    openclaw dashboard
    
#

Got it, thanks, that gives me the version baseline. I’m checking whether the rest of the pasted report/attachment came through so I can target the right failure mode.

#

Thanks, that version baseline looks okay, 2026.4.15 on Node 22.22.2 should be fine.

I still need the part of the report after that table, or at least these bits from openclaw status --all:

  • Gateway runtime
  • Connectivity probe
  • Capability
  • any error/warning lines
  • the last log tail snippet

Also, what exactly happens in the browser UI when you send a message?

  • spinner forever
  • tokens stay at 0
  • unauthorized
  • disconnected (1008): pairing required
  • reconnect loop
#
  • something else

Best next step is:

openclaw status --all
openclaw logs --follow

Then send one test message in the browser UI and paste the relevant 20 to 30 log lines here.

Quick shortcuts in case the symptom is obvious:

  • pairing required:
    openclaw devices list
    
#

Nice, that helps.

Dashboard = http://127.0.0.1:18789/ with Tailscale off means this is a local Control UI case, so it’s probably not an origin/Tailscale issue.

The next 3 checks I want are:

openclaw gateway status
openclaw models status
openclaw logs --follow

Then, while openclaw logs --follow is running, send one message in the browser UI and paste the log lines that appear.

Also tell me which of these matches the UI:

  • message sends, but no reply