Start with one request
- Check the host, port and protocol against the provider’s connection details.
- Try one request with the cURL example or the checker.
- Confirm the exit IP before testing a specific website.
- Record the exact error, time and whether the failure occurred locally or in the checker.
Common connection problems
| Symptom | What to check |
|---|---|
| 407 / authentication_failed | Use proxy credentials rather than your dashboard login. Check URL encoding and provider-specific username parameters. If using an allowlist, check the source machine’s public IP. |
| dns_error | Confirm the proxy hostname is spelled correctly and is public. Verify that it resolves from the machine running the client. |
| connection_failed | Check the port, protocol, firewall and provider availability. Try one known-good endpoint from your provider. |
| timeout | Test without an optional target first. In the checker, increase the timeout up to 15 seconds. Avoid retrying an entire batch repeatedly. |
| tls_error | Check the hostname, system clock and certificate trust. Do not disable TLS verification or install an unknown certificate as a shortcut. |
| blocked_address / invalid_proxy | Use a valid public proxy address. The checker rejects internal networks, unsupported protocols, URL paths and email-service ports. |
| check_failed | The proxy did not return a usable exit-IP response. It may be unable to reach the verification destination or may be returning an intermediary page. |
The proxy works, but the website does not
A target’s 403 means it refused that request; it does not identify a single cause. A 429 means a rate limit was reached. Check where the response came from: the Crawlhub checker, your proxy provider or the destination.
Respect any Retry-After value, reduce concurrency and use bounded retries for temporary failures. Do not keep retrying invalid credentials. A successful HTTP status can still contain an error page, so inspect the content.
Local and checker results differ
The source IP, network route, DNS behavior and timeout may differ. Provider allowlists can permit your laptop but reject our checker. With rotation, two requests may also use different exit IPs. Compare the same protocol and target with the same session settings.
Account or email trouble
For an expired confirmation or recovery link, request a new one and use the newest message. For a pending email change, confirm both inboxes. See Your account for the steps.
Send a useful support request
Send a message or email hello@crawlhub.ai. Include your product, client and version, protocol, timestamp with timezone, error code and a sanitized example.
Remove proxy passwords, API keys, cookies, access tokens and sensitive URL parameters before sending logs. We reply by email; no response-time guarantee is published.