Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Control UI on local loopback (127.0.0.1) still requires pairing in 2026.3.13, despite docs saying local connections auto-approve [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#51474•Fetched 2026-04-08 01:10:44
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
tothdbexectothdbexec
Participants
Hollychou924Hollychou924tothdbexectothdbexec
Timeline (top)
labeled ×2commented ×1

Control UI on local loopback (127.0.0.1) is still requiring pairing in 2026.3.13, even though the docs say local connections are auto-approved.

Root Cause

Control UI on local loopback (127.0.0.1) is still requiring pairing in 2026.3.13, even though the docs say local connections are auto-approved.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

Control UI on local loopback (127.0.0.1) is still requiring pairing in 2026.3.13, even though the docs say local connections are auto-approved.

Steps to reproduce

  1. Start the gateway locally with gateway.mode=local, gateway.bind=loopback, and token auth enabled.
    2. Run openclaw dashboard --no-open.
    3. Open the printed URL in Firefox on the same machine, using http://127.0.0.1:18789/#token=....
    4. Observe that the Control UI does not connect and reports pairing required.
    5. Run the gateway in foreground with openclaw gateway run --verbose --ws-log full.
    6. Repeat step 3 and observe websocket close logs with cause=pairing-required and code=4008.

Expected behavior

Docs for Control UI say local connections (127.0.0.1) are auto-approved, and only remote connections require explicit pairing approval.

Actual behavior

The browser Control UI repeatedly fails websocket connect with pairing required.

Observed in gateway logs:

  • cause=pairing-required
  • code=4008
  • reason=connect failed
  • local origin: http://127.0.0.1:18789

Example log lines:

  • closed before connect ... origin=http://127.0.0.1:18789 ... code=4008 reason=connect failed
  • → close code=4008 reason=connect failed durationMs=190 cause=pairing-required handshake=failed ...

Full example from foreground run:

  • 07:17:00 [ws] ← open remoteAddr=127.0.0.1 conn=97efe1ff…1d81
  • 07:17:01 [ws] closed before connect conn=97efe1ff-e4e3-4ed0-be0f-f786cd0e1d81 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 (X11; Ubuntu; Linux x86_64; rv:147.0) Gecko/20100101 Firefox/147.0 code=4008 reason=connect failed
  • 07:17:01 [ws] → close code=4008 reason=connect failed durationMs=190 cause=pairing-required handshake=failed lastFrameType=req lastFrameMethod=connect lastFrameId=19519d18-06e9-442d-b686-11894c69d93f conn=97efe1ff…1d81

OpenClaw version

OpenClaw 2026.3.13 (61d171a)

Operating system

OS: Ubuntu Linux

Install method

npm (global install)

Model

openai-codex/gpt-5.4

Provider / routing chain

OpenClaw Control UI → local Gateway (token auth, loopback) → openai-codex/gpt-5.4

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To resolve the issue of the Control UI requiring pairing on local loopback connections, we need to update the gateway configuration to auto-approve local connections.

Here are the steps:

  • Update the gateway.config.js file to include the following configuration:
module.exports = {
  // ... other configurations ...
  autoApproveLocalConnections: true,
};

Alternatively, you can pass the configuration as a command-line argument when starting the gateway:

openclaw gateway run --verbose --ws-log full --auto-approve-local-connections
  • Ensure that the gateway.mode is set to local and gateway.bind is set to loopback:
openclaw gateway run --mode local --bind loopback
  • Restart the gateway and retry the connection.

Verification

To verify that the fix worked, follow these steps:

  • Start the gateway with the updated configuration.
  • Open the Control UI in the browser using the printed URL.
  • Check that the Control UI connects successfully without requiring pairing.

Extra Tips

  • Make sure to update the OpenClaw version to the latest available to ensure you have the latest fixes and features.
  • If you continue to experience issues, check the gateway logs for any error messages that may indicate the cause of the problem.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Docs for Control UI say local connections (127.0.0.1) are auto-approved, and only remote connections require explicit pairing approval.

#api#ssr#installation#tensor shape#autograd error#docker error#permission error#memory optimization#batch processing#GPU compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING