openclaw - 💡(How to fix) Fix [Feature Request] Add HTTP/SOCKS5 Proxy Support for QQBot Connection [1 participants]

When running OpenClaw QQBot in an environment with dynamic IP, the QQ Open Platform rejects connections with error:

TL;DR

Add a proxy configuration option to the QQBot plugin config to enable connections through a fixed-IP proxy server.

Guidance

• Consider implementing the proposed config schema to allow users to specify proxy settings, such as type, host, port, username, and password.
• Evaluate the simpler string format "proxy": "socks5://user:pass@host:port" as an alternative to the more detailed config schema.
• Review related issues (#2153 and #8079) to ensure consistency in proxy support across different plugins and tools.
• Assess the feasibility of using a system-level transparent proxy as a temporary workaround, despite its complexity.

Example

{
  "plugins": {
    "entries": {
      "qqbot": {
        "enabled": true,
        "appId": "...",
        "clientSecret": "...",
        "proxy": {
          "type": "socks5",
          "host": "47.99.243.108",
          "port": 11080,
          "username": "optional",
          "password": "optional"
        }
      }
    }
  }
}

Notes

The proposed solution requires changes to the QQBot plugin config, which may involve updates to the plugin's code and documentation. Additionally, users may need to set up a fixed-IP proxy server to route QQBot traffic.

Recommendation

Apply workaround: Use a forked QQBot plugin with proxy support (e.g., corrinehu/qqbot-openclaw) until the official plugin is updated with proxy configuration options. This allows users to run OpenClaw locally with minimal configuration while still satisfying QQ Open Platform's IP whitelist requirement.