Hi team,

We’re currently unable to use the browser control tool because the browser controller service is colliding on the derived CDP port range (specifically 18821).

From inside the running container we confirmed:

OPENCLAW_GATEWAY_PORT=18810
Derived ports:
- Gateway: 18810
- Bridge: 18811
- Browser control: 18812
- CDP start: 18821

Port 18821 is already bound in the shared network namespace by another process/container, which causes the browser controller to fail initialization with PortInUseError.

To avoid port-family overlap between OpenClaw instances, can we move this environment to a separate gateway port family?

Proposed change:

Set OPENCLAW_GATEWAY_PORT=19010
- Gateway: 19010
- Bridge: 19011
- Browser control: 19012
- CDP start: 19021

Then recreate/restart the container so the new ports bind cleanly.

This should eliminate CDP overlap and restore browser control functionality.

Please confirm once the container is recreated so I can retest browser control.

Thanks.

Also, if multiple OpenClaw instances are running on shared host networking, it may be worth standardizing unique gateway port families per instance (e.g., increments of 100 or 1000) to prevent future CDP range overlap.

Browser controller skill

Browser controller skill