Proxy troubleshooting: 407, 429 and connection timeouts

When a proxy request fails, the fastest next step is usually to classify the failure. Replacing an IP, increasing concurrency and extending timeouts all at once removes evidence and can worsen the original problem. A 407 response, a 429 response and a connection timeout describe different situations and need different checks.

This guide gives a practical sequence for KAIROXO integrations: preserve the original result, identify the layer, change one setting, and run a small follow-up test. It applies to requests you are authorized to make. Use actual connection settings from the console, and compare against the authentication documentation and error guide rather than guessing gateway formats.

Start with a record you can compare

Pause parallel workers and reproduce the problem with one request to a small, authorized target. Record the UTC timestamp, protocol, redacted gateway configuration, target host, final HTTP status, curl exit code and elapsed time. Preserve the response headers when available. A network failure may produce no HTTP response at all, so do not turn every failure into an assumed website status.

Use the command below as a diagnostic shape, replacing all placeholders. It makes one attempt, saves the headers and body locally, and prints a short summary. The 10-second connection and 30-second transfer limits are example test values, not KAIROXO guarantees. On PowerShell, use curl.exe when necessary. Keep real credentials out of shared scripts and redact downloaded content before sharing it.

curl --proxy "http://PROXY_HOST:PROXY_PORT" --proxy-user "PROXY_USERNAME:PROXY_PASSWORD" --connect-timeout 10 --max-time 30 --silent --show-error --dump-header response-headers.txt --output response-body.html --write-out "status=%{http_code} total=%{time_total}s\n" "https://example.com/"