Proxy, SSL & Network Connection Issues

## Supported Native Integrations OpenClaw has built-in support for: - Discord - Telegram - iMessage - Signal - Slack - WhatsApp - Microsoft Teams - Location services For other services, you need webhooks or custom plugins.

## Connect External Services via Webhooks (HubSpot, etc.) For services without native integration, use the webhook endpoint: Your webhook URL: `` https://YOUR_GATEWAY_URL/api/webhook/YOUR_BOT_ID

For local development, use ngrok or similar: ``bash ngrok http 3000 # Then use: https://abc123.ngrok.io/api/webhook/YOUR_BOT_ID

Setting up HubSpot webhooks: 1. Go to HubSpot → Settings → Integrations → Webhooks 2. Create a new webhook subscription 3. Enter your OpenClaw webhook URL 4. Select the events you want to receive (contacts, deals, etc.) 5. Save and test the connection

Webhook payload format OpenClaw expects: ``json { "source": "hubspot", "event": "contact.created", "data": { // Your event payload } }

## Set Up Copilot Proxy The Copilot Proxy plugin lets you use your GitHub Copilot Pro subscription with OpenClaw. Step 1: Enable the plugin

{  plugins: {    copilotProxy: {      enabled: true    }  }}

Step 2: Authenticate with GitHub Run the authentication flow:

openclaw copilot auth

This opens a browser to authenticate with your GitHub account. The token is stored securely. Step 3: Configure as a model provider

{  models: {    providers: {      copilot: {        type: "copilot-proxy",        enabled: true      }    }  },  agents: {    defaults: {      model: "copilot/gpt-4"    }  }}

Common error: `` Copilot auth expired or invalid Re-run openclaw copilot auth` to refresh credentials.

## Fix API Key / Credential Rejections Error message: `` 401 Invalid API key

Check 1: Key format Ensure your API key doesn't have extra whitespace or quotes:

// WRONG:{  apiKey: "  sk-abc123  "  // Has whitespace}// WRONG:{  apiKey: "'sk-abc123'"  // Has quotes inside}// CORRECT:{  apiKey: "sk-abc123"}

Check 2: Key location For sandboxed agents, keys MUST be in the config file, not environment variables:

// This works for sandboxed agents:{  tools: {    web: {      search: {        apiKey: "your-brave-api-key-here"      }    }  }}// This does NOT work in sandbox (env vars don't inherit):// BRAVE_API_KEY=xxx openclaw start

Check 3: Key refresh Some services (like Moltbook) require periodic re-authentication:

# Re-authenticate with Moltbookopenclaw moltbook auth# Check current auth statusopenclaw moltbook status

Error when credentials need refresh: `` Moltbook heartbeat check needs attention: the credentials file exists again, but Moltbook is rejecting the key. • agents/status worked (shows claimed) • agents/dm/check returned 401 Invalid API key

## Check OpenClaw Version Multiple ways to check your version:

# Standard version checkopenclaw --versionopenclaw -vopenclaw -V# Full status including versionopenclaw status --all# If running from sourcepnpm openclaw --version

Example output: `` OpenClaw v1.2.3 (abc1234) Gateway: running Channel: stable

## Fix Connection Timeouts If requests are timing out: Check 1: Network connectivity from sandbox

{  sandbox: {    docker: {      network: "bridge"  // Must not be "none"    }  }}

Check 2: DNS resolution ``bash # Test from inside the container docker exec -it openclaw-sandbox nslookup api.example.com

Check 3: Firewall/proxy settings If you're behind a corporate firewall:

{  network: {    proxy: "http://proxy.company.com:8080",    noProxy: ["localhost", "127.0.0.1", "*.internal.com"]  }}

## WeChat Integration (Not Officially Supported) WeChat is not officially supported due to its closed ecosystem. Community workarounds involve: 1. Using WeChat's official API (requires business verification) 2. Third-party bridges (security risks, ToS violations) 3. Desktop automation (brittle, not recommended) Check the Discord #integrations channel for community solutions.

## Fix Log Flooding from Cron/Heartbeat If logs are flooding with cron or heartbeat messages: Check your cron schedule format:

// WRONG - runs every millisecond:{  cron: {    schedule: "* * * * * *"  // 6-part = every second  }}// CORRECT - runs every minute:{  cron: {    schedule: "* * * * *"  // 5-part = every minute  }}// CORRECT - runs every hour:{  cron: {    schedule: "0 * * * *"  }}

Reduce heartbeat frequency:

{  heartbeat: {    interval: 300000  // Every 5 minutes (in ms)  }}

## Configure Reasoning/Thinking Visibility To make /reasoning stream the default:

{  agents: {    defaults: {      reasoning: "stream"  // Options: "off", "on", "stream"    }  }}

- off - No reasoning visible - on - Reasoning shown after completion - stream - Reasoning streams in real-time (like /reasoning stream)