#api-routing
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2541 issues
After upgrading from 2026.3.28 to 2026.3.31, the gateway starts successfully (binds port, loads plugins, connects WhatsApp) but becomes completely unresponsive within 30-60 seconds. The process cannot be stopped gracefully (SIGTERM times out after 30s, requires SIGKILL). Consistent across multiple restart attempts. Rolled back to 2026.3.28 — immediately stable, no issues.
On a hardened Debian 13 VPS, OpenClaw browser automation fails even though Brave is running headless, exposes a valid CDP endpoint on localhost, and returns a valid `webSocketDebuggerUrl`. OpenClaw reports the browser profile as **not running**, returns **no tabs**, and `browser open` fails with **PortInUseError** instead of attaching to the existing CDP browser. This appears to be an OpenClaw Linux/VPS browser attach/runtime issue, not a missing-browser or broken-CDP issue.
On OpenClaw `2026.3.8-beta.1`, local Ollama models are callable directly via `ollama run`, but OpenClaw agent runs intermittently fail with: - `LLM request timed out` - `rawErrorPreview":"fetch failed"` This happens for both: - `qwen3.5:122b-a10b` - `gpt-oss:120b`
OpenClaw version: 2026.4.5 (3e72c03) Node.js version: v22.22.2 (also reproduced on v24.14.0) OS: Windows 11 (10.0.26200) Running openclaw onboard on native Windows crashes immediately after selecting a model. The ESM loader rejects the module specifier because it receives a raw Windows path (C:\...) instead of a file:/// URL. Steps to reproduce 1. Install openclaw globally on Windows: npm install -g openclaw 2. Run openclaw onboard 3. Select Ollama as the provider 4. Select any model (e.g. ollama/gemma4:e4b) Error Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:' Root cause The plugin/extension loader in dist/loader-BkajlJCF.js resolves plugin paths to absolute Windows paths (e.g. C:\Users\...\extensions\openclaw-web-search) and passes them directly to jiti / dynamic import(). On Windows, ESM requires these to be file:///C:/... URLs. Relevant lines in dist/loader-BkajlJCF.js: - Line ~2526: mod = getJiti(safeSource)(safeSource); - Line ~2213: const runtimeModule = getJiti(runtimeModulePath)(runtimeModulePath); Also in dist/io-CS2J_l4V.js: - Line ~161: mod = getJiti(contractSource)(contractSource); Suggested fix Wrap paths with pathToFileURL() before passing to dynamic import: import { pathToFileURL } from 'node:url'; // Before mod = getJiti(safeSource)(safeSource); // After mod = getJiti(safeSource)(pathToFileURL(safeSource).href); Workaround Running openclaw under WSL2 avoids the issue since Linux paths don't have drive letters.
CPU Intel(R) Core(TM) i7-4900MQ CPU @ 2.80GHz 2.80 GHz RAM 32.0 GB (31.7 GB 可用) 238 GB SSD SAMSUNG MZ7LN256HCHP-000L7, 1.82 TB HDD ST2000LM015-2E8174 NVIDIA Quadro K3100M (4 GB), Intel(R) HD Graphics 4600 (113 MB) Windows 10 专业版 VERSION:22H2 OS Internal version 19045.6466 I normally use the laptop with the AC power adapter plugged in, and OpenClaw runs completely fine. But as soon as I unplug the adapter and switch to battery power, the OpenClaw Gateway daemon crashes every single time — the failure rate is 100%.
Encountered this error although `gwen3:8b` has been pulled by ollama (and indicated in the error log too)
Antfarm workflow cron creation fails with 'gateway timeout after 120ms' error when using OpenClaw CLI fallback, preventing workflows from running autonomously.
Channels Empty
Web UI model selector sends bare model IDs with wrong provider prefix when multiple providers are configured, causing "model not allowed" errors for non-default providers.
There are five related bugs in the Anthropic `/v1/messages` experimental pass-through implementation when routing requests to OpenAI/Azure models. These issues were discovered during integration testing with Claude Code CLI which uses `input_text` content block format and requires forcing routing through Chat Completions API when the downstream proxy doesn't support Responses API.
Gateway restart fails due to stale process misdetection and race condition
在 Windows 上使用 `openclaw gateway install` 安装的计划任务，在关闭 PowerShell 窗口后 Gateway 会断连，必须重新运行 `openclaw gateway start` 才能恢复。
A fresh `npm install -g openclaw` of v2026.4.5 crashes immediately on any command (e.g. `openclaw doctor`) because 8 packages are imported in the bundled dist files but not declared in `package.json` `dependencies`. This affects anyone doing a clean global install or update. It is **not** environment-specific — npm only installs declared dependencies, so the missing packages are never present.