ECHOALL / TROUBLESHOOTING

Troubleshoot proxy errors

Investigate authentication errors, timeouts and mismatched results. Identify the failing step before retrying or changing settings.

Maintained by EchoAll · Updated 2026-10-28
01 / Authentication / 407

Verify proxy authentication before changing platforms

HTTP 407 means the proxy requires authentication. SOCKS authentication uses its own protocol and may not produce an HTTP code.

  1. Verify host, port, protocol, username and password. Test one proxy first to isolate list-format problems.
  2. URL-encode special characters such as @, : and # in credentials, or fill the separate fields in Add proxy.
  3. For IP allowlists, the provider must allow the checker server’s actual outbound IP, not just your device IP. Confirm that address with the deployment operator.

Failed proxy authentication does not prove the target platform restricted the exit.

Reference: MDN · HTTP 407 ↗
02 / Timed out

Separate a failed connection path from one slow platform

A timeout means the request did not finish within this probe’s wait period. It does not prove an unsupported region or a blocked IP.

  1. Compare exit IP and other platforms. If every check fails, verify proxy uptime, port and credentials first.
  2. If one platform fails, retry that item later. The platform, route or a temporary network issue may be involved.
  3. Compare with the local Agent. Server and local probes start from different networks.

For repeated failures, record the time, platform and redacted error before contacting the provider or maintainer.

03 / Connection / protocol

Match the address and protocol to the actual service

Name-resolution failures, refused ports and protocol mismatches can all fail before a platform restriction is evaluated.

  1. Check spelling, spaces and punctuation in the host. Ports must be 1–65535.
  2. Use the protocol explicitly supported by the provider, such as socks5:// or http://. Do not infer it from the port alone.
  3. 127.0.0.1, localhost and private addresses refer to the request origin’s network. The web server cannot use them to reach a proxy on your device; use the Agent for local proxies.

Investigate TLS errors by checking protocol, hostname and service configuration. Disabling certificate verification is not a routine fix.

Reference: curl · Proxy protocols ↗
04 / Restricted / inconclusive

Handling restricted or inconclusive results

Restricted indicates a restriction for the current exit in this check. Inconclusive means no clear conclusion is available.

  1. Retry the item later and confirm login and actual use separately.
  2. A region signal does not guarantee account access. Subscription, eligibility, device and live policies can affect use.
  3. If the service works while this tool is inconclusive, send the platform, time and redacted result to help the maintainer investigate.

The AI topic page provides platform checks and a results guide.

05 / Local vs server

The same proxy configuration can still take different paths

Server probes start at EchoAll’s deployment. Local deep checks start on the device running the Agent. Browser routing is a separate environment.

  1. Compare the same proxy and platform at similar times to reduce noise from node changes and temporary failures.
  2. Check authentication allowlists, device routing and proxy chains. Rotating proxies can assign different exits to different connections.
  3. Use the local Agent for DNS, TCP and SNI diagnostics; homepage server-side checks do not provide these local diagnostics.

The IP seen when opening EchoAll does not establish the exit used by every other platform.

Retest after checking the configuration

Retest one proxy first. Remove credentials before sharing results; do not publish raw proxy configurations.

Optional visit analytics

Analytics is unavailable in this local demo.