Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: 4.26 version cutdown connection to local model in few minites [1 pull requests, 4 comments, 4 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#74078•Fetched 2026-04-30 06:28:49
View on GitHub
Comments
4
Participants
4
Timeline
18
Reactions
0
Author
sakalaboatorsakalaboator
Participants
caikun2018caikun2018clawsweeper[bot]clawsweeper[bot]sakalaboatorsakalaboatorwoshicbywoshicby
Timeline (top)
cross-referenced ×6commented ×4mentioned ×3subscribed ×3

After upgrade to 426. The task will hang and the connection to LLM local model seems be cut off.

Error Message

error: gateway connect failed: Error: gateway closed (1000):

Root Cause

After upgrade to 426. The task will hang and the connection to LLM local model seems be cut off.

Fix Action

Fix / Workaround

After upgrade to 426. The task will hang and the connection to LLM local model seems be cut off.

PR fix notes

PR #74184: fix: Found two low-severity regressions: the focused CLI log test file

Description (problem / solution / changelog)

Summary

Found two low-severity regressions: the focused CLI log test file now fails, and the changelog gained a duplicate entry.

What Clownfish Is Fixing

  • Low: Existing fallback tests still assert the old notice text (regression)
    • File: src/cli/logs-cli.test.ts:158
    • Evidence: src/cli/logs-cli.ts:52 now emits Local Gateway RPC unavailable; reading configured file log instead., but the pairing-required and scope-upgrade tests still assert reading local log file instead at src/cli/logs-cli.test.ts:158 and src/cli/logs-cli.test.ts:181. Running pnpm test src/cli/logs-cli.test.ts fails exactly those two assertions.
    • Impact: the focused CLI test lane is red for this commit, so changed-gate/CI will fail even though the runtime fallback behavior appears to execute.
    • Suggested fix: update the two stale expectations to the new notice text, or keep a shared expected notice constant so future copy changes do not split tests from implementation.
    • Confidence: high
  • Low: Changelog entry is duplicated (bug)
    • File: CHANGELOG.md:18
    • Evidence: the same MCP/plugins: stringify non-array plugin tool results... Thanks @vincentkoc. bullet appears at CHANGELOG.md:18 and CHANGELOG.md:20; the diff for this commit adds one copy while leaving the existing copy in place.
    • Impact: unreleased notes now duplicate an unrelated fix, which can confuse release-note output and changelog audit/dedupe tooling.
    • Suggested fix: remove one of the duplicate MCP/plugins bullets and keep the new CLI/logs entry.
    • Confidence: high

Expected Repair Surface

  • src/cli/logs-cli.test.ts
  • src/cli/logs-cli.ts

Source And Review Context

Expected validation

  • pnpm check:changed

ClawSweeper already ran:

  • pnpm docs:list: completed.
  • pnpm test src/cli/logs-cli.test.ts: initially blocked because node_modules was missing.
  • pnpm install: completed; no tracked changes.
  • pnpm test src/cli/logs-cli.test.ts: failed 2 tests, 13 passed.
  • git diff --check 6306e2f..e25b542: passed.

Known review limits:

  • I did not run the broad changed gate because the focused touched test file already fails with a concrete regression.

Clownfish Guardrails

  • Re-check the finding against latest main before changing code.
  • Keep the patch to the narrowest behavior change and matching regression coverage.
  • Do not merge automatically; this PR stays for maintainer review.

Clownfish 🐠 replacement reef notes:

  • Cluster: clawsweeper-commit-openclaw-openclaw-e25b54210097
  • Source PRs: none
  • Credit: Detected by ClawSweeper commit review for e25b54210097bf373004ede6e780dfeee59f6523.; Original commit author: Peter Steinberger.
  • Validation: pnpm check:changed

fish notes: model gpt-5.5, reasoning xhigh; reviewed against 91d0bdac36ea.

Changed files

  • src/cli/logs-cli.test.ts (modified, +5/-5)
  • src/cli/logs-cli.ts (modified, +2/-1)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrade to 426. The task will hang and the connection to LLM local model seems be cut off.

Steps to reproduce

The task will hang down and the connection to LLM local model(ollama) seems be cut off. The same configuration will run OK in former version.

Expected behavior

The task will hang down and the connection to LLM local model(ollama) seems be cut off. The same configuration and workflow run OK in former version.

Actual behavior

The task will hang down and the connection to LLM local model(ollama) seems be cut off. The same configuration and workflow run OK in former version. And I can not run openclaw logs.

error:

🦞 OpenClaw 2026.4.26 (be8c246) — Self-hosted, self-updating, self-aware (just kidding... unless?).

│ gateway connect failed: Error: gateway closed (1000): ◇
Gateway not reachable. Is it running and accessible? Gateway target: ws://127.0.0.1:18789 Source: local loopback Config: /home/burkro/.openclaw/openclaw.json Bind: lan

OpenClaw version

2026.4.26

Operating system

ubuntu 24.04

Install method

npm

Model

local

Provider / routing chain

local

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The task hanging and connection to the LLM local model being cut off after the upgrade to version 426 may be resolved by checking the gateway configuration and ensuring it is running and accessible.

Guidance

  • Verify that the gateway is running and listening on the specified port (18789) by checking the OpenClaw configuration file (/home/burkro/.openclaw/openclaw.json) and the system's network settings.
  • Check the system logs for any error messages related to the gateway or OpenClaw to gain more insight into the issue.
  • Ensure that the ws://127.0.0.1:18789 endpoint is reachable and not blocked by any firewall or network configuration.
  • Try running the OpenClaw logs again to see if any additional error messages are produced that can help diagnose the issue.

Example

No code snippet is provided as the issue does not contain sufficient information to create a relevant example.

Notes

The issue may be related to a configuration change or a bug introduced in the new version of OpenClaw. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Check the gateway configuration and ensure it is running and accessible, as this is the most likely cause of the issue based on the provided error message.

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

The task will hang down and the connection to LLM local model(ollama) seems be cut off. The same configuration and workflow run OK in former version.

#authentication setup#request error#file not found#serialization error#model 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

openclaw - ✅(Solved) Fix [Bug]: 4.26 version cutdown connection to local model in few minites [1 pull requests, 4 comments, 4 participants]