How to use Proxya proxies

Every proxy is four values: host, port, username and password. The order page gives them in the two formats tools normally expect, and can export the whole order as CSV.

HOST:PORT:USERNAME:PASSWORD
USERNAME:PASSWORD@HOST:PORT

Host,Port,Username,Password
203.0.113.10,8080,user12ab,9f3c1d7e
203.0.113.11,8080,user12ab,9f3c1d7e

Within one order the username and password are usually shared across the proxies — the host is what changes. Passwords are hidden by default on the page and revealed per row.

All types speak HTTP(S) and SOCKS5. Which port you use decides which one you get.

For ISP and datacenter the SOCKS5 port is simply the HTTP port plus one, with the same username and password. Nothing else changes.

For residential proxies the gateway port is what selects the protocol at generation time; port 5555 accepts both HTTP and SOCKS5 on the same endpoint.

curl -x socks5h://USER:PASS@HOST:PORT https://api.ipify.org

Use socks5h (not socks5) when you want DNS resolved on the proxy side — that is what you normally want for scraping.

There are two ways to authorise, and you pick per order.

Username and password

The default. Works from anywhere, which is what you need on rotating cloud workers or a laptop with a changing home IP.

IP whitelist

Add your server's address to the order's whitelist and traffic from it is accepted with no credentials at all. The field is pre-filled with the address we see you from, so whitelisting the machine you are sitting at is one click.

Whitelisted traffic arrives without a password — which also means it bypasses the layer that rewrites OS fingerprints. If you rely on OS spoofing, keep the whitelist empty and authenticate with a password.

Residential traffic is a pool of gigabytes on your account rather than a fixed list of IPs. You mint connection strings from it whenever you need them, in the dashboard under Buy → Residential → Generate.

Rotating is right for wide crawls where every request can come from somewhere else. Sticky is what you need for anything with a login, a cart or a multi-step form — the IP must not change halfway through.

Traffic is drawn from the same pool no matter how many strings you generate, so generating more of them costs nothing by itself.

A proxy hides your IP, but the TCP handshake still carries the signature of the machine behind it. Send a thousand connections from a hundred IPs that all look like the same Linux box and the pattern is trivial to spot.

ISP and datacenter orders can rewrite that signature: pick an OS profile in the order and connections start presenting the TCP/IP characteristics of that system instead of your own.

Spoofing only applies to password-authenticated traffic. As long as any address sits in the order's IP whitelist, that traffic goes around the p0f layer and the profile stays dormant.

MTProto orders are not host:port:user:pass — Telegram takes a link. The order page gives you the ready link and the secret separately.

https://t.me/proxy?server=HOST&port=PORT&secret=SECRET

Open the link on a device with Telegram installed and confirm the prompt, or paste the server, port and secret into Settings → Data and Storage → Proxy. The secret is fixed for the life of the order — there is nothing to rotate.

Replace HOST, PORT, USER and PASS with the values from your order.

Python — requests

import requests

proxy = "http://USER:PASS@HOST:PORT"
r = requests.get(
    "https://api.ipify.org?format=json",
    proxies={"http": proxy, "https": proxy},
    timeout=30,
)
print(r.json())

Python — a session for multi-step work

A session reuses connections, so through a login or a checkout the target keeps seeing the same IP and the same TLS handshake.

import requests

proxy = "http://USER:PASS@HOST:PORT"
s = requests.Session()
s.proxies = {"http": proxy, "https": proxy}

for url in urls:
    r = s.get(url, timeout=30)
    print(r.status_code, len(r.content))

Node.js — fetch via undici

Node 18 and newer ships fetch on top of undici, so the proxy is set once as a global dispatcher and every later call goes through it.

import { ProxyAgent, setGlobalDispatcher } from "undici";

setGlobalDispatcher(new ProxyAgent("http://USER:PASS@HOST:PORT"));

const res = await fetch("https://api.ipify.org?format=json");
console.log(await res.json());

Playwright — a real browser

import { chromium } from "playwright";

const browser = await chromium.launch({
  proxy: {
    server: "http://HOST:PORT",
    username: "USER",
    password: "PASS",
  },
});
const page = await browser.newPage();
await page.goto("https://api.ipify.org");
console.log(await page.textContent("body"));
await browser.close();

Scrapy

# settings.py
DOWNLOADER_MIDDLEWARES = {
    "scrapy.downloadermiddlewares.httpproxy.HttpProxyMiddleware": 110,
}

# spider
class Spider(scrapy.Spider):
    def start_requests(self):
        for url in self.urls:
            yield scrapy.Request(
                url,
                meta={"proxy": "http://USER:PASS@HOST:PORT"},
            )

407 Proxy Authentication Required

The credentials didn't match, or you are relying on the whitelist and connecting from an address that isn't in it. Check the username against the order page, and remember that a whitelist entry only covers the exact address you added.

The connection hangs or is refused

Most often it is the port. On ISP and datacenter orders SOCKS5 lives on the HTTP port plus one — pointing a SOCKS client at the HTTP port produces exactly this symptom.

The target returns 403 or 429

That is the site, not the proxy. In rough order of what helps: slow down and add jitter; switch from rotating to sticky sessions if the site tracks a journey.

On hard targets, move from datacenter to ISP or residential IPs — and on ISP or datacenter, turn on an OS profile so every connection stops carrying the same signature.

Check what the target actually sees

The IP checker on this site shows the address and geolocation of whoever asks, and the proxy checker tests a proxy string end to end. Both are free and need no account.

Per-proxy orders (ISP, datacenter, MTProto) run for the term you bought and show their expiry date on the order page. Renewal is manual — there is no silent auto-charge — and an expired order stops passing traffic.

Residential is a gigabyte pool instead of a term: it lasts until you use it up.

If the proxies don't work for your case, there is a 24-hour money-back window from purchase.