Skip to main content
Anti-detect (multi-account) browsers need one proxy per profile to give each account its own IP. EclipseProxy works with all major ones.
  • Per-account dedicated IP → ISP (Social Media category) or Mobile
  • Throwaway accounts → Residential sticky
  • Bulk profiles where datacenter is acceptable → Datacenter IPv4

​
General setup (any anti-detect browser)

In the profile’s proxy settings:
  • Protocol: HTTP (works in all) or SOCKS5
  • Host: from your generator (e.g., core.eclipseproxy.com for Residential, 185.10.122.178 for ISP)
  • Port: the HTTP or SOCKS port for your product
  • Username: full username including geo and session segments
  • Password: your account proxy password
  1. New profile → Proxy → Add proxy
  2. Type: HTTPS or SOCKS5
  3. Host, port, username, password from generator
  4. Test before saving
  1. Profile settings → Proxy
  2. Type: HTTP / HTTPS / SOCKS5
  3. Paste credentials
  4. Check to verify
  1. Profile → Connection → Proxy
  2. HTTP or SOCKS5
  3. Credentials
  4. Test connection
  1. Profile → Proxy settings
  2. Select protocol
  3. Enter credentials
  4. Verify
  1. New profile → Proxy
  2. HTTP or SOCKS5
  3. Credentials
  4. Refresh IP info
  1. Profile → Proxy
  2. Custom proxy
  3. Credentials
  4. Save

​
Common issues

Check: wrong protocol (HTTP creds on SOCKS port), system-wide proxy interfering, or WebRTC leak. Enable the browser’s WebRTC blocker.
ISP IPs are dedicated. If changing, you may have Residential (rotating) configured instead. Verify: ISP uses an IP address, Residential uses core.eclipseproxy.com.
Each session ID should map to a different IP. If using ISP across many profiles, you need multiple IPs. Or use Residential with per-profile session IDs.
Proxy + anti-detect reduces detection but doesn’t eliminate it. Also check: timezone/language matching IP geo, WebRTC fully blocked, natural behavior. For maximum trust, use Mobile.