#container-setup
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2587 issues
After upgrading to OpenClaw 2026.3.13, the local loopback gateway behaves inconsistently. This is broader than the already reported status/probe `missing scope: operator.read` issue. In my case, the same gateway runtime shows: - successful local webchat/control-ui RPC for some connections - `missing scope: operator.read` for other local RPC calls - intermittent websocket handshake timeout / closed before connect - occasional failed first restart attempt before successful second start - some CLI commands failing completely with `gateway closed (1000 normal closure): no close reason` So this looks like a wider local auth/scope/session instability, not only a misleading status/probe message. Environment - OpenClaw version: 2026.3.13 - OS: Debian/Linux - Node: 22.22.1 - Gateway mode: local - Gateway bind: loopback (ws://127.0.0.1:18789) - Gateway service: systemd user service - Browser server enabled locally - Telegram channel enabled and healthy
Setting `ask: off` / `security: full` in exec-approvals.json has no effect on Windows; every exec call returns `exec denied: allowlist miss` even after gateway restart.
After re-authenticating OpenAI Codex multiple times, Gateway kept logging `refresh_token_reused` and some runs failed with OAuth refresh errors. In our case, the root cause appears to be that the main agent auth store retained both: - `openai-codex:default` (older login) - a newer named Codex profile (email-based profile key) Different paths seemed to use different profiles, which led to refresh-token rotation conflicts. Removing the stale `openai-codex:default` entry and keeping only the newest named profile fixed the issue.
On macOS, OpenClaw 2026.3.13 completes the browser auth step for OpenAI Codex OAuth but fails at code-to-token exchange, while 2026.2.6-3 succeeds under the same proxy setup.
After updating to **2026.4.5**, third-party memory plugins fail to initialize with: ``` memory-lancedb-pro invalid config: embedding: must have required property 'embedding' 1 plugin(s) failed to initialize (validation: memory-lancedb-pro) ``` This does not occur on 2026.4.4 with the same config.
The OpenClaw gateway HTTP server binds to 127.0.0.1 inside the Docker container and is not reachable via Docker host port forwarding. Accessing the gateway from inside the container succeeds (401 Unauthorized), but requests to the host's forwarded port fail with "Connection reset by peer".
When routing Azure GPT-5.2 chat requests through LiteLLM, `vector_store_ids` can leak into provider payload via `extra_body`, causing Azure to reject the request with: `litellm.BadRequestError: AzureException BadRequestError - Unknown parameter: 'vector_store_ids'`
`openclaw doctor` reports `Telegram: not configured` in the channel probe section, even though the Telegram channel is fully operational.
After upgrading OpenClaw from a working older build to **2026.3.28**, our local setup started behaving incorrectly. Rolling back to **2026.3.24** immediately restores normal behavior. At the moment this looks like an OpenClaw regression rather than a problem in our local reranker server or in `memory-lancedb-pro` alone.