Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Browser relay extension server not starting (port 18792) [1 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#72727•Fetched 2026-04-28 06:32:54
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
BloxRE12BloxRE12
Participants
BloxRE12BloxRE12

Error Message

  1. Extension shows error: "Relay not reachable/authenticated at http://127.0.0.1:18792/"
  • Error message suggests relay server is not running

Root Cause

Issue

The OpenClaw browser relay extension cannot connect because the relay server (expected on port 18792) is not starting.

Fix Action

Workaround

Currently using REST API for WordPress control instead of browser extension.

RAW_BUFFERClick to expand / collapse

Bug Report: Browser Relay Extension Server Not Starting

Issue

The OpenClaw browser relay extension cannot connect because the relay server (expected on port 18792) is not starting.

Environment

  • OpenClaw Version: 2026.4.24 (cbcfdf6)
  • OS: macOS 26.3.1 (arm64)
  • Node: v25.6.1
  • Gateway Port: 18789 (running ✓)
  • Expected Relay Port: 18792 (not running ✗)

Steps to Reproduce

  1. Install OpenClaw Chrome extension
  2. Configure with gateway port 18789 and token
  3. Extension shows error: "Relay not reachable/authenticated at http://127.0.0.1:18792/"
  4. Check ports: lsof -i :18792 shows no process listening

Expected Behavior

  • Browser relay server should start on port 18792 (gateway port + 3)
  • Extension should connect successfully
  • User can control browser via extension

Actual Behavior

  • No process listening on port 18792
  • Extension cannot connect
  • Error message suggests relay server is not running

Additional Info

  • Gateway is running correctly on port 18789
  • Browser is running on CDP port 18800
  • No openclaw browser relay command exists
  • No relay configuration found in openclaw browser --help
  • Extension documentation assumes relay server exists

Workaround

Currently using REST API for WordPress control instead of browser extension.

Request

Please implement the browser relay server component or update extension documentation if this feature is not yet available.

extent analysis

TL;DR

The browser relay server is not starting on port 18792, and the extension cannot connect, suggesting a potential issue with the OpenClaw configuration or the relay server implementation.

Guidance

  • Verify that the OpenClaw version 2026.4.24 supports the browser relay server feature, as the documentation and --help output do not mention it.
  • Check the system logs for any errors related to the OpenClaw browser relay server to determine if it's attempting to start but failing.
  • Investigate alternative configuration options or environment variables that might enable the relay server, as the openclaw browser --help output does not provide clear guidance.
  • Consider reaching out to the OpenClaw development team or community for further assistance, as the issue may be related to a missing or incomplete feature.

Notes

The provided information suggests that the browser relay server feature may not be fully implemented or documented in the current version of OpenClaw, which could be the root cause of the issue.

Recommendation

Apply workaround: Continue using the REST API for WordPress control until the browser relay server feature is implemented or further guidance is provided by the OpenClaw development team.

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…
#api#output truncation#response parsing#generation error#database connection

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Browser relay extension server not starting (port 18792) [1 participants]