Residential setup

Residential is the most flexible product, with the most setup options. This page covers all of them.

Generator

Unified Proxy Generator — select Residential as the product.

Gateways

Pick the gateway closest to your traffic source.

Ports

On 3030 / 2020 a username with a -session- segment is sticky and one without is rotating. The per-mode ports still work: on them the port decides, and a -session- segment on a rotating port is ignored.

Format

Two equivalent formats:

core.eclipseproxy.com:10000:eclipse_yourname-country-kh-state-phnompenh-asn-38901-session-OaUE4kFO-lifetime-30:your_password_here

http://eclipse_yourname-country-kh-state-phnompenh-asn-38901-session-OaUE4kFO-lifetime-30:[email protected]:10000

For SOCKS5, swap http:// for socks5://.

Username segments

The username encodes all your targeting and session settings, joined with -:

eclipse_yourname             ← account
-country-kh                  ← country (ISO 3166-1 alpha-2)
-state-phnompenh             ← state (lowercase, no spaces)
-asn-38901                   ← ISP, by ASN (needs a country; Vega network only)
-session-OaUE4kFO            ← sticky session ID
-lifetime-30                 ← lifetime in minutes
-pool-vega                   ← network (optional, always last)

All segments after the account name are optional. The minimum valid username is just your account name. Segments the gateway doesn't know are ignored.

Targeting

Country

ISO 3166-1 alpha-2 codes: us, gb, de, fr, it, es, br, in, kh, etc.

We cover 213 countries and territories. The dashboard generator dropdown is the source of truth for what's currently available.

-country-us

State / region

Lowercased, no spaces. -region- is accepted as an alias of -state- (the generator emits -region-):

-country-us-state-california
-country-kh-state-phnompenh

City

Lowercased, no spaces:

-country-us-city-losangeles

State OR city: not both

You can target either state OR city, not both at the same time. This is a pool-level constraint.

-country-us-state-california                 ✓
-country-us-city-losangeles                  ✓
-country-us-state-california-city-losangeles ✗

ISP (ASN)

Target one ISP inside a country by its autonomous system number:

-country-us-asn-7018
-country-us-state-texas-asn-7018

• Needs a country. An -asn- on its own is refused (HTTP 503, SOCKS5 network unreachable): it is never silently widened to "any ISP".
• AS7018 and 7018 are both accepted.
• Vega only. ISP targeting is available on the Vega network alone. You don't need to add -pool-vega yourself: an ISP-targeted request is routed there automatically. Pinning a different network together with an -asn- leaves nothing that can serve the request, and it is refused.
• In the dashboard generator, pick a country first, then the ISP under Advanced Options → ISP. The list shows the ISPs available for that country, and the Network control is pinned to Vega while an ISP is selected.

Sticky vs rotating

Sticky session syntax

-session-abc123-lifetime-30

• Same session-abc123 returns the same IP across requests
• After lifetime-30 minutes, the session expires
• Different session IDs return different IPs
• -sesstime- is accepted as an alias of -lifetime- (the generator emits -sesstime-)

Lifetime values

Common: 1, 5, 10, 30, 60, 120, 1000 minutes (1000 is the maximum).

For sticky beyond a few hours, the upstream residential IP may rotate before lifetime expires (out of our control). For guaranteed stability, use ISP.

"Why does session ID change when I change lifetime?"

The dashboard generator regenerates a random session ID alongside any change. They aren't linked: to keep the same session ID with a different lifetime, copy the session ID manually.

Choose a network

By default Eclipse picks the best available network for every request. If you want to stay on one, add -pool- and a network code to the end of your username:

acme-country-us-pool-vega

You can allow more than one by separating them with a comma, and Eclipse will use whichever is best at the time:

acme-country-us-pool-orion,vega

Sticky sessions stay on the network they started on. Leave the code out to go back to automatic.

Rules:

• -pool- must be the last segment in the username. Anything after it is read as part of the network code and the request fails.
• Only the codes above are accepted. An unknown code is refused (HTTP 503 Service Unavailable, SOCKS5 network unreachable), never silently redirected, so a typo shows up immediately in testing.
• A pinned network that can't serve what the rest of the username asks for (an -asn- on anything but Vega, a feature the network lacks) is refused the same way.
• In the dashboard generator, tick the networks you want under Advanced Options → Network. Tick more than one to allow a mix; tick Automatic to clear them.

Authentication

User:pass (default) or IP whitelist. See Authentication.

Pool basics

• ~2.3 million IPs online at any one time, across 213 countries
• Pool changes constantly as residential users come online/offline
• Threads unlimited on Residential
• GB you buy never expires

Things to watch for

• "All my generated proxies look the same": normal for rotating; each connection rotates at the gateway
• "Wrong country IP": usually a username typo or no inventory for that city; verify with curl -x ... https://ipinfo.io. See Wrong country IP
• "City has no inventory": broaden to state or country
• "503 / network unreachable": nothing can serve that username. Check the -pool- code, add a -country- to any -asn-, and drop a non-Vega pin when targeting an ISP. See Error codes
• "Protocol mismatch error": using HTTP creds on SOCKS port or vice versa; re-generate with correct port