openclaw - 💡(How to fix) Fix [Bug]:Feishu websocket proxy mismatch (actual socks5 expected http) with OpenClaw 2026.4.5

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…

Feishu websocket proxy mismatch (actual socks5 expected http) with OpenClaw 2026.4.5

Error Message

[error]: [ '[ws]', 'protocol mismatch' ] [error]: [ '[ws]', 'connect failed' ]

Root Cause

Feishu websocket proxy mismatch (actual socks5 expected http) with OpenClaw 2026.4.5

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Feishu websocket proxy mismatch (actual socks5 expected http) with OpenClaw 2026.4.5

Steps to reproduce

Hi, I successfully connected OpenClaw to ChatGPT Codex OAuth, and local agent calls work correctly.

Environment:

OpenClaw 2026.4.5 macOS Feishu channel enabled Proxy app enabled (mixed SOCKS5/HTTP port: 7897)

What works:

openclaw models auth login --provider openai-codex OAuth successful Local agent works: openclaw agent --agent main --message "hello" Codex responds correctly

Problem: Feishu websocket/channel cannot connect.

Gateway starts successfully:

[gateway] ready [gateway] agent model: openai-codex/gpt-5.4

But Feishu websocket repeatedly fails with:

AssertionError [ERR_ASSERTION]: protocol mismatch

actual: 'socks5:' expected: 'http:'

Relevant logs:

[feishu] starting WebSocket connection... [error]: [ '[ws]', 'protocol mismatch' ] [error]: [ '[ws]', 'connect failed' ]

AssertionError [ERR_ASSERTION]: protocol mismatch at Object.request (.../follow-redirects/index.js:541:14)

Already tried:

unset ALL_PROXY unset HTTP_PROXY / HTTPS_PROXY using only: HTTP_PROXY=http://127.0.0.1:7897 HTTPS_PROXY=http://127.0.0.1:7897 restarting gateway verifying FR proxy IP local Codex calls confirmed working

Observation: It seems Feishu SDK / axios / follow-redirects still detects a socks5: proxy somewhere (possibly system-level), while expecting http:.

Any ideas where OpenClaw / Feishu websocket transport may still be reading SOCKS settings?

Expected behavior

/

Actual behavior

/

OpenClaw version

OpenClaw 2026.4.5

Operating system

mac OS13.7.8

Install method

No response

Model

openai-codex/gpt-5.4

Provider / routing chain

/

Additional provider/model setup details

/

Logs, screenshots, and evidence

Impact and severity

No response

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

/

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]:Feishu websocket proxy mismatch (actual socks5 expected http) with OpenClaw 2026.4.5