openclaw - 💡(How to fix) Fix [Bug]: Gateway connection closes with status 408 during WhatsApp session [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#77795Fetched 2026-05-06 06:21:20
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
2
Timeline (top)
commented ×2labeled ×2

The gateway loses its WhatsApp web connection and closes with status 408 (Request Time-out) during runtime.

Root Cause

The gateway loses its WhatsApp web connection and closes with status 408 (Request Time-out) during runtime.

Fix Action

Fix / Workaround

Additional provider/model setup details

12:20:23 [ws] ⇄ res ✓ sessions.list 454ms conn=<redacted> id=<redacted> 12:20:39 [whatsapp] Web connection closed (status 408). Retry 1/12 in 2.3s… (status=408 Request Time-out Connection was lost) 12:20:39 [ws] webchat disconnected code=1001 reason=n/a conn=<redacted> 12:20:39 [agent/embedded] [trace:embedded-run] startup stages: runId=<redacted> sessionId=<redacted> phase=attempt-dispatch totalMs=6546 stages=workspace:1ms@1ms,runtime-plugins:7ms@8ms,hooks:0ms@8ms,model-resolution:6515ms@6523ms,auth:3ms@6526ms,context-engine:1ms@6527ms,attempt-dispatch:19ms@6546ms 12:20:42 [tools] tools.profile (full) allowlist contains unknown entries (ollama_web_search, ollama_web_fetch). These entries won't match any tool unless the plugin is enabled. 12:20:42 [tools] tools.allow allowlist contains unknown entries (ollama_web_search, ollama_web_fetch). These entries won't match any tool unless the plugin is enabled. 12:20:42 [diagnostic] liveness warning: reasons=event_loop_delay interval=30s eventLoopDelayP99Ms=1055.4 eventLoopDelayMaxMs=8350.9 eventLoopUtilization=0.698 cpuCoreRatio=0.697 active=1 waiting=0 queued=1 phase=channels.whatsapp.start-account recentPhases=sidecars.subagent-recovery:6ms,sidecars.main-session-recovery:11ms,post-attach.update-sentinel:0ms,sidecars.session-locks:1545ms,sidecars.model-prewarm:2285ms,post-ready.maintenance:569ms work=[active=agent:main:whatsapp:direct:<redacted>(processing,q=1,age=20s) queued=agent:main:whatsapp:direct:<redacted>(processing,q=1,age=20s)] 12:20:45 [whatsapp] Listening for personal WhatsApp inbound messages.

Code Example

12:20:39 [whatsapp] Web connection closed (status 408). Retry 1/12 in 2.3s…
12:20:39 [ws] webchat disconnected code=1001 reason=n/a
12:20:45 [whatsapp] Listening for personal WhatsApp inbound messages.
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

The gateway loses its WhatsApp web connection and closes with status 408 (Request Time-out) during runtime.

Steps to reproduce

openclaw gateway run Start the gateway Wait for WhatsApp provider to initialize Observe runtime logs

Expected behavior

Gateway must run and continue without closing

Actual behavior

[whatsapp] Web connection closed (status 408). Retry 1/12 in 2.3s… (status=408 Request Time-out Connection was lost) [ws] webchat disconnected code=1001 reason=n/a

OpenClaw version

OpenClaw 2026.5.4 (325df3e)

Operating system

windows 11

Install method

default windows

Model

Deepseek

Provider / routing chain

opencode

Additional provider/model setup details

12:20:23 [ws] ⇄ res ✓ sessions.list 454ms conn=<redacted> id=<redacted> 12:20:39 [whatsapp] Web connection closed (status 408). Retry 1/12 in 2.3s… (status=408 Request Time-out Connection was lost) 12:20:39 [ws] webchat disconnected code=1001 reason=n/a conn=<redacted> 12:20:39 [agent/embedded] [trace:embedded-run] startup stages: runId=<redacted> sessionId=<redacted> phase=attempt-dispatch totalMs=6546 stages=workspace:1ms@1ms,runtime-plugins:7ms@8ms,hooks:0ms@8ms,model-resolution:6515ms@6523ms,auth:3ms@6526ms,context-engine:1ms@6527ms,attempt-dispatch:19ms@6546ms 12:20:42 [tools] tools.profile (full) allowlist contains unknown entries (ollama_web_search, ollama_web_fetch). These entries won't match any tool unless the plugin is enabled. 12:20:42 [tools] tools.allow allowlist contains unknown entries (ollama_web_search, ollama_web_fetch). These entries won't match any tool unless the plugin is enabled. 12:20:42 [diagnostic] liveness warning: reasons=event_loop_delay interval=30s eventLoopDelayP99Ms=1055.4 eventLoopDelayMaxMs=8350.9 eventLoopUtilization=0.698 cpuCoreRatio=0.697 active=1 waiting=0 queued=1 phase=channels.whatsapp.start-account recentPhases=sidecars.subagent-recovery:6ms,sidecars.main-session-recovery:11ms,post-attach.update-sentinel:0ms,sidecars.session-locks:1545ms,sidecars.model-prewarm:2285ms,post-ready.maintenance:569ms work=[active=agent:main:whatsapp:direct:<redacted>(processing,q=1,age=20s) queued=agent:main:whatsapp:direct:<redacted>(processing,q=1,age=20s)] 12:20:45 [whatsapp] Listening for personal WhatsApp inbound messages.

Logs, screenshots, and evidence

12:20:39 [whatsapp] Web connection closed (status 408). Retry 1/12 in 2.3s…
12:20:39 [ws] webchat disconnected code=1001 reason=n/a
12:20:45 [whatsapp] Listening for personal WhatsApp inbound messages.

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The gateway's WhatsApp web connection is closing due to a request timeout, which may be caused by a network issue or a problem with the WhatsApp provider.

Guidance

  • Verify the network connection and check for any issues that could be causing the request timeout.
  • Investigate the WhatsApp provider's status and check for any known issues or outages.
  • Check the OpenClaw gateway logs for any other error messages that may indicate the cause of the problem.
  • Consider increasing the timeout value or implementing a retry mechanism to handle temporary connection issues.

Example

No code snippet is provided as the issue seems to be related to a network or provider issue rather than a code problem.

Notes

The issue may be specific to the WhatsApp provider or the network connection, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Increase the timeout value or implement a retry mechanism to handle temporary connection issues, as the root cause of the problem is unclear and may be related to external factors.

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

Gateway must run and continue without closing

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]: Gateway connection closes with status 408 during WhatsApp session [2 comments, 2 participants]