Hi Zeabur Team,
I'm experiencing an issue with OpenClaw's browser tool on Zeabur.
The browser tool is not working and returns the error:
"Error: No supported browser found (Chrome/Brave/Edge/Chromium on macOS, Linux, or Windows)."
Setup Details:
- Main Service: OpenClaw-dists (Service ID: 69a9619ba847f44e511d81d7)
- Browser Sandbox: openclaw-sandbox-browser (Service ID: 69b3aa5ada87c2b9576efd79)
- Project ID: 69a5b446971cdaeedfa5b751
- Environment ID: 69a5b4468ca26dea02bdb33d
What I've Done:
- Deployed OpenClaw using the official template
- Deployed OpenClaw Browser Sandbox template to the same project
- Verified Chromium is running in Browser Sandbox (listening on ws://127.0.0.1:9223)
- Set environment variables:
- OPENCLAW_BROWSER_CDP_ADDRESS=0.0.0.0
- OPENCLAW_BROWSER_CDP_URL=ws://service-69b3aa5ada87c2b9576efd79:9222
- OPENCLAW_BROWSER_CDP_PORT=9222
- Restarted both services multiple times
- Verified all environment variables are correctly set
The Problem:
Despite all configurations, OpenClaw main service cannot connect to the Browser Sandbox.
The browser tool still reports "No supported browser found" error.
Possible Root Cause:
- Service-to-service network communication issue
- DNS resolution problem (service name not resolving)
- Network isolation between services
- WebSocket (ws://) protocol not supported between services
Questions:
- Can services in the same Zeabur project communicate with each other using service names?
- Is there any network isolation or firewall between services?
- Are WebSocket connections supported between services?
- Is there a specific way to configure inter-service communication on Zeabur?
Any help would be greatly appreciated!