#network-issue
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2617 issues
When running `openclaw update`, the **Completion cache update** step produces the following error: ``` Completion cache update failed ([openclaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md at readQaScenarioPack (file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:754:27) at readQaScenarioById (file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:790:19) at readQaScenarioExecutionConfig (file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:795:9) at readRequiredDiscoveryRefs (file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:2834:9) at file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:2840:39 ```
After a gateway restart following the 2026.4.1 update, the local node-host service requests a role-upgrade repair pairing (roleFrom=operator roleTo=node). This creates an unresolvable deadlock: openclaw devices list works (uses local fallback) openclaw devices approve <requestId> returns unknown requestId — no local fallback path openclaw doctor --fix does not detect or resolve the pending request The Control UI dashboard shows no pending pairing request to approve via UI All CLI commands requiring gateway auth fail with 1008: pairing required The result is a fully locked gateway that cannot be recovered through any supported CLI path.
Telegram cannot start because the plugin fails to load at startup due to missing grammY-related runtime dependencies. This is not a Telegram token / webhook / network issue. The failure happens during module loading before the Telegram runtime can start.
When spawning a subagent with `sessions_spawn` using an NVIDIA provider configured as `"api": "openai-completions"`, OpenClaw sends Anthropic-style message content (arrays with `type` objects) instead of OpenAI-style simple strings. This causes the NVIDIA API to reject requests with HTTP 400 errors. bug was created using openclaw *
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.
When configuring multiple Ollama providers (`ollama` on port 11434 and `ollama2` on port 11435), the Gateway routes ALL requests to the first provider (`ollama` on port 11434), completely ignoring the `baseUrl` configured for `ollama2`.
Gateway token validation fails immediately after upgrading from 2026.4.1 to 2026.4.2. All OpenClaw CLI commands return "Gateway closed (1008): unauthorized: gateway token mismatch" error. Token is correctly configured but rejected by gateway. System becomes completely non-functional until manual service restart.