Proxies for Incogniton
Give every Incogniton profile its own clean IP. Add your Proxy Rotator gateway to the Incogniton Proxy Library once, then attach a sticky residential or mobile IP to each profile so every fingerprint keeps a stable, believable location. Single proxy or a bulk paste for hundreds of profiles, both take minutes.
Sticky IP per profile HTTPS & SOCKS5 Bulk import ready
Built for Incogniton multi-accounting
Incogniton isolates the fingerprint. The IP behind it has to be just as believable, and just as stable. That is what our pool delivers.
Residential & mobile IPs
Real residential and mobile IPs from a 100M+ pool look like genuine home and cellular users, which is what Incogniton profiles need to avoid flags on social and e-commerce platforms.
Sticky IP per profile
Give each profile its own sticky session so it keeps one consistent address every time it launches. Without that, Incogniton's own docs note that platforms can still link accounts by IP no matter how different the fingerprints are.
Bulk import friendly
Incogniton's Bulk add accepts one ip:port:username:password line per proxy. Paste a list, or load a CSV, and populate the Proxy Library for hundreds of profiles in a single step.
HTTPS and SOCKS5
Incogniton's Connection type dropdown offers HTTPS and SOCKS5. Our gateway serves both, so you pick per profile without changing plans or credentials.
City & country targeting
Pin each profile to a country, and a city on residential, so the exit IP matches the timezone, WebRTC and geolocation you set in the profile's own settings.
Rotating when you need it
Scraping or warming from a profile? Point it at the rotating endpoint on the same gateway for a fresh IP per connection, with no second subscription. See rotating proxies.
Connect Proxy Rotator to Incogniton
Add the proxy to the Proxy Library once, then attach it to as many profiles as you need.
Copy your gateway details
Sign in to your Proxy Rotator dashboard and open Proxy Gateways. Copy the host, the port for the proxy type and location you want, and your gateway username and password. Those four values are everything Incogniton asks for.
Open the Proxy Library in Incogniton
In the Incogniton desktop app, open Proxy Library from the left sidebar and click + New proxy. On older builds this section is labelled Proxy Management, and the button is Create Single Proxy, the form is the same.
Fill in the proxy form
Set the connection type, paste the gateway address, then enter your credentials. Leave Rotating proxy switched off, our gateway handles rotation on its own side and never needs an external API call to change IP.
The Incogniton New proxy form filled in with Proxy Rotator gateway details.
gateway.proxyrotator.com:8080:USER:PASS into the Proxy (ip:port) field and Incogniton splits it across the username and password fields for you.Check the proxy, then save it
Click Check. Incogniton connects through the proxy and returns the exit IP and its location. A green result means the credentials and port are right. Click Add to save it to the library, or Add to list first if you are staging several at once.
Attach it to a profile
Create or edit a browser profile, open the Proxy tab, choose Proxy Library and pick your saved entry with Select from Proxy Library. Save the profile and launch it, the browser now runs on that IP. Repeat with a different sticky port for each additional profile.
Bulk import for many profiles
Running dozens or hundreds of profiles? Do not add them one at a time. In the New proxy form, click Bulk add at the bottom left, paste one proxy per line in ip:port:username:password format, or use Load from file to import a CSV. Assign a Group so the batch stays organised, then save the whole set at once.
The trick for multi-accounting is the port. Keep the host, username and password identical on every line and increment the sticky port, so each line becomes a separate, independent session that holds its own IP.
# One line per Incogniton profile. Same host and credentials, # a different sticky port from the range in your dashboard. gateway.proxyrotator.com:11001:USER:PASS gateway.proxyrotator.com:11002:USER:PASS gateway.proxyrotator.com:11003:USER:PASS gateway.proxyrotator.com:11004:USER:PASS gateway.proxyrotator.com:11005:USER:PASS
After importing, Incogniton lists every entry in the Proxy Library with its own status indicator, so you can spot a bad line before you attach it to a profile. Assign them to profiles from the profile editor's Proxy tab without ever retyping credentials again.
Field mapping
Every field in the Incogniton proxy form, and exactly what to put in it.
| Incogniton field | What to enter | Example |
|---|---|---|
| Display name | Any label that identifies the profile it belongs to | Proxy Rotator - US sticky 01 |
| Connection type | HTTPS or SOCKS5, both on the same gateway | HTTPS |
| Proxy (ip:port) | Your gateway host and the port for that proxy type | gateway.proxyrotator.com:8080 |
| Proxy username | Your gateway username | USER |
| Proxy password | Your gateway password | PASS |
| Group | Optional. Handy for splitting sticky from rotating entries | Sticky residential |
| Proxy provider | Leave on Main provider. Only change it if the location looks wrong | Main provider |
| Rotating proxy | Leave off. Our gateway rotates server side, with no API call | Off |
| Proxy rotation API url | Not needed, leave blank | — |
Host, port and credentials all come from Proxy Gateways in your Proxy Rotator dashboard.
Authentication: two methods
Use whichever suits your setup. Both authenticate against the same gateway.
- Username and password (recommended): enter your gateway login in the Proxy username and Proxy password fields. Credentials travel with the connection, so this works from any machine or network, including a laptop on a changing IP.
- IP whitelist (fallback): add your machine's public IP to the whitelist in your dashboard, then leave the username and password blank. Note that Incogniton's Check runs from the same machine, so the whitelisted IP must be the one you are running the app from.
Verify the connection
The fastest check is Check inside the Proxy Library, which returns the exit IP and location. To confirm the same credentials outside Incogniton, run this from a terminal. It should print an IP that is not your own.
curl -x http://USER:PASS@gateway.proxyrotator.com:8080 https://api.ipify.org
Run it twice against a rotating port and you should see two different IPs. Run it twice against a sticky port and you should see the same IP both times, which is the behaviour every Incogniton profile needs.
Which proxy type for which Incogniton workflow
Every type below is included in one plan, so you can mix them across profiles without buying anything extra.
| What the profile does | Proxy type | Session mode |
|---|---|---|
| Long-lived social accounts | Residential or mobile | Sticky, one port per profile |
| Ad accounts and ad verification | Residential | Sticky, one port per profile |
| Marketplace and seller accounts | Residential | Sticky, one port per profile |
| Account registration and warmup | Mobile or residential | Sticky, one port per profile |
| Scraping from inside a profile | Datacenter or residential | Rotating |
| Geo and QA testing | Datacenter | Rotating |
| High-volume, low-sensitivity requests | IPv6 | Rotating |
| Included in one Proxy Rotator plan | All of the above | Both modes |
Read more on sticky proxies, rotating proxies and residential proxies.
Automating Incogniton profiles
Incogniton exposes a local REST API on port 35000 by default, plus official TypeScript and Python SDKs, and it drives profiles through Playwright, Puppeteer and Selenium. Because the proxy is bound to the profile in the Proxy Library, your scripts never touch proxy configuration, they just launch a profile and inherit its IP.
Launch a profile for Puppeteer and connect over the returned CDP endpoint. Use puppeteer-core, since the full package bundles its own Chromium and will not attach to Incogniton's browser.
// npm i puppeteer-core
const puppeteer = require('puppeteer-core');
const API = 'http://localhost:35000'; // Incogniton local API
const PROFILE_ID = 'your-incogniton-profile-id';
(async () => {
// The profile already carries its Proxy Library entry, so the browser
// launches behind your Proxy Rotator gateway. No proxy args needed.
const res = await fetch(`${API}/automation/launch/puppeteer`, {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ profileID: PROFILE_ID })
});
const { puppeteerUrl } = await res.json();
const browser = await puppeteer.connect({
browserURL: puppeteerUrl,
acceptInsecureCerts: true
});
const page = await browser.newPage();
await page.goto('https://api.ipify.org');
console.log('Exit IP:', await page.evaluate(() => document.body.innerText));
await browser.disconnect();
await fetch(`${API}/profile/stop/${PROFILE_ID}`);
})();
Prefer plain HTTP calls? The same lifecycle works from any language against the local endpoints.
import requests
API = "http://localhost:35000" # Incogniton local API
PROFILE_ID = "your-incogniton-profile-id"
# 1. Confirm the Incogniton desktop app is running
requests.get(f"{API}/alive", timeout=10)
# 2. Launch the profile. Its Proxy Library entry is applied automatically,
# so the session is already on your Proxy Rotator IP.
requests.get(f"{API}/profile/launch/{PROFILE_ID}", timeout=60)
# 3. Drive the session with Selenium or Playwright, then close it cleanly
requests.get(f"{API}/profile/stop/{PROFILE_ID}", timeout=30)
Match the profile to the IP
A clean IP is only half the job. If a profile exits through a New York residential IP while its browser still reports a European timezone, that mismatch is exactly what detection systems look for. Incogniton fills most of this in automatically once the proxy is attached, but when a proxy is added late or swapped, set it yourself:
- Timezone under the profile's Browser & Navigator settings, matched to the exit IP's region.
- WebRTC IP under Privacy & Network, so a WebRTC leak test reports the proxy address rather than your real one.
- Geolocation coordinates under Privacy & Network, aligned to the city you targeted.
This is where city-level targeting earns its keep. Pin a profile to one city on residential, set the matching timezone and coordinates once, and every launch afterwards tells the same story. Then verify with the detection tools built into Incogniton, or with any browser fingerprint checker, before you use the profile for real work.
Rotating vs sticky for Incogniton
For account work you almost always want sticky proxies. A sticky session holds one IP so each profile looks like the same returning person every time it logs in. Incogniton's own documentation puts static and sticky residential IPs behind the large majority of antidetect use cases, and that matches what we see.
Reach for rotating proxies when a fresh IP per connection is the point: bulk data collection, availability checks, or discovery work run from inside a profile. Both modes come from the same gateway on the same plan, so you switch by changing the port, not the provider.
Incogniton proxy not working?
The symptoms Incogniton shows, what usually causes them, and the fix.
| What you see | Likely cause | Fix |
|---|---|---|
| Red cancel icon on the proxy | Connection type does not match the port, or the port is missing | Confirm HTTPS vs SOCKS5 and include the port: host:port |
| Check fails, but the proxy works elsewhere | IP-whitelist auth from a machine whose public IP is not whitelisted | Switch to username and password, or whitelist your current IP |
| Profile will not launch | Credentials rejected or the gateway is unreachable | Re-test with the cURL command above from the same machine |
| Red lightning bolt with a green check | Not an error. The proxy works, the route is just slow | Try a nearer country, or a datacenter IP for lower latency |
| Proxy shows the wrong country | Geolocation lookup is stale, not the proxy itself | Set Proxy provider to Backup provider and check again |
| Sites still see your real location | Timezone, WebRTC or geolocation not matched to the exit IP | Set them under Browser & Navigator and Privacy & Network |
| Several profiles share one IP | They point at the same sticky port, or at a rotating port | Give every profile its own sticky port from your range |
| An IPv6 proxy fails on some sites | The target site has no IPv6 support | Use residential or datacenter IPv4 for those profiles |
Still stuck? Our support team answers real questions from real people, not a bot queue.
Using another antidetect browser too?
One plan and one set of credentials covers every tool below. Run Incogniton and any of these side by side.
AdsPower
Sticky IP per browser profile for multi-account work.
View setup guideGoLogin
Custom proxy per profile on the Orbita browser.
View setup guideMultilogin
Sticky IPs across the Mimic and Stealthfox engines.
View setup guideDolphin Anty
Profile proxies with timezone and geo matching.
View setup guideOcto Browser
Proxy Manager, bulk add and local API automation.
View setup guideKameleo
Chroma and Junglefox kernels, with a pre-launch proxy test.
View setup guidePlaywright & Puppeteer
Native proxy auth per browser context, no desktop app.
View setup guideProxifier
Push any desktop app through the same gateway.
View setup guideAll integrations
Scrapy, Selenium, Octoparse and every other supported tool.
Browse all guidesProxy Rotator with Incogniton FAQ
How do I add a proxy to Incogniton?
host:port with your username and password. Click Check to confirm the exit IP, then Add to save it. Attach it to a profile from the profile editor's Proxy tab using Select from Proxy Library.Which proxy type is best for Incogniton profiles?
Does Incogniton support SOCKS5?
Can I import proxies into Incogniton in bulk?
ip:port:username:password, or use Load from file for a CSV. Keep the host and credentials the same on every line and change only the sticky port, so each line becomes an independent session for one profile.Does every Incogniton profile need its own proxy?
Should I turn on the Rotating proxy toggle in Incogniton?
Why is my proxy not working in Incogniton?
host:port, and check your username and password. If you authenticate by IP whitelist instead, make sure the public IP of the machine running Incogniton is whitelisted in your dashboard.Why does Incogniton show the wrong country for my proxy?
Are Incogniton's free built-in proxies good enough for account work?
Can I use these proxies with Incogniton's API, Selenium or Puppeteer?
How many Incogniton profiles can I run at the same time?
Power your Incogniton profiles with clean IPs
Residential, mobile, datacenter and IPv6 in one plan, with a sticky IP per profile and bulk import into the Proxy Library. From $24.95/mo.