Which SOCKS5 clients does the command generator produce code for?+
cURL with --proxy, wget via torsocks, Python requests with the [socks] extra, Python aiohttp with aiohttp-socks, Node.js fetch with socks-proxy-agent, and Go net/http with x/net/proxy. Each tab emits a full working command or script pre-filled with your inputs.
How do I safely pass SOCKS5 credentials on the command line?+
Set credentials as environment variables (export PROXY_USER=...; export PROXY_PASS=...) and reference them in the URL: curl --proxy socks5h://$PROXY_USER:$PROXY_PASS@host:1080 https://target. This keeps plaintext credentials out of your shell history and out of process listings.
Do the generated commands work with rotating residential proxies?+
Yes. Rotating pools expose a single gateway host:port with credentials that carry session semantics (user-session-abc). Every request through the gateway rotates automatically. Paste the gateway credentials into the generator and the emitted command supports rotation with no changes.
Why does the generator default to socks5h:// instead of socks5://?+
socks5h:// forces DNS resolution to happen at the proxy exit, preventing your local ISP from seeing target hostnames. Local DNS leaks are the #1 source of soft blocks on modern anti-bot systems. There is no downside to socks5h for HTTP scraping.
How do I install the requests[socks] extra for Python?+
Run pip install 'requests[socks]' once. This pulls the PySocks package as a transitive dependency and enables the socks5:// scheme in requests. On Python 3.11+ the same command works unchanged inside virtualenvs and Poetry projects.
Can the generator produce a Playwright or Puppeteer SOCKS5 config?+
The generator focuses on HTTP clients where SOCKS5 is a single URL parameter. Browser automation requires launcher flags (--proxy-server=socks5://host:port for Chromium). Copy the host:port from the generator and pass it via launch options — auth flows through Chromium's HTTP_PROXY_AUTH prompt or a proxy-auth extension.
How do I add custom headers to the generated cURL command?+
Append -H 'Header: Value' to the emitted command. Common additions: -H 'User-Agent: ...', -H 'Accept-Language: en-US,en;q=0.9'. Combine with the Headers Inspector tool to match headers to your proxy exit country.
Are the generated commands compatible with older cURL versions?+
The --proxy flag with socks5h:// requires cURL 7.21.7 or newer (2011). Every modern OS ships with a newer version. On very old CentOS 6 or Ubuntu 12.04 systems, upgrade cURL first or fall back to the wget-via-torsocks tab.
How do I use the generated cURL command inside a bash loop for scraping?+
Wrap the emitted command in a for-loop and substitute the URL: `for url in $(cat urls.txt); do curl --proxy socks5h://$PROXY $url; sleep 1; done`. Keep the SOCKS5 credentials in $PROXY as an env variable so the command line stays readable and safe from process listings.
Can I generate a command that rotates User-Agents per request?+
The generator emits a single command with a static UA. For rotation, wrap the emitted curl call in a shell loop that picks a random line from a UA list and passes it via `-A`. For Python, use the random.choice() pattern over a UA pool inside the requests session.
Why does the Node fetch snippet require socks-proxy-agent instead of undici?+
Undici (Node's built-in fetch) supports HTTP/HTTPS proxies via ProxyAgent but does not implement SOCKS5. socks-proxy-agent bridges the SOCKS5 handshake into Node's http/https stack. Install with `npm install socks-proxy-agent` and pass the agent via the fetch dispatcher option.
Does the generator support HTTP CONNECT tunneling for HTTPS through SOCKS5?+
Yes — every emitted command handles HTTPS transparently. cURL, requests, aiohttp and socks-proxy-agent all wrap the target TLS handshake inside the SOCKS5 tunnel. You never need to configure CONNECT semantics manually; that's HTTP-proxy syntax, not SOCKS5.
How do I add timeout and retry logic to the generated commands?+
For cURL: `--connect-timeout 10 --max-time 30 --retry 3 --retry-delay 2`. For Python requests: `requests.get(url, proxies=..., timeout=(10, 30))` inside a try/except with a manual retry counter or the `tenacity` library. Bake these into a wrapper function once and reuse across the codebase.
Can I generate a Docker-friendly command that runs the request in a container?+
Yes — prefix the emitted command with `docker run --rm curlimages/curl` and pass the proxy env var via `-e PROXY_URL=...`. This is useful in CI environments where you don't want to install curl or Python locally but still need to route through a SOCKS5 exit.