The four connection details
| Field | Meaning |
|---|---|
| Host | The gateway hostname or IP address supplied for the proxy product. It is separate from the destination website. |
| Port | The proxy’s listening port. Use the supplied value; there is no universal proxy port. |
| Username | The proxy identity. Some providers encode location or session choices in it; the format is provider-specific. |
| Password | The proxy credential, separate from your website login password. |
HTTP, HTTPS and SOCKS5
The protocol in the proxy URL describes the connection to the proxy. It does not have to match the destination URL.
| Proxy URL scheme | How to read it |
|---|---|
| http:// | Connect to an HTTP proxy. An HTTPS destination normally uses a CONNECT tunnel through it. |
| https:// | Use TLS on the client-to-proxy connection. The proxy must explicitly support it. |
| socks5:// | Use SOCKS5. DNS resolution behavior depends on the client. |
| socks5h:// | In clients such as cURL and Requests, ask the SOCKS5 proxy to resolve the destination hostname. |
Keep certificate verification enabled. Change a scheme only when the provider supports that protocol on the selected port.
Common input formats
PROXY_HOST:PROXY_PORT
PROXY_HOST:PROXY_PORT:PROXY_USERNAME:PROXY_PASSWORD
http://PROXY_USERNAME:PROXY_PASSWORD@PROXY_HOST:PROXY_PORTSeparate host, port, username and password fields are easiest when your tool offers them. In a URL, percent-encode special characters in the username and password, including @, :, /, # and %. Do not encode the whole URL. The Python example handles credential encoding.
Authentication and allowlists
Username/password authentication identifies your proxy account on each connection. An IP allowlist, when a provider offers it, authorizes the public IP of the machine making the connection. A checker running on a server has a different source IP from your laptop.
Crawlhub does not currently offer proxy-user creation or IP-allowlist management. Follow your active provider’s settings for these features.
Keep credentials out of shared files
Keep real credentials out of Git, screenshots and support messages. Load them from your runtime’s secret configuration or an interactive prompt. Do not put proxy passwords in browser-delivered JavaScript.
Continue with Code examples for client-specific setup.