Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Many error gateway connect failed: Error: gateway closed (1000): in release 2026.5.5 [2 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#78394•Fetched 2026-05-07 03:37:26
View on GitHub
Comments
2
Participants
2
Timeline
11
Reactions
2
Author
najef1979-codenajef1979-code
Participants
clawsweeper[bot]clawsweeper[bot]najef1979-codenajef1979-code
Timeline (top)
mentioned ×3subscribed ×3commented ×2labeled ×2

Just updated to 5.5 and directly had a lot or gateway errors. error gateway connect failed: Error: gateway closed (1000):

Error Message

09:26:01+00:00 warn gateway/ws {"subsystem":"gateway/ws"} handshake timeout conn=97a00c8a-1174-4074-bca0-043b8aba4c74 peer=127.0.0.1:33386->127.0.0.1:18789 remote=127.0.0.1 09:26:02+00:00 error gateway connect failed: Error: gateway closed (1000): 09:26:02+00:00 error gateway connect failed: Error: gateway closed (1000): gateway connect failed: Error: gateway closed (1000): 09:26:02+00:00 warn gateway/ws {"subsystem":"gateway/ws"} {"cause":"handshake-timeout","handshake":"failed","durationMs":19899,"lastFrameType":"req","lastFrameMethod":"connect","lastFrameId":"600cb1b1-52ca-4b4b-803a-d5f0a9e57489","host":"127.0.0.1:18789","remoteAddr":"127.0.0.1","remotePort":33386,"localAddr":"127.0.0.1","localPort":18789,"endpoint":"127.0.0.1:33386->127.0.0.1:18789","handshakeMs":19515} closed before connect conn=97a00c8a-1174-4074-bca0-043b8aba4c74 peer=127.0.0.1:33386->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=n/a host=127.0.0.1:18789 ua=n/a code=1000 reason=n/a

09:25:39+00:00 info gateway/ws {"subsystem":"gateway/ws"} ⇄ res ✓ node.list 52624ms conn=08657951…7416 id=60c46455…2c78 gateway connect failed: Error: gateway closed (1000): 09:25:40+00:00 warn gateway/ws {"subsystem":"gateway/ws"} {"handshake":"pending","durationMs":1200,"lastFrameType":"req","lastFrameMethod":"connect","lastFrameId":"831253f5-6d7c-4f85-8530-895a5a1858ea","host":"127.0.0.1:18789","remoteAddr":"127.0.0.1","remotePort":44008,"localAddr":"127.0.0.1","localPort":18789,"endpoint":"127.0.0.1:44008->127.0.0.1:18789"} closed before connect conn=8488fa66-fa81-4e95-bd2f-9b26d3a03666 peer=127.0.0.1:44008->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=n/a host=127.0.0.1:18789 ua=n/a code=1005 reason=n/a

Root Cause

Just updated to 5.5 and directly had a lot or gateway errors. error gateway connect failed: Error: gateway closed (1000):

Fix Action

Fix / Workaround

upgrade to 5.5 and check logs.

Code Example

09:26:01+00:00 warn gateway/ws {"subsystem":"gateway/ws"} handshake timeout conn=97a00c8a-1174-4074-bca0-043b8aba4c74 peer=127.0.0.1:33386->127.0.0.1:18789 remote=127.0.0.1
09:26:02+00:00 error gateway connect failed: Error: gateway closed (1000):
09:26:02+00:00 error gateway connect failed: Error: gateway closed (1000):
gateway connect failed: Error: gateway closed (1000):
09:26:02+00:00 warn gateway/ws {"subsystem":"gateway/ws"} {"cause":"handshake-timeout","handshake":"failed","durationMs":19899,"lastFrameType":"req","lastFrameMethod":"connect","lastFrameId":"600cb1b1-52ca-4b4b-803a-d5f0a9e57489","host":"127.0.0.1:18789","remoteAddr":"127.0.0.1","remotePort":33386,"localAddr":"127.0.0.1","localPort":18789,"endpoint":"127.0.0.1:33386->127.0.0.1:18789","handshakeMs":19515} closed before connect conn=97a00c8a-1174-4074-bca0-043b8aba4c74 peer=127.0.0.1:33386->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=n/a host=127.0.0.1:18789 ua=n/a code=1000 reason=n/a


09:25:39+00:00 info gateway/ws {"subsystem":"gateway/ws"} ⇄ res ✓ node.list 52624ms conn=08657951…7416 id=60c46455…2c78
gateway connect failed: Error: gateway closed (1000):
09:25:40+00:00 warn gateway/ws {"subsystem":"gateway/ws"} {"handshake":"pending","durationMs":1200,"lastFrameType":"req","lastFrameMethod":"connect","lastFrameId":"831253f5-6d7c-4f85-8530-895a5a1858ea","host":"127.0.0.1:18789","remoteAddr":"127.0.0.1","remotePort":44008,"localAddr":"127.0.0.1","localPort":18789,"endpoint":"127.0.0.1:44008->127.0.0.1:18789"} closed before connect conn=8488fa66-fa81-4e95-bd2f-9b26d3a03666 peer=127.0.0.1:44008->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=n/a host=127.0.0.1:18789 ua=n/a code=1005 reason=n/a
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Just updated to 5.5 and directly had a lot or gateway errors. error gateway connect failed: Error: gateway closed (1000):

Steps to reproduce

upgrade to 5.5 and check logs.

Expected behavior

no errors and not so many errors

Actual behavior

many errors

OpenClaw version

2026.5.5

Operating system

Ubuntu

Install method

Script

Model

minimax

Provider / routing chain

minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

09:26:01+00:00 warn gateway/ws {"subsystem":"gateway/ws"} handshake timeout conn=97a00c8a-1174-4074-bca0-043b8aba4c74 peer=127.0.0.1:33386->127.0.0.1:18789 remote=127.0.0.1
09:26:02+00:00 error gateway connect failed: Error: gateway closed (1000):
09:26:02+00:00 error gateway connect failed: Error: gateway closed (1000):
gateway connect failed: Error: gateway closed (1000):
09:26:02+00:00 warn gateway/ws {"subsystem":"gateway/ws"} {"cause":"handshake-timeout","handshake":"failed","durationMs":19899,"lastFrameType":"req","lastFrameMethod":"connect","lastFrameId":"600cb1b1-52ca-4b4b-803a-d5f0a9e57489","host":"127.0.0.1:18789","remoteAddr":"127.0.0.1","remotePort":33386,"localAddr":"127.0.0.1","localPort":18789,"endpoint":"127.0.0.1:33386->127.0.0.1:18789","handshakeMs":19515} closed before connect conn=97a00c8a-1174-4074-bca0-043b8aba4c74 peer=127.0.0.1:33386->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=n/a host=127.0.0.1:18789 ua=n/a code=1000 reason=n/a


09:25:39+00:00 info gateway/ws {"subsystem":"gateway/ws"} ⇄ res ✓ node.list 52624ms conn=08657951…7416 id=60c46455…2c78
gateway connect failed: Error: gateway closed (1000):
09:25:40+00:00 warn gateway/ws {"subsystem":"gateway/ws"} {"handshake":"pending","durationMs":1200,"lastFrameType":"req","lastFrameMethod":"connect","lastFrameId":"831253f5-6d7c-4f85-8530-895a5a1858ea","host":"127.0.0.1:18789","remoteAddr":"127.0.0.1","remotePort":44008,"localAddr":"127.0.0.1","localPort":18789,"endpoint":"127.0.0.1:44008->127.0.0.1:18789"} closed before connect conn=8488fa66-fa81-4e95-bd2f-9b26d3a03666 peer=127.0.0.1:44008->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=n/a host=127.0.0.1:18789 ua=n/a code=1005 reason=n/a

Impact and severity

openclaw feels slugish and slow,, not sure if its related to this or not.

Additional information

No response

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

no errors and not so many errors

#search optimization#API routing#API middleware#SSR setup#ISR setup

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 [Bug]: Many error gateway connect failed: Error: gateway closed (1000): in release 2026.5.5 [2 comments, 2 participants]