An active CleanProxies plan
Static ISP proxies for fixed US IPs, or rotating residential / mobile proxies for pools. The $4.99 trial works too.
Set the proxy for one command with -e: wget -qO- -e use_proxy=yes -e https_proxy=http://USERNAME:PASSWORD@HOST:PORT https://api.ipify.org. Wget also reads the http_proxy and https_proxy environment variables and ~/.wgetrc. It has no SOCKS support, so use cURL for SOCKS5.
Wget is the standard tool for scripted downloads and mirroring on Linux servers. It supports HTTP(S) proxies with Basic authentication, which every CleanProxies product offers, but it only reads the lower-case proxy variables and has no SOCKS option at all.
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.
wget --version). Some newer Linux distributions install GNU Wget2 under the wget name; its credential flags differ (see Troubleshooting).Both products use the same setup in Wget. What changes is how long an IP stays with you.
Each wget run opens fresh connections, so a rotating line normally gives every run a new residential IP; within one --input-file run, files from the same host can share a connection and an IP. Use a sticky line when a series of downloads must finish on one IP.
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.
Each ISP line is one dedicated US IP, so every wget run through it exits from the same address all month. That suits scheduled downloads from sites that rate-limit or allow-list by IP.
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.
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 Wget.
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.
Take a rotating residential line, or an ISP line, from your CleanProxies dashboard.
Write it as http://USERNAME:PASSWORD@HOST:PORT, or keep http://HOST:PORT and pass the credentials as flags.
Run wget -qO- -e use_proxy=yes -e https_proxy=http://USERNAME:PASSWORD@HOST:PORT https://api.ipify.org. It prints the exit IP.
Export http_proxy and https_proxy, or put the settings in ~/.wgetrc.
Replace the highlighted placeholders with the values from your dashboard. Pick an example to see its code.
-e runs a .wgetrc command for this call only. use_proxy is already on by default; passing it makes the command work even if a wgetrc turned proxies off.
# credentials inside the proxy URL
wget -qO- -e use_proxy=yes -e https_proxy=http://USERNAME:PASSWORD@HOST:PORT https://api.ipify.org
# credentials as flags (safer for passwords with @ or :)
wget -qO- -e use_proxy=yes -e https_proxy=http://HOST:PORT \
--proxy-user=USERNAME --proxy-password=PASSWORD https://api.ipify.orgexport http_proxy="http://USERNAME:PASSWORD@HOST:PORT"
export https_proxy="http://USERNAME:PASSWORD@HOST:PORT"
export no_proxy="localhost,127.0.0.1"
wget -qO- https://api.ipify.orghttps_proxy for https:// URLs and http_proxy for http:// URLs, so set both. Both point to an http:// proxy URL; HTTPS downloads still run end to end through a CONNECT tunnel. --no-proxy skips the proxy for one command.use_proxy = on
http_proxy = http://HOST:PORT/
https_proxy = http://HOST:PORT/
proxy_user = USERNAME
proxy_password = PASSWORDwget -e use_proxy=yes -e https_proxy=http://USERNAME:PASSWORD@HOST:PORT \
--input-file=urls.txt --wait=1 --random-wait --tries=3 --timeout=30chmod 600 ~/.wgetrc.wget -qO- -e https_proxy=http://USERNAME:PASSWORD@HOST:PORT https://api.ipify.org; echo
wget -qO- --no-proxy https://api.ipify.org; echoGNU Wget supports HTTP(S) and FTP proxies only; there is no SOCKS option. Every CleanProxies product works with Wget over HTTP(S). If you specifically need SOCKS5, it's available on static ISP and ISP subnet proxies (switched on per proxy list in the dashboard, same username and password): send those requests with cURL and -x socks5h://USERNAME:PASSWORD@HOST:PORT.
api.ipify.org returns only the IP address. Run the test with and without the proxy flags and compare. Add -d (debug, if your build supports it) to see the CONNECT request and the proxy's reply.
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).
@ or : in the password breaking the proxy URL.Copy the line again, or pass the credentials with --proxy-user and --proxy-password.http_proxy is set, or the variables are upper case (Wget reads the lower-case names).Set lower-case https_proxy as well, or pass -e https_proxy=....use_proxy = off in a wgetrc, or the host matches no_proxy.Add -e use_proxy=yes and check env | grep -i proxy.wget is GNU Wget2, which doesn't implement --proxy-user.Use --http-proxy-user and --http-proxy-password, or put the credentials in the proxy URL; Wget2 also has --https-proxy.Setup guides and best practices from the CleanProxies blog.
Setup guides for tools people run next to Wget.
The -x flag, separate credentials, socks5h for remote DNS, env vars and a loop to test a whole list.
Setup guide--proxy per scheme, env vars, SOCKS5 with remote DNS, sessions on a fixed IP and default options.
Setup guideThe proxies dict, Session-level proxies, SOCKS5 with remote DNS and rotation over an ISP list.
Setup guidehttp_proxy variables in both cases, /etc/environment, apt config and the Ubuntu desktop panel.
Setup guideStraight answers about running CleanProxies in Wget.
No. GNU Wget supports HTTP(S) and FTP proxies only. Use the HTTP(S) form of your CleanProxies credentials with wget, or use cURL when you need SOCKS5, which CleanProxies offers on static ISP and ISP subnet proxies.