openclaw - 💡(How to fix) Fix [Bug]: falling back to HTTP. error=Error: connect ENETUNREACH [1 participants]

openclaw-gateway-1 | 2026-03-31T23:49:35.300-07:00 [agent/embedded] [ws-stream] WebSocket connect failed for session=059e30ae-e63c-4baa-b0f5-1ba797673dae; falling back to HTTP. error=Error: connect ENETUNREACH 162.159.140.245:443 - Local (0.0.0.0:0) openclaw-gateway-1 | 2026-03-31T23:49:35.300-07:00 [agent/embedded] [ws-stream] WebSocket connect failed for session=059e30ae-e63c-4baa-b0f5-1ba797673dae; falling back to HTTP. error=Error: connect ENETUNREACH 162.159.140.245:443 - Local (0.0.0.0:0)

TL;DR

• Set the NO_PROXY environment variable or configure OpenClaw to use the HTTP_PROXY and HTTPS_PROXY environment variables for WebSocket connections.

Guidance

• Verify that the HTTP_PROXY and HTTPS_PROXY environment variables are set correctly before running OpenClaw.
• Check the OpenClaw documentation for any configuration options that allow specifying a proxy for WebSocket connections.
• Consider setting the NO_PROXY environment variable to a specific value to see if it affects the behavior of OpenClaw.
• Test the connection using a tool like curl to see if it respects the proxy settings.

Example

• No code snippet is provided as there is no clear indication of the programming language or framework used.

Notes

• The issue seems to be related to the fact that OpenClaw is not respecting the HTTP_PROXY and HTTPS_PROXY environment variables for WebSocket connections.
• The provided logs indicate that OpenClaw is trying to connect directly to the server instead of using the proxy.

Recommendation

• Apply workaround: Set the NO_PROXY environment variable or configure OpenClaw to use the HTTP_PROXY and HTTPS_PROXY environment variables for WebSocket connections, as it seems that OpenClaw is not respecting these variables by default.