APP ERROR | Friends of the Crustacean 🦞🤝 | Page 1

boreal totem Apr 27, 2026, 8:33 PM

#

Help diagnose this OpenClaw Android gateway connection failure.

Please:

pick one route only: same machine, same LAN, Tailscale, or public URL
classify this as pairing/auth, TLS trust, wrong advertised route, wrong address/port, or gateway down
remember: Tailscale/public mobile routes require wss:// or Tailscale Serve; private LAN ws:// is still allowed
quote the exact app status/error below
tell me whether openclaw devices list should show a pending pairing request
if more signal is needed, ask for openclaw qr --json, openclaw devices list, and openclaw nodes status
give the next exact command or tap

Debug info:

screen: onboarding final check
app version: 2026.4.5
device: INFINIX Infinix X6870
android: 15 (SDK 35)
gateway address: http://192.168.1.22:18789
status/error: Connected (operator offline)

swift skiffBOT Apr 27, 2026, 8:33 PM

#

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

median needleBOT Apr 27, 2026, 8:35 PM

#

Route: same LAN (192.168.1.22:18789). Private LAN ws:///http:// is okay here.

Classification: pairing/auth, specifically the operator side is missing/offline — not gateway down, not TLS trust, not wrong address/port.

Exact app status/error: Connected (operator offline)

openclaw devices list should not necessarily show a pending node pairing for this exact status, because the node side appears connected. If it does show a pending request, approve the one matching the INFINIX/Android device.

Next exact command on the gateway host:

openclaw nodes status

If the phone appears there, next tap in the Android app: Connect again on the final check screen to retry the operator session.

If still stuck, paste:

#

openclaw qr --json
openclaw devices list
openclaw nodes status

boreal totem Apr 27, 2026, 9:00 PM

#

Z:\openclaw-main>openclaw qr --json
{
"setupCode": "eyJ1cmwiOiJ3czovLzE5Mi4xNjguMS4yMjoxODc4OSIsImJvb3RzdHJhcFRva2VuIjoid1piMkFJLW50ZHhLNlk3dFZEOEFVODlvc21iNDFfcmtWNUdVYXVyeUUxRSJ9",
"gatewayUrl": "ws://192.168.1.22:18789",
"auth": "token",
"urlSource": "gateway.bind=lan"
}

median needleBOT Apr 27, 2026, 9:01 PM

#

That QR output confirms the route: same LAN.

Advertised route is ws://192.168.1.22:18789 from gateway.bind=lan
That is valid for private LAN; no wss:// needed here.
So this is not TLS trust and not wrong advertised route.
The app status/error is exactly: Connected (operator offline)

Classification: pairing/auth, specifically the Android node side seems to reach the gateway, but the operator/UI role is not authenticated/connected.

Because the setup code includes a bootstrap token, openclaw devices list may not show a pending request if bootstrap auth succeeded. But if the operator role fell back to device pairing, it should show a pending Android/INFINIX request — likely role/operator/UI-ish. Next exact command:

openclaw devices list

If you see a pending request for that phone:

#

openclaw devices approve <requestId>

Then on Android tap Connect again.

If no pending request appears, paste these next:

openclaw devices list
openclaw nodes status

Small security note: that QR JSON contains a bootstrap token, so don’t keep reposting it publicly; regenerate/rotate after debugging if this thread is visible. Docs: https://docs.openclaw.ai/platforms/android

boreal totem Apr 27, 2026, 9:04 PM

#

Z:\openclaw-main>openclaw devices list

🦞 OpenClaw 2026.4.15 (041266a) — I don't judge, but your missing API keys are absolutely judging you.

│
◇
Paired (7)
┌──────────────────────┬────────────┬────────────────────────────────────────┬────────────┬──────────────┐
│ Device │ Roles │ Scopes │ Tokens │ IP │
├──────────────────────┼────────────┼────────────────────────────────────────┼────────────┼──────────────┤
│ Nokia │ node, │ operator.approvals, operator.read, │ node, │ 192.168.1.15 │
│ │ operator │ operator.talk.secrets, operator.write │ operator │ │
│ Nokia │ node, │ operator.approvals, operator.read, │ node, │ 192.168.1.15 │
│ │ operator │ operator.talk.secrets, operator.write │ operator │ │
│ fbffead3ac9d9eb8601b │ operator │ operator.admin, operator.read, │ operator │ │
│ 171044d0d7dfb58a0af5 │ │ operator.write, operator.approvals, │ │ │
│ f46435628b04c91486e8 │ │ operator.pairing │ │ │
│ f7a6 │ │ │ │

median needleBOT Apr 27, 2026, 9:04 PM

#

Still same LAN route, and still pairing/auth.

Exact app status/error: Connected (operator offline)

openclaw devices list result: I don’t see a Pending section, so right now it does not show a pending pairing request. That means there may be nothing to approve, or the copied output is clipped.

The odd part: I also don’t see the INFINIX/192.168.1.22 phone clearly paired as both node + operator in the visible list. The Nokia entries are paired, but that looks like a different device/IP.

Next exact command:

openclaw nodes status

If the INFINIX shows there as connected, tap Connect again in the Android final check.
If it does not show there, disconnect in the Android app and reconnect using the QR/setup code again.

boreal totem Apr 27, 2026, 9:04 PM

#

Z:\openclaw-main>openclaw nodes status

🦞 OpenClaw 2026.4.15 (041266a) — You had me at 'openclaw gateway start.'

│
◇
Known: 2 · Paired: 2 · Connected: 1
┌──────┬───────────────────────────────────────────────────┬──────────┬────────┬──────────────────┬──────┐
│ Node │ ID │ IP │ Detail │ Status │ Caps │
├──────┼───────────────────────────────────────────────────┼──────────┼────────┼──────────────────┼──────┤
│ Noki │ f104741170bcb0109e6f6665aa824bb0db313bdd5c7aedf12 │ 192.168. │ client │ paired · │ cale │
│ a │ bb38886f6eeaa05 │ 1.15 │ : │ connected (1m │ ndar │
│ │ │ │ opencl │ ago) │ , │
│ │ │ │ aw- │ │ came │
│ │ │ │ androi │ │ ra, │
│ │ │ │ d/ │ │ canv │
│ │ │ │ node │ │ as, │
│ │ │ │ · │ │ cont │
│ │ │ │ device │ │ acts │

│

median needleBOT Apr 27, 2026, 9:05 PM

#

Same LAN route confirmed.

Classification: pairing/auth, not TLS, not gateway down, not wrong address/port.

Exact app status/error: Connected (operator offline)

openclaw devices list should show a pending request only if pairing is waiting for approval. In your output it does not show Pending, so there’s nothing to approve right now.

The big clue is version/device mismatch:

Android app: 2026.4.5
Gateway/CLI: 2026.4.15
Gateway sees connected node: Nokia / 192.168.1.15
Reported phone is INFINIX, connecting to gateway at 192.168.1.22

Next exact tap: in the Android app, tap Disconnect, then reconnect by scanning a fresh QR/setup code from:

#

openclaw qr

If it still says Connected (operator offline) after reconnect, update/rebuild the Android app to match the gateway version.

boreal totem Apr 27, 2026, 9:07 PM

#

downloaded the latest version from playstore still same eroor

median needleBOT Apr 27, 2026, 9:09 PM

#

Yep — if Play Store still gives the same result, stop chasing the app version for now.

Route: same LAN (ws://192.168.1.22:18789)
Classification: pairing/auth
Exact app status/error: Connected (operator offline)

openclaw devices list should not show a pending request right now — your output showed only paired devices, no Pending section. So approval is not the next step.

I think the QR/setup-code bootstrap is getting the node side connected, but the operator/UI side isn’t getting usable auth. Try same LAN but skip QR bootstrap and use the gateway token manually.

On the gateway PC, run privately — don’t paste the output here:

openclaw config get gateway.auth.token

Then in Android:

#APP ERROR