Making requests with Web Unblocker
Port: 9000. Take your exact username, password and host from
Web Unblocker → Proxy Access in the dashboard.
Your Web Unblocker username is your base proxy username with -wu appended.
Sending a request
Section titled “Sending a request”curl -x USERNAME-wu:PASSWORD@YOUR_HOST:9000 https://example.comimport requests
proxy = "http://USERNAME-wu:PASSWORD@YOUR_HOST:9000"r = requests.get( "https://example.com", proxies={"http": proxy, "https": proxy}, timeout=120,)print(r.text)import { HttpsProxyAgent } from 'https-proxy-agent';
const agent = new HttpsProxyAgent( 'http://USERNAME-wu:PASSWORD@YOUR_HOST:9000');const res = await fetch('https://example.com', { dispatcher: agent });console.log(await res.text());Country targeting
Section titled “Country targeting”Append -country- to the password, the same grammar the
proxy products use.
curl -x USERNAME-wu:PASSWORD-country-US@YOUR_HOST:9000 https://example.comCountry is the only targeting option here. City, ZIP, ASN and device OS are residential-pool features and have no meaning when we are choosing the exit for you.
Authentication
Section titled “Authentication”Username and password only. IP whitelisting is not supported, because the connection is terminated and re-originated rather than relayed.
Raise your timeouts
Section titled “Raise your timeouts”We may render the page and retry it several times before answering. Requests can take tens of seconds, and most default HTTP client timeouts are far shorter than that.
Set at least 120 seconds. A client that gives up early fails a request that was about to succeed, and the work is still billed.
Do not add your own retries first
Section titled “Do not add your own retries first”Web Unblocker already retries internally. Wrapping it in your own aggressive retry loop multiplies the work and the cost without improving the outcome.
If a target fails consistently, that is a signal to ask support rather than to retry harder.
Was this page helpful?
Thanks — that helps us fix it.