How to Use Dataimpulse SOCKS5 Proxies with curl on Linux

Overview

This tutorial shows how to route command-line HTTP traffic through Dataimpulse residential or mobile proxies over SOCKS5 on Linux. You will configure curl, verify the exit IP, run a small rate-limited batch fetch, and apply the same settings to other CLI tools.

Dataimpulse offers residential and mobile IPs over HTTP and SOCKS5 with pay-as-you-go billing, which makes it a reasonable fit for scripted, high-volume data collection. The techniques below are protocol-level and vendor-neutral: any SOCKS5 endpoint behaves the same way, and Dataimpulse is simply the provider used for the examples.

Prerequisites

• A Linux host (workstation, VM, or container) with a POSIX shell
• curl built with SOCKS5 support, plus jq for parsing JSON responses
• A Dataimpulse account with credit loaded
• The SOCKS5 endpoint host, port, username, and password from the Dataimpulse dashboard

Before you start

• Only collect data you are authorised to collect. Respect each target site's terms of service and robots.txt, and follow the laws that apply to you.
• Pay-as-you-go billing is metered by traffic, so retries, large responses, and media downloads all consume credit. Check the dashboard usage view while you test.

How the SOCKS5 endpoint works

SOCKS5 is a transport-level proxy protocol, so it carries HTTPS traffic without terminating TLS itself. Your client negotiates a TCP connection through the proxy, and the target's certificate is still validated end to end.

Two address forms matter in practice:

• socks5:// — your machine resolves the destination hostname, then sends the IP to the proxy.
• socks5h:// — the proxy resolves the hostname. This avoids local DNS leaks and is the better default for collection work.

Steps

1. Install the command-line tools

sudo apt update
sudo apt install -y curl jq

On Fedora or RHEL, use sudo dnf install -y curl jq. On Arch, use sudo pacman -S curl jq.

2. Confirm SOCKS5 support in curl

curl --help all | grep -i socks

You should see options such as --socks5, --socks5-hostname, --socks4, and --socks4a. If nothing is listed, your curl build lacks SOCKS support and needs upgrading before continuing.

3. Store your credentials in a restricted file

Create the file with owner-only permissions, then fill in the values from your Dataimpulse dashboard.

install -m 600 /dev/null "$HOME/.dataimpulse.env"

cat > "$HOME/.dataimpulse.env" <<'EOF'
export PROXY_HOST="your-endpoint-host"
export PROXY_PORT="your-socks5-port"
export PROXY_USER="your-username"
export PROXY_PASS="your-password"
EOF
chmod 600 "$HOME/.dataimpulse.env"

The quoted heredoc delimiter prevents the shell from expanding anything, so the file is written literally. Keep this file out of any repository you sync or publish.

4. Load the variables into your shell

source "$HOME/.dataimpulse.env"
printf 'Proxy endpoint: %s:%s\n' "$PROXY_HOST" "$PROXY_PORT"

Sourcing from a file keeps the password out of your command line, where it would otherwise be recorded in shell history and visible in process listings.

5. Send your first request through the proxy

curl --socks5-hostname "${PROXY_HOST}:${PROXY_PORT}" \
     --proxy-user "${PROXY_USER}:${PROXY_PASS}" \
     --silent --show-error --max-time 30 \
     "https://api.ipify.org?format=json"

The single-URL form is equivalent and easier to template into scripts:

curl --proxy "socks5h://${PROXY_USER}:${PROXY_PASS}@${PROXY_HOST}:${PROXY_PORT}" \
     --silent --show-error --max-time 30 \
     "https://api.ipify.org?format=json"

A JSON response containing an IP address that differs from your own confirms the request went through the proxy.

6. Verify rotation and exit location

for i in 1 2 3; do
  curl --proxy "socks5h://${PROXY_USER}:${PROXY_PASS}@${PROXY_HOST}:${PROXY_PORT}" \
       --silent --show-error --max-time 30 \
       "https://api.ipify.org?format=json" | jq -r '.ip'
done

Different addresses on each request mean the endpoint is rotating between connections. If you see the same address every time, check the session settings in the Dataimpulse dashboard and its documentation for how a fixed versus rotating exit is selected for your account.

7. Fetch a real page and record the response code

curl --proxy "socks5h://${PROXY_USER}:${PROXY_PASS}@${PROXY_HOST}:${PROXY_PORT}" \
     --silent --show-error --location --max-time 60 \
     --output page.html \
     --write-out 'status=%{http_code} bytes=%{size_download}\n' \
     "https://example.com/"

--write-out reports the status code and byte count without a second request, which helps you correlate traffic spend with actual results.

8. Run a rate-limited batch fetch

Create a script named fetch-through-proxy.sh:

#!/usr/bin/env bash
set -euo pipefail

source "$HOME/.dataimpulse.env"
PROXY="socks5h://${PROXY_USER}:${PROXY_PASS}@${PROXY_HOST}:${PROXY_PORT}"

mkdir -p out
: > out/status.log

while IFS= read -r url; do
  [ -z "$url" ] && continue
  name="$(printf '%s' "$url" | sha256sum | cut -c1-12)"
  code="$(curl --proxy "$PROXY" \
               --silent --show-error \
               --location --max-time 60 \
               --retry 2 --retry-delay 5 \
               --output "out/${name}.html" \
               --write-out '%{http_code}' \
               "$url")" || code="error"
  printf '%s\t%s\n' "$code" "$url" | tee -a out/status.log
  sleep 2
done < targets.txt

Make it executable and give it a target list:

chmod +x fetch-through-proxy.sh
printf '%s\n' "https://example.com/" "https://example.org/" > targets.txt
./fetch-through-proxy.sh

One line of output per URL is written to out/status.log, and the delay between requests keeps you within the target's acceptable request rate. Adjust sleep to match each site's expectations rather than removing it.

9. Apply the proxy to other CLI tools

• Environment variables. export ALL_PROXY="socks5h://user:pass@host:port" is honoured by curl and some libraries, but not every program. Some tools expect HTTPS_PROXY and HTTP_PROXY instead, so set those too if needed, and remember the values apply to every command in that shell session.
• proxychains-ng. This wrapper forces arbitrary TCP programs through a SOCKS proxy. Add a socks5 host port entry to /etc/proxychains.conf or ~/.proxychains/proxychains.conf, then prefix commands with proxychains4. Authentication syntax varies between builds, so confirm your version's configuration format before relying on it for credentialed endpoints.
• Tools without SOCKS support. GNU wget, for example, does not speak SOCKS. Run such tools through proxychains-ng, or switch that workload to an HTTP proxy endpoint, since Dataimpulse supports HTTP as well as SOCKS5.

10. Tidy up when the run is finished

unset PROXY_PASS PROXY_USER

• Delete ~/.dataimpulse.env if you no longer need it, or leave it at mode 600 for the next session.
• Remove any command from your shell history that accidentally contained the password in plain text.

Troubleshooting

Summary

You configured a Linux shell to send requests through the Dataimpulse SOCKS5 endpoint, verified rotation with an IP echo service, captured response codes and byte counts, and ran a rate-limited batch job. Prefer socks5h:// so DNS resolves at the proxy, keep credentials in a mode 600 file instead of on command lines, and reach for proxychains-ng when a tool cannot speak SOCKS5 itself. Because billing is pay-as-you-go by traffic, watch the dashboard while you tune delays and retries.