openclaw - 💡(How to fix) Fix 🐛 Feishu channel fails with tenant_access_token error when HTTP proxy is configured [3 comments, 3 participants]

openclaw2026-03-17 11:09:31

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#48949•Fetched 2026-04-08 00:50:36

View on GitHub

Comments

Participants

Timeline

Reactions

Author

Participants

Timeline (top)

commented ×3

Feishu (飞书) channel cannot send messages when system HTTP proxy is configured. Error: Cannot destructure property 'tenant_access_token' of '(intermediate value)' as it is undefined.

Root cause: The @larksuiteoapi/node-sdk uses axios which respects system proxy settings (http_proxy/https_proxy). When proxy is enabled (e.g., v2rayN), requests to open.feishu.cn are routed through the proxy and fail with HTTP 400 error: "The plain HTTP request was sent to HTTPS port".

Error Message

2026-03-17T18:42:11.506+08:00 [delivery-recovery] Retry failed for delivery 0ae83c95-443b-40bb-9e61-48519f90e297: Cannot destructure property 'tenant_access_token' of '(intermediate value)' as it is undefined.

[error]: AxiosError: Request failed with status code 400 ... url: 'https://open.feishu.cn/open-apis/auth/v3/tenant_access_token/internal' ... response: { status: 400, statusText: 'Bad Request', data: '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<html> <head><title>400 The plain HTTP request was sent to HTTPS port</title></head> <body> <h1>400 Bad Request</h1> <p>The plain HTTP request was sent to HTTPS port.<hr/>Powered by Tengine</body> </html>' }

Root Cause

Fix Action

Fix / Workaround

Workaround (Temporary)

Option 2: Patch Lark SDK to disable proxy (what I did to fix locally)

Severity: High - Feishu channel is completely unusable for users with HTTP proxy
Affected users: Anyone using corporate proxy, v2rayN, Shadowsocks, or similar tools
Workaround availability: Requires manual configuration (not user-friendly)

Code Example

2026-03-17T18:42:11.506+08:00 [delivery-recovery] Retry failed for delivery 0ae83c95-443b-40bb-9e61-48519f90e297: Cannot destructure property 'tenant_access_token' of '(intermediate value)' as it is undefined.

[error]: AxiosError: Request failed with status code 400
...
url: 'https://open.feishu.cn/open-apis/auth/v3/tenant_access_token/internal'
...
response: {
  status: 400,
  statusText: 'Bad Request',
  data: '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html>
<head><title>400 The plain HTTP request was sent to HTTPS port</title></head>
<body>
<h1>400 Bad Request</h1>
<p>The plain HTTP request was sent to HTTPS port.<hr/>Powered by Tengine</body>
</html>'
}

---

export http_proxy="http://127.0.0.1:10808"
   export https_proxy="http://127.0.0.1:10808"

---

{
     "channels": {
       "feishu": {
         "enabled": true,
         "defaultAccount": "main",
         "accounts": {
           "main": {
             "appId": "cli_xxx",
             "appSecret": "xxx"
           }
         }
       }
     }
   }

---

openclaw message send --channel feishu --target oc_xxx --message "test"

---

export NO_PROXY="localhost,127.0.0.1,10.82.1.0/24,open.feishu.cn,*.feishu.cn,feishu.cn"

---

openclaw gateway restart

---

// Before
const defaultHttpInstance = axios__default["default"].create();

// After  
const defaultHttpInstance = axios__default["default"].create({ proxy: false });

---

import axios from "axios";

function configureFeishuAxiosProxy(): void {
  const noProxy = process.env.NO_PROXY || process.env.no_proxy || '';
  const shouldBypass = noProxy.split(',').some(pattern => 
    pattern === 'open.feishu.cn' || 
    pattern === '*.feishu.cn' ||
    pattern === '.feishu.cn' ||
    pattern === 'feishu.cn'
  );
  
  if (shouldBypass) {
    axios.defaults.proxy = false;
  }
}

export function createFeishuClient(creds: FeishuClientCredentials): Lark.Client {
  configureFeishuAxiosProxy();
  // ... rest of client creation
}

RAW_BUFFERClick to expand / collapse

🐛 Bug: Feishu channel fails with `tenant_access_token` error when HTTP proxy is configured

Summary

Feishu (飞书) channel cannot send messages when system HTTP proxy is configured. Error: Cannot destructure property 'tenant_access_token' of '(intermediate value)' as it is undefined.

Environment

OpenClaw version: 2026.3.13
Node version: 22.22.0
OS: macOS 15.3.0 (arm64)
Feishu SDK: @larksuiteoapi/[email protected]
Proxy: v2rayN (HTTP proxy at http://127.0.0.1:10808)

Error Details

Gateway Logs

2026-03-17T18:42:11.506+08:00 [delivery-recovery] Retry failed for delivery 0ae83c95-443b-40bb-9e61-48519f90e297: Cannot destructure property 'tenant_access_token' of '(intermediate value)' as it is undefined.

[error]: AxiosError: Request failed with status code 400
...
url: 'https://open.feishu.cn/open-apis/auth/v3/tenant_access_token/internal'
...
response: {
  status: 400,
  statusText: 'Bad Request',
  data: '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html>
<head><title>400 The plain HTTP request was sent to HTTPS port</title></head>
<body>
<h1>400 Bad Request</h1>
<p>The plain HTTP request was sent to HTTPS port.<hr/>Powered by Tengine</body>
</html>'
}

Key Observation

The error 400 The plain HTTP request was sent to HTTPS port indicates that:

Request is being sent to proxy (127.0.0.1:10808)
Proxy is mishandling the HTTPS CONNECT tunnel
Feishu API server receives plain HTTP instead of HTTPS

Reproduction Steps

Configure system proxy:

export http_proxy="http://127.0.0.1:10808"
export https_proxy="http://127.0.0.1:10808"

Configure Feishu channel in ~/.openclaw/openclaw.json:

{
  "channels": {
    "feishu": {
      "enabled": true,
      "defaultAccount": "main",
      "accounts": {
        "main": {
          "appId": "cli_xxx",
          "appSecret": "xxx"
        }
      }
    }
  }
}

Start Gateway and attempt to send Feishu message:

openclaw message send --channel feishu --target oc_xxx --message "test"

Expected: Message sent successfully
Actual: Error Cannot destructure property 'tenant_access_token'

Workaround (Temporary)

Option 1: Add Feishu domains to NO_PROXY

export NO_PROXY="localhost,127.0.0.1,10.82.1.0/24,open.feishu.cn,*.feishu.cn,feishu.cn"

Then restart Gateway:

openclaw gateway restart

Option 2: Patch Lark SDK to disable proxy (what I did to fix locally)

File: /opt/homebrew/lib/node_modules/openclaw/node_modules/@larksuiteoapi/node-sdk/lib/index.js

Change:

// Before
const defaultHttpInstance = axios__default["default"].create();

// After  
const defaultHttpInstance = axios__default["default"].create({ proxy: false });

Proposed Fix

In `@openclaw/feishu` extension

The Feishu channel plugin should configure the Lark SDK's HTTP instance to bypass proxy for Feishu API domains by default. This is similar to how enterprise SaaS APIs should be accessed directly, not through user's proxy.

Suggested code change in extensions/feishu/src/client.ts:

import axios from "axios";

function configureFeishuAxiosProxy(): void {
  const noProxy = process.env.NO_PROXY || process.env.no_proxy || '';
  const shouldBypass = noProxy.split(',').some(pattern => 
    pattern === 'open.feishu.cn' || 
    pattern === '*.feishu.cn' ||
    pattern === '.feishu.cn' ||
    pattern === 'feishu.cn'
  );
  
  if (shouldBypass) {
    axios.defaults.proxy = false;
  }
}

export function createFeishuClient(creds: FeishuClientCredentials): Lark.Client {
  configureFeishuAxiosProxy();
  // ... rest of client creation
}

Alternative: Better NO_PROXY handling in getWsProxyAgent

The existing getWsProxyAgent() function already checks NO_PROXY for WebSocket client, but the HTTP client (used for API calls) doesn't respect it.

Impact

Severity: High - Feishu channel is completely unusable for users with HTTP proxy
Affected users: Anyone using corporate proxy, v2rayN, Shadowsocks, or similar tools
Workaround availability: Requires manual configuration (not user-friendly)

Additional Context

Feishu is an official supported channel in OpenClaw
This is a common pattern: enterprise SaaS APIs (Feishu, Lark, etc.) should bypass user proxy by default
Similar issues may affect other channels that use axios or similar HTTP libraries

Suggested Priority

🔴 High - Blocks Feishu channel usage for proxy users

Reported by: OpenClaw user (Apple Lobster / 苹果龙虾)
Date: 2026-03-17
Contact: Available via OpenClaw Discord or GitHub

extent analysis

Fix Plan

To resolve the issue with the Feishu channel failing due to tenant_access_token errors when an HTTP proxy is configured, we will implement the following steps:

Modify the @openclaw/feishu extension: Update the extensions/feishu/src/client.ts file to configure the Lark SDK's HTTP instance to bypass the proxy for Feishu API domains by default.
Implement NO_PROXY handling: Enhance the getWsProxyAgent() function to respect the NO_PROXY environment variable for both WebSocket and HTTP clients.

Code Changes

Step 1: Modify `client.ts`

import axios from "axios";

function configureFeishuAxiosProxy(): void {
  const noProxy = process.env.NO_PROXY || process.env.no_proxy || '';
  const shouldBypass = noProxy.split(',').some(pattern => 
    pattern === 'open.feishu.cn' || 
    pattern === '*.feishu.cn' ||
    pattern === '.feishu.cn' ||
    pattern === 'feishu.cn'
  );
  
  if (shouldBypass) {
    axios.defaults.proxy = false;
  }
}

export function createFeishuClient(creds: FeishuClientCredentials): Lark.Client {
  configureFeishuAxiosProxy();
  // ... rest of client creation
}

Step 2: Update `getWsProxyAgent()` (if necessary)

Ensure that the getWsProxyAgent() function checks the NO_PROXY environment variable and bypasses the proxy for Feishu API domains.

Verification

To verify that the fix worked:

Configure your system proxy using export http_proxy="http://127.0.0.1:10808" and export https_proxy="http://127.0.0.1:10808".
Restart the Gateway using openclaw gateway restart.
Attempt to send a Feishu message using openclaw message send --channel feishu --target oc_xxx --message "test".
Verify that the message is sent successfully without any tenant_access_token errors.

Extra Tips

Ensure that the NO_PROXY environment variable is set correctly to include Feishu API domains.
If using a proxy manager like v2rayN, configure it to bypass the proxy for Feishu API domains.
Monitor the Gateway logs for any issues related to proxy configuration or Feishu API connectivity.

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?

#api #ssr #installation #tensor shape #autograd error #cache error #pipeline error #runtime error #dependency conflict

Still need to ship something?

×6

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

openclaw - 💡(How to fix) Fix 🐛 Feishu channel fails with tenant_access_token error when HTTP proxy is configured [3 comments, 3 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fix / Workaround

Workaround (Temporary)

Option 2: Patch Lark SDK to disable proxy (what I did to fix locally)

Code Example

🐛 Bug: Feishu channel fails with tenant_access_token error when HTTP proxy is configured

Summary

Environment

Error Details

Gateway Logs

Key Observation

Reproduction Steps

Workaround (Temporary)

Option 1: Add Feishu domains to NO_PROXY

Option 2: Patch Lark SDK to disable proxy (what I did to fix locally)

Proposed Fix

In @openclaw/feishu extension

Alternative: Better NO_PROXY handling in getWsProxyAgent

Impact

Additional Context

Suggested Priority

extent analysis

Fix Plan

Code Changes

Step 1: Modify client.ts

Step 2: Update getWsProxyAgent() (if necessary)

Verification

Extra Tips

Still need to ship something?

RELATED_DISCOVERY

TRENDING

🐛 Bug: Feishu channel fails with `tenant_access_token` error when HTTP proxy is configured

In `@openclaw/feishu` extension

Step 1: Modify `client.ts`

Step 2: Update `getWsProxyAgent()` (if necessary)