openclaw-browser: Chromium remote debugging stays bound to 127.0.0.1 even with --remote-debugging-address=0.0.0.0
Author: camgrslCreated Feb 26, 2026Updated May 23, 2026
coollabsio/openclaw-browser:latest keeps Chrome DevTools Protocol bound to loopback (127.0.0.1:9222) even when passing:
--remote-debugging-address=0.0.0.0--remote-debugging-port=9222
As a result, the main OpenClaw container cannot reach CDP at http://browser:9222/json/version, and Browser tool integration stays unavailable (cdpReady=false).
Source: coollabsio/openclaw