Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] Memory index command ignores proxy environment variables [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#63087•Fetched 2026-04-09 07:58:46
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
ifitrainifitrain
Participants
ifitrainifitrain

Error Message

  1. Command fails with timeout error Memory index failed (main): fetch failed | Connect Timeout Error

Fix Action

Fix / Workaround

Workarounds Attempted

  • Setting all proxy environment variables (HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, lowercase variants)
  • Direct connection works fine for other tools (curl, gh, etc.)
  • Only OpenClaw memory index ignores proxy settings

Code Example

HTTP_PROXY=http://127.0.0.1:7897
   HTTPS_PROXY=http://127.0.0.1:7897
   ALL_PROXY=http://127.0.0.1:7897
   http_proxy=http://127.0.0.1:7897
   https_proxy=http://127.0.0.1:7897

---

Memory index failed (main): fetch failed | Connect Timeout Error 
(attempted addresses: 142.251.34.202:443, 142.250.73.74:443, ...)
RAW_BUFFERClick to expand / collapse

OpenClaw Memory Index Not Respecting Proxy Environment Variables

Problem Description

The openclaw memory index command does not respect proxy environment variables (HTTP_PROXY, HTTPS_PROXY, etc.), causing connection timeouts when trying to access Google Gemini embedding service.

Environment

  • OS: macOS 26.3 (Sonoma) - Mac mini M4 Pro (arm64)
  • OpenClaw Version: 2026.4.5
  • Node.js Version: v25.9.0
  • Network: Behind proxy requiring 127.0.0.1:7897 for external access

Issue Symptoms

  1. Memory index command attempts to connect directly to Google API (142.250.x.x:443)
  2. Connection times out after 10 seconds
  3. Proxy environment variables are set but ignored: 
    HTTP_PROXY=http://127.0.0.1:7897
HTTPS_PROXY=http://127.0.0.1:7897
ALL_PROXY=http://127.0.0.1:7897
http_proxy=http://127.0.0.1:7897
https_proxy=http://127.0.0.1:7897
  4. Port 7897 is confirmed open and working (tested with curl and nc)

Steps to Reproduce

  1. Set proxy environment variables
  2. Run: openclaw memory index --force
  3. Observe connection attempts to Google IPs instead of proxy
  4. Command fails with timeout error

Expected Behavior

The memory index command should respect standard proxy environment variables and route requests through the configured proxy.

Actual Behavior

Memory index failed (main): fetch failed | Connect Timeout Error 
(attempted addresses: 142.251.34.202:443, 142.250.73.74:443, ...)

Workarounds Attempted

  • Setting all proxy environment variables (HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, lowercase variants)
  • Direct connection works fine for other tools (curl, gh, etc.)
  • Only OpenClaw memory index ignores proxy settings

Request

Please add support for proxy environment variables in the memory index command, or provide a configuration option to specify proxy settings.

Related Issues

  • May be related to how Node.js fetch/axios is configured in the memory-core plugin
  • Consider using standard Node.js proxy support or allowing custom agent configuration

extent analysis

TL;DR

The OpenClaw memory index command likely needs to be configured or modified to respect and utilize the proxy environment variables for routing requests through the specified proxy.

Guidance

  • Verify that the proxy environment variables are correctly set and accessible within the context of the OpenClaw command execution.
  • Investigate the use of a custom agent configuration in the memory-core plugin to explicitly specify the proxy settings.
  • Consider modifying the OpenClaw memory index command to utilize standard Node.js proxy support, potentially through the http and https modules or libraries like axios.
  • Review related issues and discussions regarding proxy support in Node.js and its applications to identify potential solutions or workarounds.

Example

No specific code example can be provided without further details on the OpenClaw implementation. However, a general approach might involve setting a proxy agent for HTTP requests, such as:

const { HttpsProxyAgent } = require('https-proxy-agent');
const proxyUrl = 'http://127.0.0.1:7897';
const agent = new HttpsProxyAgent(proxyUrl);
// Use the agent in your HTTP requests

Notes

The solution may depend on the specific implementation details of the OpenClaw memory index command and the memory-core plugin, which are not fully provided in the issue description.

Recommendation

Apply a workaround by configuring a custom proxy agent within the OpenClaw memory index command or the memory-core plugin, as this seems to be the most direct approach to resolving the issue given the current information.

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#environment variable#index setup#retrieval issue#search optimization

Still need to ship something?

×6

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

Back to top recommendations

TRENDING