← Back to Channels and integrations
OpenClaw browser

Local preview, remote routing, and node-host control

Local preview trouble is often a routing or browser-policy problem, not a content problem. This page maps the correct path for local page review.

Preview ruleServe local files over HTTP, target the real browser host, and treat file:// or policy blocks as routing issues first.
Correct path

How local preview should usually work

  1. Serve the files over HTTP. Browser preview should not depend on file://.
  2. Use the real browser host. Route the preview to the machine the browser is actually running on.
  3. Check policy blocks. If navigation is blocked, treat SSRF/policy settings as the likely issue.
Examples

What usually causes local preview failure?

Using file:// directlyThe browser refuses or behaves oddly because the page was never served the right way.
Binding the server wrongThe local HTTP server is not reachable from the actual browser host or environment.
Navigation blocked by policyThe browser can run, but local/private-network policy still blocks the route.
Open deeper reference links for this page