What the browser needs from you#
Every anti-detect browser has a proxy form per profile with the same fields: type (HTTP or SOCKS5), host, port, username, password. Fill them with the Proxy Cyber gateway and a sticky username, or with a dedicated ISP address for accounts that must never change IP.
| Field | Residential sticky session | Dedicated ISP address |
|---|---|---|
| Type | HTTP (or SOCKS5) | HTTP (or SOCKS5) |
| Host | res.proxy-cyber.com | the IP from your list |
| Port | 9000 (SOCKS5: 9001) | 8000 (SOCKS5: 8001) |
| Username | USER-cc-us-state-ny-sid-profile17-ttl-24h | from your list |
| Password | PASS | from your list |
One profile, one session id#
Use a distinct session identifier for each independent workflow, where the assigned gateway supports it. Confirm the permitted duration and location parameters in your connection details. A residential device can disconnect before the requested duration; a sticky session is not a guarantee of the same IP for days. For a fixed address, compare a dedicated static product. ISP proxy
Align the profile with the exit#
- Time zone and language of the profile = country and city of the exit.
- Geolocation permission, if enabled, near the exit's city.
- Keep WebRTC in the "replace with proxy IP" or "disabled" mode the browser offers.
- Test the profile's IP inside the browser before touching the account.
Which network for accounts#
| Situation | Network | Why |
|---|---|---|
| Many low-value accounts, daily activity | Residential sticky sessions | Cheap per account, natural daily IP change |
| Valuable accounts that must not change IP | ISP proxy, one per profile | Static, residential-registered, unlimited traffic |
| Platforms that challenge residential-grade IPs | Dedicated mobile device | Carrier IP, rotation on your command |
| Bulk checks without logins | Residential rotating | Breadth over consistency |
Import lists at scale#
Import only the actual proxy list assigned in your account. Match the receiving browser’s format, such as host:port:user:pass, and map each line to the intended profile. The account API currently reads account data and orders with GET /api/v1/me and GET /api/v1/orders; it does not provide a documented /v1/proxies?format=txt export endpoint.
res.proxy-cyber.com:9000:USER-cc-us-sid-p001-ttl-24h:PASS
res.proxy-cyber.com:9000:USER-cc-us-sid-p002-ttl-24h:PASS
res.proxy-cyber.com:9000:USER-cc-gb-sid-p003-ttl-24h:PASSQuestions people ask#
HTTP or SOCKS5 in the profile?
Either works. HTTP is the simplest and supports credentials everywhere; SOCKS5 is useful when the browser offers remote DNS through it. Never mix: pick one per profile.
The proxy check in the browser fails but cURL works.
Most often a stray space in a field or the wrong port for the type chosen (9001 is SOCKS5 only). Copy the four fields again from a working cURL line.