Skip to main content
If you have a specific error code, see Error codes. This page is for “something’s wrong” diagnostics.

Is the proxy down?

Check status.eclipseproxy.com first. Real-time incident updates live there.
  1. Proxy password reset? Old credentials return 407. Update all scripts.
  2. Wrong protocol/port? HTTP creds on SOCKS (or vice versa). Re-generate.
  3. Out of bandwidth? Check dashboard and top up.
  4. Target blocking? Test against api.ipify.org. If works, target is blocking that IP type.
  • Username typo? Re-generate from dashboard.
  • No inventory? Try -strict-off for fallback.
  • Target geolocates differently? Verify with curl -x ... https://ipinfo.io. If that shows right country but target disagrees, it’s target-side detection.
Measure with: curl -x http://USER:PASS@HOST:PORT -o /dev/null -s -w "%{time_total}\n" https://api.ipify.org (not ping).Common causes: some regions slower, target is slow, bandwidth exhausted, wrong product for use case.
  1. Check status page.
  2. Reset password or change tools?
  3. Test against api.ipify.org to isolate.
  4. Try different country or product.
Datacenter IPs expected to have high scores. For Residential/ISP, contact support with screenshot (IPQualityScore, Scamalytics) for replacement.
Check: wrong protocol, system-wide proxy interfering, WebRTC leak, or tool reusing connection. Use fresh session ID per request.

What to include when contacting support

  • Exact error message
  • Proxy string (mask the password)
  • Target URL (if shareable)
  • What you’ve already tried from this page
Cuts ticket resolution time in half.