openclaw - 💡(How to fix) Fix Browser tool unusable on datacenter IPs — Indeed, LinkedIn, Glassdoor, DuckDuckGo all block VPS IP ranges [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#59849Fetched 2026-04-08 02:39:48
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
commented ×2mentioned ×1subscribed ×1

Root Cause

The OpenClaw browser tool (Chrome CDP) works great in principle, but is effectively unusable for mainstream job sites and search engines because the VPS/server IP is blocked by Cloudflare CAPTCHAs.

RAW_BUFFERClick to expand / collapse

The OpenClaw browser tool (Chrome CDP) works great in principle, but is effectively unusable for mainstream job sites and search engines because the VPS/server IP is blocked by Cloudflare CAPTCHAs.

Affected sites confirmed blocked:

  • Indeed (de.indeed.com) — Cloudflare block
  • LinkedIn — requires login + bot detection
  • Glassdoor — Cloudflare block
  • Bing — CAPTCHA wall
  • DuckDuckGo — CAPTCHA wall ("bots use DuckDuckGo too")

Environment:

Linux VPS (vm7002), headless Chrome 146, OpenClaw 2026.4.1, IP appears as datacenter range (38.91.104.66).

Impact:

The browser tool is core functionality for research, scraping, and web interaction — all blocked by the same Cloudflare/CAPTCHA infrastructure that most major sites use.

Requested:

Either documentation on how to route browser traffic through a residential proxy, or native proxy support in the browser tool config (e.g., browser.proxyUrl or SOCKS support).

extent analysis

TL;DR

Implementing a residential proxy or native proxy support in the OpenClaw browser tool configuration is likely necessary to bypass Cloudflare CAPTCHAs.

Guidance

  • Investigate residential proxy services that can mask the datacenter IP address, making it appear as if the traffic is coming from a residential network.
  • Consider adding native proxy support to the OpenClaw browser tool configuration, such as browser.proxyUrl or SOCKS support, to route traffic through a proxy.
  • Research the feasibility of integrating a proxy rotation service to further evade CAPTCHA detection.
  • Evaluate the potential impact of proxy usage on the tool's performance and functionality.

Example

No code snippet is provided as the issue does not imply a specific code-related solution.

Notes

The effectiveness of the proposed solution may vary depending on the quality of the residential proxy service and the sophistication of Cloudflare's CAPTCHA detection mechanisms.

Recommendation

Apply a workaround by implementing a residential proxy or native proxy support, as upgrading to a fixed version is not implied in the issue. This is because the issue is related to the tool's interaction with external services (Cloudflare CAPTCHAs) rather than an internal bug that could be fixed with a version update.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING