Fault after updating to OpenClaw (2026.4.1) - LOOK !

[Denis-Liu-JB]

openclaw-logs-visible-2026-04-02-08-51-48.log.txt

After updating to latest version OpenClaw (2026.4.1), the WARN repeat showing - see the info from attached logs and the photo.

From Chatgpt:
#Identified it, the root cause is very clear:

**The culprit is not an ordinary client, but a 'OpenClawX Node' process on the local machine. **

From the real-time gateway logs, it can be seen that duplicate Warnings are of the same category:

• client=OpenClawX Node
• node v1.8.6
• remote=127.0.0.1
• ua=Dart/3.5 (dart:io)
• reason=token_missing
• closed before connect ... unauthorized: gateway token missing

What does this indicate
There is a local program that is frantically reconnecting to 'ws://127.0.0.1:18789', but * * does not include a gateway token * *, so every handshake is rejected, and then immediately retry, so the Warning keeps flashing.

One sentence positioning:
It is OpenClawX Node v1.8.6 that repeatedly connects to the gateway on the local loopback, but the authentication is not properly configured or the token is not passed. This is not an external attack, nor is it the gateway itself causing trouble.

The behavioral characteristics I confirmed from the log:
-Fixed connection source: 127.0.0.1 -Client fixed: OpenClawX Node
-Protocol Stack: Dart/3.5-Fixed reason for failure: authProvided=none / authReason=token_cissing`
-High frequency, close to * * reconnecting several times per second**

So the direct cause of the Warning is:

A local Node companion/node host component has started, but it has not received or used the gateway auth token.

---

After checking, the positioning result is very clear:

##Positioning results
The source of the Warning is:

-* * Client * *: OpenClawX Node-* * Version * *: v1.8.6 -* * Protocol Stack * *: Dart/3.5 (dart: io)
-Source Address: 127.0.0.1-Behavior: Continuously reconnecting to the gateway -* * Reason for failure * *: token_missing`

That is to say, the OpenClawX Node component on the local machine is connected to your gateway, but without a token. **

##More specifically: Where did it run
Your OpenClaw environment itself runs in the Android PRoot container, and I caught the process chain:

-Libproot. so (package name: com. nxg. openclawroot)

• openclaw
• openclaw-gateway

The abnormal client 'OpenClawX Node' in the log is also from the local loopback address of the same device, not from the external network.

So it can be basically determined that:

The OpenClawX Node Companion component configuration on the phone/local device lost the token, or took the wrong gateway address without attaching the token, so infinite retry is required. **#