Skip to content

fix(openclaw): bind gateway to loopback interface#1857

Draft
felipevicens wants to merge 1 commit into
kagent-dev:mainfrom
felipevicens:fix/openclaw-gateway-loopback-bind
Draft

fix(openclaw): bind gateway to loopback interface#1857
felipevicens wants to merge 1 commit into
kagent-dev:mainfrom
felipevicens:fix/openclaw-gateway-loopback-bind

Conversation

@felipevicens
Copy link
Copy Markdown

Add Bind: loopback to the openclaw gateway bootstrap configuration
so the local gateway only listens on the loopback interface rather
than all network interfaces.

Without this setting, OpenClaw defaults to 0.0.0.0. However, the sandbox iptables rules block all non-proxy traffic, so the TUI can only reach the gateway through loopback inside the sandbox network namespace. As a result, binding to 0.0.0.0 makes the gateway unreachable from the TUI (not connected to gateway).

Setting "bind": "loopback" fixes the issue at the source in the generated config, instead of requiring a manual post-creation patch to openclaw.json.

   Add Bind: loopback to the openclaw gateway bootstrap configuration
   so the local gateway only listens on the loopback interface rather
   than all network interfaces.

Signed-off-by: Felipe Vicens <felipejose.vicensgonzalez@telefonica.com>
@github-actions github-actions Bot added the bug Something isn't working label May 12, 2026
@peterj
Copy link
Copy Markdown
Collaborator

peterj commented May 12, 2026

thanks for the PR! Could you also just update the unit test here, so it also check the bind value being set correctly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants