Skip to content
residential proxiesproxy setupsticky sessions

How to Connect a ProxyLabs Residential Proxy

The residential gateways, username order, and sticky lengths ProxyLabs actually uses. Copy the finished string from your dashboard.

A residential plan is ready once the dashboard shows a line you can paste. The line is host:port:username:password. This page is the map of that line. The copy button in the dashboard is the source you should paste into a tool. To check that line before you rely on it, use how to test a proxy before you pay.

The two gateways

Residential traffic uses port 8080.

Country code on the usernameGateway
us, ca, mx, br, ar, co, cl, peus.proxylabs.app:8080
Every other code, including gb, de, jp, au, and hkeu.proxylabs.app:8080

Pick the gateway for the country code in the username. A United States session belongs on us.proxylabs.app. A United Kingdom session uses -country-gb on eu.proxylabs.app. Japan, Australia, and Hong Kong use that same Europe gateway.

Rotating

Leave the username as the dashboard issued it. Each request can take a new address.

bash
curl -x http://USERNAME:[email protected]:8080 https://example.com

Sticky sessions

A sticky session keeps one address for a time you choose: 10, 30, 60, or 120 minutes. The dashboard writes that length in seconds, then a session id:

MinutesSeconds in the username
10600
301800
603600
1207200

The parameter order is country, then region, then city, then -ttl-, then -session-.

text
eu.proxylabs.app:8080:USERNAME-country-gb-ttl-3600-session-ab12cd:PASSWORD
us.proxylabs.app:8080:USERNAME-country-us-ttl-3600-session-ab12cd:PASSWORD

The same shape as a URL:

bash
curl -x http://USERNAME-country-gb-ttl-3600-session-ab12cd:[email protected]:8080 https://example.com

-ttl- is how long the address is held. It is a lifetime, measured from the start of the session. A new session id is a new address. Reusing the session id inside the TTL keeps the address.

HTTP and HTTPS through this port are the setup to use for scraping. SOCKS5 is available on the same gateways when a tool asks for it.

Country, region, and city

Add only the parts you need, in this order:

text
USERNAME-country-us-region-ny-city-newyork-ttl-1800-session-ab12cd

City and region slugs are the ones the dashboard offers. Generate the line there when you need a city, and paste that line.

Where this sits next to the other products

Residential bandwidth is billed per GB. The list price is £2.50/GB. It is £1.00/GB from 5,000 GB and £0.95/GB from 10,000 GB. Purchased data stays on the plan until you use it. Card, PayPal, and crypto all work. A £1 trial is 0.5 GB.

Residential proxies is the page to buy from. Rotating vs sticky is the page for choosing a session length.

Dedicated ISP proxies are a different product: a static address, billed per IP per month, copied from the dashboard as ip:port:username:password. Read dedicated ISP proxies.

Mobile proxies use mobile-eu.proxylabs.app and mobile-us.proxylabs.app. Read mobile proxies.

Lines that fail

These are the mistakes that produce a timeout or the wrong country. The dashboard copy button avoids all four.

What was pastedWhat happens
-country-ukThe United Kingdom code is gb.
us, ca, mx, br, ar, co, cl, or pe on eu.proxylabs.appThose eight codes use us.proxylabs.app. Every other country uses eu.proxylabs.app.
city-NewYork, or a city you typed yourselfThe slug is lowercase, and it has to be one the dashboard lists. New York is region-ny and city-newyork, in that order, after the country.
The same session id after the ttlThe clock started at the first request. Reusing the id does not add time. A new id is a new address.

An address that has to be the same address tomorrow is not a longer ttl. It is a dedicated ISP proxy.

Useful guide? Share it with your team.

Share
← Back to all articlesBack to top ↑
All articles ↗
residential proxies

Why your residential proxy still gets blocked on Akamai and Cloudflare sites

A residential exit can be clean and still meet a block page. The address, the TLS handshake, and the challenge script are three separate checks.

6 min read
cURL

How to Set Up a Proxy with cURL (Every Option Explained)

Complete cURL proxy reference: HTTP, HTTPS, SOCKS5, authentication, geo-targeting, and troubleshooting. Every flag and option with working examples.

8 min read
proxies

Proxy Authentication: IP Whitelist vs User/Pass vs API

Compare proxy authentication methods: IP whitelisting, username/password, and API tokens. Covers security trade-offs, setup complexity, and when to use each.

7 min read