-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Configure stealth and proxies
SGavrl edited this page May 30, 2026
·
1 revision
obscura fetch https://example.com --stealth
obscura serve --stealth
obscura mcp --stealthWhat --stealth changes:
- Uses the wreq HTTP client with browser-matching TLS fingerprints (ClientHello, ALPN, cipher order).
- Loads a tracker blocklist that drops requests to known analytics and fingerprinting endpoints.
- Bundles webpki roots instead of relying on the system store.
Requires a build that includes the stealth feature. Release binaries on the Releases page include it. To build it yourself:
cargo build --release --features stealth- Basic bot detection that checks TLS fingerprint or User-Agent.
- Sites that rely on third-party analytics being reachable.
- Cloudflare interactive challenges.
- Datadome and Akamai bot manager active challenges.
- CAPTCHAs.
- IP-based rate limiting (use proxies).
HTTP proxy:
obscura fetch https://example.com --proxy http://proxy.example.com:8080
obscura serve --proxy http://proxy.example.com:8080With auth:
obscura fetch https://example.com --proxy http://user:pass@proxy.example.com:8080SOCKS5:
obscura fetch https://example.com --proxy socks5://proxy.example.com:1080obscura fetch https://example.com --user-agent "Mozilla/5.0 (...) ..."
obscura serve --user-agent "Mozilla/5.0 (...) ..."Default UA matches a recent Chrome on the build platform.
obscura serve \
--stealth \
--proxy http://user:pass@proxy.example.com:8080 \
--user-agent "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 ..."