Python library · HTTP · 4 steps
Camoufox Proxy Setup: proxy=, geoip=True and One Sticky Line per Profile
Camoufox takes a proxy the way Playwright does: pass proxy={"server": "http://host:port", "username": ..., "password": ...} to Camoufox(). Add geoip=True so the browser takes its timezone, locale, geolocation and WebRTC address from the proxy's exit IP. With a QuanticData sticky line per persistent profile, each profile keeps its own IP.
Set up the proxy in Camoufox
Open Camoufox, follow the 4 moves below and finish with the tool's own check. The values are in the table after the steps.
-
01
Install Camoufox with the geoip extra
Install the Python package with the geoip extra and download the browser build with python -m camoufox fetch. The geoip extra is what lets Camoufox read the location of the proxy's exit IP.
pip install -U "camoufox[geoip]" python -m camoufox fetch -
02
Pass the proxy and geoip=True
Camoufox accepts every Playwright Firefox launch option. Give it proxy with three keys, server as http:// plus the gateway host residentialpremium.quanticdata.io and port 8080, and the username and password of your line, and set geoip=True. Copy the line from the generator rather than typing the username: it carries the country and the session.
Illustration of a Camoufox launch with a QuanticData proxy: server http://residentialpremium.quanticdata.io:8080, the sticky username and password, and geoip=True, which takes timezone, locale and geolocation from the exit IP. -
03
Open a page and read the exit
Open a page that prints your IP and its location, such as https://ipinfo.io/json, and compare the country with the one in the username. With geoip=True the browser's timezone and language follow the same exit, so the page sees a visitor whose clock and language match the IP.
-
04
Keep each profile on its own line
For profiles that must survive restarts, launch with persistent_context=True and a user_data_dir per profile, and give each profile its own sticky line. Cookies and storage stay in the folder; the session id in the username keeps the exit IP.
Illustration of two persistent Camoufox profiles, each with its own user_data_dir folder and its own QuanticData sticky username, so cookies and the exit IP stay with the profile between runs.
Check it
Load https://ipinfo.io/json in the Camoufox page. The ip and country it returns are the exit of your QuanticData line.
Run the same profile again with the same line: as long as the session lasts, the exit IP stays the same.
Why geoip=True matters with a proxy
A proxy changes the IP a site sees, but the browser still reports your computer's timezone, language and, through WebRTC, possibly your own address. With geoip=True Camoufox looks up the exit IP and sets longitude, latitude, timezone, country, locale and the WebRTC IP from it, and picks the browser language from the languages spoken in that region. You can also pass a fixed IP to geoip instead of True.
Use the country in the QuanticData username to pick the exit, then let geoip=True align the rest. Pass locale yourself only when you need a specific language.
One persistent profile, one sticky line
Copy one sticky line per profile from the dashboard, each with its own sid, and keep them next to the profile folders. The session lasts as long as its ttl, up to 24 hours on Residential Premium and Mobile; after that the same line works from a new IP. For an account that must keep one address for weeks, use a dedicated ISP IP: one Premium ISP IP is $4.99 for 30 days with unlimited traffic.
from camoufox.sync_api import Camoufox
# One line per profile, copied from the QuanticData generator (host:port:user:pass, HTTP)
PROFILES = {
"shop-us-1": "residentialpremium.quanticdata.io:8080:USER-country-us-sid-k3f9a1b2-ttl-30m:PASS",
"shop-us-2": "residentialpremium.quanticdata.io:8080:USER-country-us-sid-q7w2e5r8-ttl-30m:PASS",
}
for name, line in PROFILES.items():
host, port, user, password = line.split(":", 3)
with Camoufox(
persistent_context=True,
user_data_dir=f"profiles/{name}",
geoip=True,
proxy={"server": f"http://{host}:{port}", "username": user, "password": password},
) as context:
page = context.new_page()
page.goto("https://ipinfo.io/json")
print(name, page.inner_text("body"))
HTTP or SOCKS5 in Camoufox
Every proxy example in the Camoufox documentation uses an http:// server with a username and password, and that is the setup this guide uses: the HTTP port 8080 of a Residential Premium or Mobile line. The maintainers state that the proxy layer also accepts socks:// servers, which Firefox reads as SOCKS5, with DNS resolved through the proxy; they ask for reports when SOCKS5 with a login fails. Stay on HTTP with a login unless your task needs SOCKS5.
To block WebRTC entirely instead of aligning it, Camoufox has block_webrtc=True. To save traffic on gigabyte plans, block_images=True stops image requests.
Camoufox proxy not working: the usual causes
- The login inside the server URL: put the username and password in their own keys, and only http://host:port in server.
- The SOCKS5 port with an http:// server, or the reverse: 8080 is the HTTP port and 1080 the SOCKS5 port on Residential Premium and Mobile.
- geoip=True without the geoip extra: install camoufox[geoip], then run the script again.
- A country other than the one you wanted: the country is in the username. Generate a line with the right country rather than editing the string.
- A new IP between runs: the session ttl ended, or two profiles share one sid. Give each profile its own line.
- Still failing: log in and ask Quantic AI in the dashboard. It tests your line from our side with your own login and tells you what the gateway answered.
What to type: ports and the username
Copy the line from the dashboard (Proxies, your plan, the generator) rather than typing it: it already carries the host, the country, the session id and the session length. The table shows what each field holds.
| Plan | Copy it from | HTTP port | SOCKS5 port | Username shape |
|---|---|---|---|---|
| Residential Premium | the generator | 8080 | 1080 | USER-country-us-sid-k3f9a1b2-ttl-30m |
| Mobile | the generator | 8080 | 1080 | USER-country-us-type-mobile-sid-a1b2c3-ttl-30m |
| Residential Basic | the generator | in the line | in the line | USER-country-us plus a session for sticky |
| Datacenter (per GB) | the generator | 9999 | 10000 | the line's username |
| IPv6 | the generator | 1001 | in the line | the line's username |
| ISP (dedicated IP) | the plan page, one line per IP | in the line | in the line | the line's own login |
The host and the password are in the same line. Pick HTTP or SOCKS5 in the tool and use the port of that column; a port from the other column is the most common reason a check fails. On Premium ISP city plans one port serves both types. USER and the session id stand for your own values.
Where the line comes from in the dashboard
Step 3: the number of IPs, the price for 30 days and the Buy button. One IP is one antidetect profile.
After payment the plan is in My proxies: each IP comes as IP:Port:Username:Password, HTTP or SOCKS5, ready to paste into the tool.
The plan page has the generator: country, pool, Sticky session with its TTL, HTTP or SOCKS5, then one line per profile in host:port:user:pass.
The whole buying flow, both routes and the prices are on the integrations page.
Camoufox proxy questions
What customers ask when they put a QuanticData line into Camoufox.
Something else? Ask usHow do I use a proxy with Camoufox?
Pass proxy={"server": "http://host:port", "username": "...", "password": "..."} to Camoufox(), the same option Playwright uses. With a QuanticData line the server is http:// plus residentialpremium.quanticdata.io:8080, and the username is the sticky username from the generator.
What does geoip=True do in Camoufox?
It looks up the proxy's exit IP and sets the browser's timezone, locale, geolocation and WebRTC address from it, so they match the IP the site sees. It needs the package installed with the geoip extra.
Does Camoufox support SOCKS5 proxies?
The documentation's examples use HTTP servers with a login. The maintainers say the proxy layer also accepts socks:// servers, read as SOCKS5, and ask for reports if SOCKS5 with a login fails. HTTP on port 8080 with a username and password is the tested route.
How do I keep the same IP in a Camoufox profile?
Use a sticky QuanticData line: its session id keeps one exit IP for the session length, up to 24 hours. Launch with persistent_context=True and a user_data_dir per profile, and never share one session id between two profiles.
Which QuanticData plan works best with Camoufox?
Residential Premium for scraping and testing in many countries, from $4 for 1 GB valid 30 days; Mobile for social targets, from $5 for 1 GB valid 90 days; a dedicated ISP IP, $4.99 for 30 days, for one profile that must keep one address.
Run Camoufox through a sticky line
Create an account, buy a Residential Premium pack from $4 for 1 GB or a mobile pack from $5 for 1 GB, copy one sticky line per profile and pass it to proxy=.
Balance, crypto, card or PayPal · no VAT from the balance or crypto