An active CleanProxies plan
Static ISP proxies for fixed US IPs, or rotating residential / mobile proxies for pools. The $4.99 trial works too.
On Linux, set the proxy with environment variables: export https_proxy=http://USERNAME:PASSWORD@HOST:PORT and the same for http_proxy. Add them to /etc/environment to make them permanent, and give apt its own line in /etc/apt/apt.conf.d/. On Ubuntu desktop, Settings → Network → Network Proxy covers GNOME apps.
Linux has no single proxy switch: command-line tools read environment variables, apt has its own config, and the desktop has a GNOME setting. Set the layers you need and the server or workstation leaves from a dedicated CleanProxies static ISP IP, which suits long scraping jobs on unlimited bandwidth.
Static ISP proxies for fixed US IPs, or rotating residential / mobile proxies for pools. The $4.99 trial works too.
From the dashboard's proxy manager: host (or IP), port, username and password. Convert lists with the proxy list formatter.
curl --version.Both products use the same setup in Linux. What changes is how long an IP stays with you.
A dedicated US ISP IP with unlimited bandwidth and threads, the same address all month: right for servers and long jobs. Whitelist the server's public IP and drop the credentials from every URL, or use SOCKS5 with socks5h://.
Dedicated static IPs registered to US and Canadian ISPs. The address stays the same for as long as you hold it, with unlimited bandwidth and HTTP(S) or SOCKS5 access.
Put a rotating residential line in the variables for a new IP per connection, or a sticky line (5 to 60 minutes or 24 hours) when a job keeps a session. Residential is HTTP(S) with username and password only.
Residential IPs in 190+ countries with country, state and city targeting. Rotate on every request or hold a sticky session for up to 90 minutes; GB never expire.
Every product connects over HTTP(S); static ISP and ISP subnet proxies also run SOCKS5 and IP whitelisting. This is what the dashboard gives you to paste into Linux.
IP:PORT:USER:PASSOne line per dedicated IP. With IP whitelisting on, the line is just IP:PORT and no password is sent.
HOST:PORT:USER:PASSGenerated in the proxy manager. The username carries the location and session you pick, so generate a new list to change them.
http://USERNAME:PASSWORD@HOST:PORTsocks5://USERNAME:PASSWORD@HOST:PORTUse http:// even for HTTPS websites; the TLS session still runs end to end. The socks5:// form is for static ISP and ISP subnet proxies.
Four steps, then check the exit IP with the free proxy checker.
In your shell run export https_proxy=http://USERNAME:PASSWORD@HOST:PORT and export http_proxy= with the same URL, plus the uppercase HTTPS_PROXY and HTTP_PROXY, because tools differ in which case they read.
Run curl -s https://api.ipify.org. The address printed should be your CleanProxies IP.
Add the lines to ~/.bashrc (or ~/.zshrc) for your user, or to /etc/environment for every user; the latter applies at the next login.
apt reads its own Acquire::http::Proxy line. On Ubuntu desktop, open Settings → Network → Network Proxy, choose Manual and enter the host and port for GNOME apps.
Replace the highlighted placeholders with the values from your dashboard. Pick an example to see its code.
Set both cases: curl reads only lowercase http_proxy (and either case for the others), while some other tools read only uppercase. no_proxy lists hosts that go direct, separated by commas.
export http_proxy="http://USERNAME:PASSWORD@HOST:PORT"
export https_proxy="$http_proxy"
export HTTP_PROXY="$http_proxy"
export HTTPS_PROXY="$http_proxy"
export no_proxy="localhost,127.0.0.1"
export NO_PROXY="$no_proxy"
curl -s https://api.ipify.orghttp_proxy="http://USERNAME:PASSWORD@HOST:PORT"
https_proxy="http://USERNAME:PASSWORD@HOST:PORT"
HTTP_PROXY="http://USERNAME:PASSWORD@HOST:PORT"
HTTPS_PROXY="http://USERNAME:PASSWORD@HOST:PORT"
no_proxy="localhost,127.0.0.1"/etc/environment is not a shell script: one KEY=value per line, no export and no $variables. Percent-encode @ or : in a password (@ becomes %40). With an ISP proxy on SOCKS5, socks5h://USERNAME:PASSWORD@HOST:PORT works for curl and other tools that support it.apt reads http_proxy when you run it in the same environment, but sudo drops most variables. A file in /etc/apt/apt.conf.d/ makes apt use the proxy no matter how it's started.
Acquire::http::Proxy "http://USERNAME:PASSWORD@HOST:PORT/";
Acquire::https::Proxy "http://USERNAME:PASSWORD@HOST:PORT/";sudo nano /etc/apt/apt.conf.d/95proxy, then run sudo apt update. For one-off commands, sudo -E apt update keeps your exported variables instead.curl -s https://api.ipify.orgfetch and many compiled programs don't read them by default.Run the command below with the variables set, then once with env -u http_proxy -u https_proxy -u HTTP_PROXY -u HTTPS_PROXY in front of it. The first prints your CleanProxies IP, the second your own.
Open What is my IP? through the proxy to see the address and headers a website receives, or paste up to ten lines into the free proxy checker to test connectivity, latency and exit IP.
Still stuck? Our 24/7 support team answers fast: contact us with the error and the line you used (leave the password out).
HTTP_PROXY is set, which curl doesn't read for http:// URLs.Set lowercase http_proxy and https_proxy as well.sudo -E, put the lines in /etc/environment, or configure the tool (apt, Docker) with its own proxy setting.@, : and # in the password, or whitelist your IP on an ISP proxy and use http://IP:PORT./etc/environment and ~/.bashrc are read at login or when a shell starts.Log out and in again, or open a new terminal (source ~/.bashrc for the current one).Setup guides and best practices from the CleanProxies blog.
Setup guides for tools people run next to Linux.
The -x flag, separate credentials, socks5h for remote DNS, env vars and a loop to test a whole list.
Setup guideOne-off -e flags, proxy credentials, env vars, ~/.wgetrc and bulk downloads through a rotating line.
Setup guideProxies inside containers (config.json, Compose), build-time args, and the daemon or Docker Desktop proxy.
Setup guideSystem Settings proxies per network service, password option, bypass list and networksetup.
Setup guideStraight answers about running CleanProxies in Linux.
On the desktop, open Settings, Network, Network Proxy and choose Manual. For the terminal and servers, export http_proxy and https_proxy in your shell or add them to /etc/environment, and give apt its own Acquire::http::Proxy line.