openclaw - 💡(How to fix) Fix [Bug]: neodata proxy returns error 9021 (forward_error) [1 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#72248Fetched 2026-04-27 05:32:36
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×2closed ×1commented ×1

neodata proxy at http://localhost:19000/proxy/api returns error code 9021 (forward_error). Error changed from 9002 (auth_error) to 9021 after restart. Port is reachable but gateway forwarding fails.

Error Message

neodata proxy at http://localhost:19000/proxy/api returns error code 9021 (forward_error). Error changed from 9002 (auth_error) to 9021 after restart. Port is reachable but gateway forwarding fails. 3. Any API call returns error 9021 Returns error 9021 (forward_error) from gateway Error response: {"error":{"code":"9021","message":"请求异常,请稍后重试","type":"forward_error","source":"gateway"}} Port 19000 is reachable, but gateway forwarding fails. Error changed from 9002 (auth_error) to 9021 (forward_error) after QClaw restart. Browser shows localhost:19000/proxy/api responds but returns error 9021 for all queries.

Root Cause

neodata proxy at http://localhost:19000/proxy/api returns error code 9021 (forward_error). Error changed from 9002 (auth_error) to 9021 after restart. Port is reachable but gateway forwarding fails.

Code Example

Browser shows localhost:19000/proxy/api responds but returns error 9021 for all queries.
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

neodata proxy at http://localhost:19000/proxy/api returns error code 9021 (forward_error). Error changed from 9002 (auth_error) to 9021 after restart. Port is reachable but gateway forwarding fails.

Steps to reproduce

  1. Start QClaw gateway
  2. Visit http://localhost:19000/proxy/api in browser
  3. Any API call returns error 9021

Expected behavior

Should return stock data normally via neodata proxy

Actual behavior

Returns error 9021 (forward_error) from gateway

OpenClaw version

0.2.14

Operating system

Windows 11

Install method

Windows Installer

Model

qclaw/modelroute

Provider / routing chain

neodata (localhost:19000/proxy/api)

Additional provider/model setup details

Error response: {"error":{"code":"9021","message":"请求异常,请稍后重试","type":"forward_error","source":"gateway"}}

Port 19000 is reachable, but gateway forwarding fails. Error changed from 9002 (auth_error) to 9021 (forward_error) after QClaw restart.

Logs, screenshots, and evidence

Browser shows localhost:19000/proxy/api responds but returns error 9021 for all queries.

Impact and severity

  • 受影响:股票数据查询功能完全不可用
  • 严重程度:高(核心功能失效)
  • 频率:总是
  • 后果:无法获取实时股票数据,交易系统瘫痪

Additional information

之前正常使用,重启后错误码从9002变为9021。

extent analysis

TL;DR

The neodata proxy error 9021 (forward_error) after a QClaw restart may be resolved by investigating and fixing the gateway forwarding issue.

Guidance

  • Verify the QClaw gateway configuration to ensure it is correctly set up to forward requests to the neodata proxy.
  • Check the neodata proxy logs for any errors or issues that may be causing the forwarding to fail.
  • Investigate the change in error code from 9002 (auth_error) to 9021 (forward_error) after the restart, as this may indicate a change in the underlying issue.
  • Test the neodata proxy directly (bypassing the QClaw gateway) to determine if the issue is specific to the gateway or a more general problem with the proxy.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The issue may be related to a configuration change or an issue with the QClaw gateway or neodata proxy. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Investigate and fix the gateway forwarding issue, as the error code change suggests a potential configuration or connectivity problem.

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

Should return stock data normally via neodata proxy

Still need to ship something?

×6

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

Back to top recommendations

TRENDING