[!] ERROR: Could not connect to server

[cers000]

Please input the correct endpoint: ws://127.0.0.1:32123/ws
auth_token: UbKDq5LKlzcZgxhZw9w5mKZsq
enter_auth_pin: 123456

The gateway is now open.
nullclaw gateway runtime started
  Gateway:  http://127.0.0.1:3000
  Components: 3 active
  Model:    deepseek/deepseek-v3.2-251201
  Provider: custom:https://openai.qiniu.com/v1
  Ctrl+C to stop

Gateway listening on 127.0.0.1:3000
info(memory): memory plan resolved: backend=sqlite retrieval=Gateway pairing code: 166601
keyword vector=none rollout=off hygiene=true snapshot=false cache=false semantic_cache=false summarizer=false sources=1
info(web): Web channel auth token loaded from channels.web auth_token
info(web): Web UI JWT signing key loaded from persisted store
info(web): Web local pairing code active (fixed): 123456
info(web): Web channel ready on ws://127.0.0.1:32123/ws
info(web): Web channel optional upgrade auth token active (hidden in logs)
info(channel_manager): web gateway started
info(websocket): starting blocking worker to listen on 127.0.0.1:32123
warning(websocket): (127.0.0.1:4844) handshake error reading from socket: error.Unexpected

But still prompts:[!] ERROR: Could not connect to server
nullclaw ：warning(websocket): (127.0.0.1:4860) handshake error reading from socket: error.Unexpected
Win10 64bit
bun.js

[mugenyume]

I’d love to know what steps you took to reach this point—I’ve tried many different approaches, but I’m still encountering the same issue. Sharing your process might help me identify a potential fix.

[cers000]

I’d love to know what steps you took to reach this point—I’ve tried many different approaches, but I’m still encountering the same issue. Sharing your process might help me identify a potential fix.

I have identified the issue. It is unrelated to nullclaw-chat-ui; rather, it is a problem with the websocket package used by nullclaw. On the Windows system, this package references an incorrect API for network connectivity, which causes it to continuously fail when attempting to establish the websocket connection.
nullclaw/issues#317