Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Feishu @larksuiteoapi/node-sdk axios timeout from gateway process (Alibaba Cloud ECS / Node.js 24) [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#72721•Fetched 2026-04-28 06:32:57
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
sign-2025sign-2025
Participants
sign-2025sign-2025

When the OpenClaw Gateway starts with Feishu channel enabled in websocket connection mode, the @larksuiteoapi/node-sdk embedded axios calls to Feishu API (open.feishu.cn) consistently timeout after 10 seconds. However, native Node.js https.request works perfectly (577ms).

This appears to be an interaction between the bundled axios (used internally by @larksuiteoapi/node-sdk) and the gateway process environment on Alibaba Cloud ECS with Node.js 24.

Root Cause

Root Cause (Suspected)

Fix Action

Workaround

Switch Feishu channel to webhook mode:

{"channels": {"feishu": {"connectionMode": "webhook", ...}}}

Configure Feishu Open Platform to POST events to your gateway endpoint instead.

Code Example

{"channels": {"feishu": {"connectionMode": "webhook", ...}}}
RAW_BUFFERClick to expand / collapse

Description

When the OpenClaw Gateway starts with Feishu channel enabled in websocket connection mode, the @larksuiteoapi/node-sdk embedded axios calls to Feishu API (open.feishu.cn) consistently timeout after 10 seconds. However, native Node.js https.request works perfectly (577ms).

This appears to be an interaction between the bundled axios (used internally by @larksuiteoapi/node-sdk) and the gateway process environment on Alibaba Cloud ECS with Node.js 24.

Reproduction

  1. Configure Feishu channel in openclaw.json with connectionMode: "websocket"
  2. Start gateway: node dist/index.js gateway --port 14720
  3. Gateway logs show plugins booting, then feishu plugin hangs on connection
  4. After 10s timeout: AxiosError: timeout of 10000ms exceeded POST https://open.feishu.cn/open-apis/bot/v1/openclaw_bot/ping

Diagnostic Results

TestResult
Shell curl to Feishu API✅ 630ms success
Node.js https.request to Feishu auth endpoint✅ 577ms success
Same axios call from gateway child process❌ 10s timeout
DNS resolution✅ 3ms, correct IP
IPv4 connectivity✅ Alibaba Cloud internal DNS (100.100.2.136) works
Firewall✅ iptables OUTPUT ACCEPT

Root Cause (Suspected)

@larksuiteoapi/node-sdk uses an embedded axios instance with connection pooling / keepAlive configuration that behaves differently inside the gateway's child process environment. On Alibaba Cloud ECS with Node.js 24.14.0, outbound HTTPS from the gateway process via axios hangs, while native https.request works fine.

Workaround

Switch Feishu channel to webhook mode:

{"channels": {"feishu": {"connectionMode": "webhook", ...}}}

Configure Feishu Open Platform to POST events to your gateway endpoint instead.

Environment

  • Node.js: v24.14.0
  • OS: Alibaba Cloud Linux 3
  • openclaw: 2026.4.24 (cbcfdf6)
  • @larksuiteoapi/node-sdk: ^1.61.1 (bundled dep)
  • axios version: bundled with @larksuiteoapi/node-sdk

extent analysis

TL;DR

Switching the Feishu channel to webhook mode is the most likely workaround to resolve the axios timeout issue.

Guidance

  • Verify that the issue is indeed related to the axios connection pooling or keepAlive configuration by checking the axios version and its configuration in the @larksuiteoapi/node-sdk.
  • Test the workaround by configuring the Feishu channel to use webhook mode and setting up the Feishu Open Platform to POST events to the gateway endpoint.
  • If the workaround is successful, consider updating the @larksuiteoapi/node-sdk to a version that fixes the axios issue, if available.
  • Monitor the gateway logs and performance after applying the workaround to ensure it does not introduce any new issues.

Example

{
  "channels": {
    "feishu": {
      "connectionMode": "webhook",
      // ... other configurations ...
    }
  }
}

Notes

The root cause of the issue is suspected to be related to the axios connection pooling or keepAlive configuration, but the exact cause is not confirmed. The workaround may have implications on the gateway's performance and scalability.

Recommendation

Apply the workaround by switching the Feishu channel to webhook mode, as it is a relatively simple and non-invasive change that can resolve the issue.

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…
#api#generation error#database connection#vector store#embedding generation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING