Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: WebSocket Gateway Probe Timeout on Loopback [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#48936•Fetched 2026-04-08 00:50:49
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
utzaagentutzaagent
Participants
RyceRyceutzaagentutzaagent
Timeline (top)
labeled ×2commented ×1subscribed ×1

Running openclaw gateway probe returns "Connect: failed - timeout" even though the gateway is fully functional (HTTP works, WebSocket connections work). Environment:

OpenClaw: 2026.3.13 OS: Linux 6.12.62+rpt-rpi-2712 (arm64) - Raspberry Pi 5 Gateway: loopback (127.0.0.1:18789) Steps to reproduce:

Root Cause

Running openclaw gateway probe returns "Connect: failed - timeout" even though the gateway is fully functional (HTTP works, WebSocket connections work). Environment:

OpenClaw: 2026.3.13 OS: Linux 6.12.62+rpt-rpi-2712 (arm64) - Raspberry Pi 5 Gateway: loopback (127.0.0.1:18789) Steps to reproduce:

Code Example

handshake timeout conn=... remote=127.0.0.1
closed before connect ... cause: handshake-timeout
durationMs: 3445, handshakeMs: 3002
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

Running openclaw gateway probe returns "Connect: failed - timeout" even though the gateway is fully functional (HTTP works, WebSocket connections work). Environment:

OpenClaw: 2026.3.13 OS: Linux 6.12.62+rpt-rpi-2712 (arm64) - Raspberry Pi 5 Gateway: loopback (127.0.0.1:18789) Steps to reproduce:

Steps to reproduce

Steps to reproduce:

Run openclaw gateway probe Observe: "Connect: failed - timeout" But HTTP works: curl http://127.0.0.1:18789/ returns 200

Expected behavior

Probe should succeed since gateway is functional

Actual behavior

Timeout despite gateway being reachable via HTTP and WebSocket actually working

OpenClaw version

OpenClaw: 2026.3.13

Operating system

OS: Linux 6.12.62+rpt-rpi-2712 (arm64) - Raspberry Pi 5

Install method

No response

Model

openrouter/minimax/minimax-m2.5

Provider / routing chain

Gateway: loopback (127.0.0.1:18789)

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

handshake timeout conn=... remote=127.0.0.1
closed before connect ... cause: handshake-timeout
durationMs: 3445, handshakeMs: 3002

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

The fix involves increasing the handshake timeout in the OpenClaw configuration to allow for more time to establish a connection.

Steps to Apply the Fix

  • Locate the OpenClaw configuration file.
  • Add or modify the handshake_timeout setting to increase the timeout value. For example:
# OpenClaw configuration file
handshake_timeout: 6000  # Increase timeout to 6 seconds

Alternatively, if the configuration is set via environment variables or command-line flags, adjust the corresponding value. For instance:

# Example command-line flag
openclaw --handshake-timeout 6000
  • Restart the OpenClaw service to apply the changes.

Verification

To verify the fix, run the OpenClaw gateway probe again and check for a successful connection:

# Run the probe
openclaw gateway probe

If the handshake timeout issue is resolved, the probe should succeed without reporting a timeout error.

Extra Tips

  • Monitor the OpenClaw logs to ensure the increased timeout resolves the issue without introducing other problems.
  • Consider adjusting the timeout value based on the specific requirements of your environment and the performance characteristics of your gateway.

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

Probe should succeed since gateway is functional

#api#ssr#installation#tensor shape#autograd error#memory optimization#batch processing#GPU compatibility#latency issue#model loading

Still need to ship something?

×6

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

Back to top recommendations

TRENDING