ScrapingAutomationProxies

Camoufox Proxy Setup: geoip, Sticky Sessions & Residential IPs (2026)

AE
Engineering desk
Published
October 10, 2026
Reviewed by
Read Time
6 min read
Rotating gateway changes the exit after launch while sticky session keeps timezone, language, and WebRTC on one IP

A Camoufox proxy is the Playwright-style proxy dict you pass when the browser launches, plus geoip=True. Camoufox’s geoip page says the flag, or an explicit target IP, uses that IP’s longitude, latitude, timezone, country, and locale, spoofs the WebRTC address, and picks a browser language from the distribution of speakers in the region. Those values are configured at launch. The page does not describe updating them while the browser is already running, and it does not document a fallback if the lookup fails. Checked against that page on 10 October 2026.

The dict has three keys: server, username, and password. The login does not belong inside the server URL. Keeping the hostname at proxy.aethyn.io does not keep the household IP. The session id on the username is what holds the exit that geoip just read. The handshake itself is covered in TLS fingerprinting for scrapers. Launch versus context on stock Playwright is the Playwright residential guide.

Quick setup

Server, username, password, and geoip on; a pasted user:pass URL is rejected
Camoufox’s geoip examples pass server, username, and password as separate keys. A login embedded in the server string is the 407 path.

Install the extra that downloads the lookup database, then launch with an HTTP proxy. Premium is proxy.aethyn.io:2099. Elite is port 5499 when the username needs a supported city or ISP. Replace aethyn-XXXXX and PASSWORD from the dashboard.

Code Snippet
pip install -U "camoufox[geoip]"
Code Snippet
from camoufox.sync_api import Camoufox

with Camoufox(
    geoip=True,
    proxy={
        "server": "http://proxy.aethyn.io:2099",
        "username": "aethyn-XXXXX-country-us-session-fox1-lifetime-30",
        "password": "PASSWORD",
    },
) as browser:
    page = browser.new_page()
    page.goto("https://api.ipify.org")
    print(page.content())

Camoufox documents this shape with an http:// server. Keep that. Authenticated SOCKS5 is a known Chromium Playwright limit. Camoufox is a Firefox build, and this page does not claim that build accepts or rejects SOCKS5 authentication. The ports, if you need them later, are on the protocol list.

Verify the exit

Read the IP page before the real target. The country in that response should be the country on the username. If it is not, close the browser and launch again with a different session id. Do not continue into the target on a lookup that already disagrees with the job.

One browser, one sticky session

Launch looks up the exit, pages stay on it, the next browser gets a new session
Pages inside one browser share the launch exit. A new Camoufox() call does not rotate that exit by itself. The session id on the username does.

A new browser launch is a new browser identity. The proxy exit depends on the session token in the username. Use a new session id when you need a separate exit, and keep the previous id’s lifetime in mind: reusing a session id inside its sticky window can return the same exit IP. That reuse is the right retry for the same job and the wrong identity for a second one. Omitting -session- asks the gateway for a fresh exit on the next connection. That is the rotation to keep out of a browser that has already taken its geoip snapshot.

Open the browser, let geoip run, then do the pages that belong to that identity inside the with block. Pagination, a consent click, and a second URL on the same site stay there so cookies and the looked-up WebRTC address stay on one household. When the identity is finished, leave the block. That closes the browser. The next identity is another Camoufox(...) call with -session-fox1 changed to -session-fox2.

On Aethyn the hold is 1–1440 minutes, and the default is 30 if you omit -lifetime-N. Encode it on the username and make it at least as long as the browser stays open. Sticky residential proxies are a hold on a rotating-pool IP, not a dedicated static address. The targeting docs pin an exit only inside that window. When the lifetime expires, the next connection on that session id can draw a new household. The open browser still has the first timezone, language, and WebRTC address. Close it and start a new lookup. Do not assume the IP stays nailed up after the timer.

City and ISP tokens belong on Elite, and only when the targeting reference says the token is supported. Premium is country. On Elite, a city that does not match falls back to the country. Check targeting before you promise a metro in the scraper.

Timezone, language, and WebRTC

Matched browser keeps exit, WebRTC, timezone, and language together; a drifted browser does not
The drifted pane still shows the first WebRTC address after the exit IP has moved. geoip does not repair that mid-browser.

Some bot-management systems may compare network and browser signals, including IP geolocation, timezone, language, and WebRTC-related information. A mismatch can contribute to an inconsistent browser identity. Which signals are used, and how much they matter, varies by destination. A US exit with a browser still configured for another region is that kind of mismatch. It is a different signal from a datacenter ASN, and a mismatch on its own is not proof the destination will block the session.

geoip is supposed to derive the coordinates, timezone, locale, and WebRTC address from the IP it was shown, and to choose a language from speakers in that region rather than from one fixed locale. It can only do that for the IP it saw at launch. If you also pass a locale or timezone, it has to be the place the sticky exit actually is. Guessing America/New_York on a Chicago exit fights the lookup. Let geoip read the exit, then leave those fields alone for that browser.

The published geoip page does not document what Camoufox does when the lookup fails. If the launch does not produce an exit you can read, treat it as a failed start and launch again. Do not fill the gap with a guessed timezone.

This does not clear a managed challenge or a Turnstile widget. A residential exit changes the IP the site scores. It does not execute a challenge for you. If the document comes back 200 and the body is a block page, classify it. That failure mode is Playwright’s silent 403, and it happens on Camoufox for the same reason: the browser loaded a document, and the document was not the page.

What to check when it fails

What you seeLikely causeWhat to change
407Login pasted into serverusername and password keys only
Timezone and WebRTC disagree with the IP pageExit changed after launch, or the sticky lifetime ended under an open browserNew browser, a session id you choose, and -lifetime- long enough for the job
Country is wrong before the target loadsSession id reused from another job, or no country on the usernameA new session id and -country-
200 and a challenge bodyIP reputation or a real challengeClassify the body. Try Elite if Premium is what the target is scoring. Elite is not a guarantee. Do not add a solver on this page

Change one thing and read the exit again. Public pages only. This guide does not teach CAPTCHA solving.

Premium residential is the country pool. Elite is the pool with city and ISP targeting when the target scores the exit. Prices are on /pricing.

FAQ

Camoufox proxy questions

How do I set a proxy in Camoufox?
Install camoufox[geoip], then pass geoip=True and a proxy dict with server, username, and password. Camoufox’s geoip docs use an HTTP server URL. Put the login in the username and password keys, not inside the server string. The flag reads the exit when the browser launches.
Should Camoufox use a rotating residential proxy?
Rotation between jobs is fine when each exit gets its own browser launch and its own session id. Changing exits inside a browser that is already open can invalidate the timezone, locale, language, and WebRTC address that geoip=True took from the first IP. Those values are set at launch. The geoip page does not describe refreshing them mid-browser.
How long can the sticky session last?
On Aethyn the hold is 1–1440 minutes. The default is 30 minutes if you omit -lifetime-N. Put it on the username, for example aethyn-XXXXX-country-us-session-fox1-lifetime-30, and make it at least as long as the browser stays open. That timer belongs to the gateway, not to Camoufox. Inside the window, the same session id can return the same exit. When the lifetime ends, the next connection on that id can draw a new household while the open browser still shows the first lookup. Close it and launch again.
Does Camoufox need Elite or Premium?
Premium HTTP on port 2099 is the country-level pool. Elite HTTP on port 5499 is the pool that adds supported city and ISP targeting, and the one to try when the destination’s exit-IP reputation is the problem. Elite does not guarantee the target will accept the session. Both pools are residential. Aethyn does not sell a datacenter proxy to try first.
Share this article

Guides, integrations & docs

Continue reading

Hold one household exit for the whole browser

Premium HTTP 2099 for country volume. Elite 5499 when the target scores the exit. Sticky 1–1440 minutes in the username. Free trial, no card.

Back to all articles