Check network connectivity, firewall rules, proxy host/port, ISP port blocking, and target availability. Set 10-15 second timeouts for residential, 5-10 for ISP.

Wrong credentials, expired password, URL encoding issues with special characters, wrong port, or suspended account. Copy credentials directly from dashboard and verify account status.

Anti-bot detection, flagged IP, unrealistic headers, high request rate, or blocked IP range. Use rotating residential proxies, add realistic headers, slow down, use headless browser for protected sites.

Geographic distance, residential proxy variability, network congestion, local bandwidth limits, concurrent overload. Try closer locations, upgrade to ISP for speed-sensitive tasks, enable connection pooling.

Expected behavior — websites serve localized content based on IP location. Also caused by A/B testing, caching differences, or anti-bot serving modified content. Target proxies in your home region if you need consistent content.

Silent blocks (200 status, empty body), SSL failures, firewall termination, timeouts, or encoding issues. Check status codes, test with cURL -v, verify gzip handling.

Usually client-side issues, not proxy-related. The CONNECT tunnel preserves direct SSL between client and target. Verify by accessing the URL directly without proxy.

Different sites have different security. Switch to residential proxies with realistic headers for anti-bot sites. Use correct geo-targeting for restricted sites. Use headless browser for JavaScript-heavy sites.

Step 1: test with cURL. Step 2: check network connectivity. Step 3: check proxy URL format in your app. Step 4: check environment variable conflicts. Step 5: enable verbose logging. Step 6: contact support.

Target updated defenses, IP pool flagged, configuration change, or network issues. Reduce rate, switch locations/sessions, verify headers, test manually.

Loading unnecessary resources, headless browser defaults, redirect chains, retry loops. Block images in headless browsers, use HTTP requests when possible, limit retries.

Wrong port, service temporarily down, IP blocked at network level, firewall rules, ISP port blocking. Verify host/port, try HTTP and SOCKS5 ports, try different network.

407 (auth failed), 403 (blocked), 429 (rate limited), 502 (bad gateway), 503 (unavailable), 504 (timeout), 520-530 (Cloudflare). 4xx = request issue, 5xx = server/proxy issue.

Through dashboard support center. Include account email, proxy type, target website, exact error, proxy config (without password), reproduction steps, and timing.

Check targeting syntax, verify with IP geolocation service. Ensure country codes are correct ISO format. Try country-level targeting if city-level has limited availability.