Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix WhatsApp WebSocket ETIMEDOUT on connection after login [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#61788•Fetched 2026-04-08 02:54:32
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
cHaos91cHaos91
Participants
cHaos91cHaos91

Error Message

[subsystem: gateway/channels/whatsapp] [default] starting provider (+[REDACTED])
[default] channel exited: {"error":{"data":{"code":"ETIMEDOUT"},"isBoom":true,"output":{"statusCode":408,"error":"Request Time-out"}}
WebSocket error: AggregateError

The connection attempts to start, but fails within ~5 seconds with ETIMEDOUT.

Code Example

[subsystem: gateway/channels/whatsapp] [default] starting provider (+[REDACTED])
[default] channel exited: {"error":{"data":{"code":"ETIMEDOUT"},"isBoom":true,"output":{"statusCode":408,"error":"Request Time-out"}}
WebSocket error: AggregateError
RAW_BUFFERClick to expand / collapse

Describe the bug

After successfully pairing WhatsApp via QR code, the WebSocket connection to WhatsApp servers fails with ETIMEDOUT immediately after the gateway starts. The provider starts but the channel exits within seconds with WebSocket timeout error.

Environment

  • OpenClaw Version: 2026.4.5
  • Node.js: v22.22.1
  • OS: Linux x86_64 (Intel Core i7-3630QM)
  • Channel: WhatsApp Web

Logs

[subsystem: gateway/channels/whatsapp] [default] starting provider (+[REDACTED])
[default] channel exited: {"error":{"data":{"code":"ETIMEDOUT"},"isBoom":true,"output":{"statusCode":408,"error":"Request Time-out"}}
WebSocket error: AggregateError

The connection attempts to start, but fails within ~5 seconds with ETIMEDOUT.

Steps to reproduce

  1. Run openclaw channels login --channel whatsapp
  2. Scan QR code with WhatsApp
  3. Credentials are created successfully
  4. Restart gateway
  5. Observe WebSocket timeout in logs

Expected behavior

After successful QR scan and credential creation, WhatsApp should connect and remain connected.

Additional context

  • Network connectivity to WhatsApp is confirmed (curl to web.whatsapp.com returns 200)
  • Not using Tailscale exit node (direct internet connection via local gateway)
  • Same issue occurred with previous credentials (401 Unauthorized after ~6 seconds)
  • Issue persists across gateway restarts
  • Credentials file is created (~1726 bytes) but WebSocket fails to establish connection
  • Gateway shows "starting provider" but then channel exits with ETIMEDOUT

Related

  • Issue #60136 - Credentials corruption during pre-key rotation (different issue)
  • Issue #58481 - WebSocket drops on WSL2 (TCP keepalive issue)

Frequency

Consistent - happens every time after pairing, regardless of credentials being present.

extent analysis

TL;DR

The WebSocket connection to WhatsApp servers fails with ETIMEDOUT immediately after the gateway starts, suggesting a potential issue with the connection timeout or the WhatsApp server's response time.

Guidance

  • Verify the network connectivity to WhatsApp servers using tools like curl or wget to ensure there are no issues with the internet connection.
  • Check the WhatsApp server status to see if there are any known issues or outages that could be causing the timeout.
  • Review the OpenClaw configuration to see if there are any settings that can be adjusted to increase the WebSocket connection timeout.
  • Investigate the possibility of a firewall or proxy issue that could be blocking or slowing down the WebSocket connection.

Example

No specific code snippet can be provided without more information about the OpenClaw configuration and implementation.

Notes

The issue seems to be related to the WebSocket connection, but the root cause is still unclear. Further investigation is needed to determine if the issue is with the OpenClaw implementation, the WhatsApp server, or the network connectivity.

Recommendation

Apply workaround: Increase the WebSocket connection timeout in the OpenClaw configuration, if possible, to see if it resolves the issue. This could help determine if the issue is related to the timeout value.

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

After successful QR scan and credential creation, WhatsApp should connect and remain connected.

#SSR setup#ISR setup#authentication setup#request error#file not found

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 WhatsApp WebSocket ETIMEDOUT on connection after login [1 participants]