OpenClaw Discord proxy fix for REST API timeout issues
If your OpenClaw Discord bot appears connected but can't send messages or run commands, you might be experiencing a proxy configuration issue where WebSocket connections work but REST API calls don't.
The Problem
A user on r/openclaw reported their Discord channel suddenly stopped working. Running openclaw doctor showed "Discord failed" and logs were spamming: "fetch failed UND_ERR_CONNECT_TIMEOUT".
The issue wasn't a broken proxy, but rather that the proxy setting in OpenClaw was sufficient for Discord WebSocket connections but not for REST API requests. This created a situation where the bot looked half-connected but couldn't actually function.
The Solution
Here's what fixed it:
- Keep the Discord proxy configuration in your OpenClaw JSON file
- Create a file at
~/.openclaw/proxy-preload.cjs - Set a global undici proxy in that file
- Start OpenClaw with
NODE_OPTIONS=--require=...to load the proxy configuration
Important Notes
- Use an HTTP proxy, not SOCKS5
- If you update OpenClaw, check whether the bundled undici path has changed
This specific configuration issue can cause Discord to appear connected while REST calls fail silently, preventing message sending and command execution.
📖 Read the full source: r/openclaw
👀 See Also
How to disable Claude Code's verb spinner feature
Claude Code includes a default verb spinner that displays whimsical gerunds like 'Seasoning' and 'Crafting' during processing. You can disable it by editing the settings.json file with a blank space in the spinnerVerbs array.
Enhancing OpenClaw with the Power of Local LLM: Introducing GLM-4.7-Flash
The integration of GLM-4.7-Flash with OpenClaw is revolutionizing AI automation by enabling seamless local deployment and sophisticated code execution.
Claude Code Self-Audit Finds 3GB of Cruft in ~/.claude — Here's How to Clean It
A user prompted Claude Code to audit its own ~/.claude directory and found 2.6GB of stale session transcripts, 170MB of failed telemetry retry logs, and 153MB of undo buffers — dropping from 3GB to under 200MB after cleanup.
Why Most Claude Pipeline Failures Trace Back to Prompts, Not Models — and How to Fix with Skills
A Reddit post argues that the root cause of pipeline failures in Claude workflows is treating prompts like skills. The fix: define input contracts, output schemas, and a learnings file — making a skill what you promote to v1.