Incogniton proxy setup: one saved proxy for every browser profile

Incogniton keeps each browser profile’s fingerprint, cookies and storage apart, and its own docs are blunt about the gap: without a proxy, every profile on your connection shares your real IP. The quickest fix is to save the proxy once in Incogniton’s Proxy Library and pick it from there in each profile. This guide does that, then covers importing a batch of proxies and profiles from CSV, letting teammates use profiles, and the three ways a proxy check fails.

Every label below is taken from Incogniton’s own guide to attaching an external proxy and the pages around it. Incogniton is a desktop app we cannot script, so if a button has moved, that page wins.

How to add a proxy in Incogniton

Short answer: Proxy Library in the left menu, + New proxy, paste IP:PORT:USER:PASS into the Proxy (ip:port) field, click Check, then Add. Then open the profile, go to its Proxy tab, choose Proxy Library and click Select from Proxy Library. The long version:

1. Open Proxy Library from the left-side menu and click + New proxy in the top right.
2. Give it a display name you will recognise later. Name it after the job, not the IP: acme-uk-ads tells you more in six months than a row of digits.
3. Pick the Connection type. Incogniton’s form docs name two, HTTPS and SOCKS5, while its CSV import (below) calls the first one HTTP. For a port your dashboard lists as HTTP, that first choice is the one to try; for a SOCKS5 port, SOCKS5. If the type is wrong, the check in step 6 fails straight away, so you will know.
4. Paste the whole line into Proxy (ip:port). Incogniton splits it and fills Proxy username and Proxy password for you:

   IP:PORT:USER:PASS

5. Leave Rotating proxy off. It asks for a Proxy rotation API url that Incogniton calls to get a new IP, and a static address has nothing to rotate.
6. Click Check. A green result means Incogniton reached the proxy and looked up its location. Then click Add. Adding several in a row? Add to list queues this one and clears the form for the next.

Two more fields on that form are worth a look. Group files the proxy with others for the same client. And Proxy provider is not about who sold you the proxy: it picks the geolocation database Incogniton checks the IP against, which matters when the location comes out wrong (see the fixes below).

Attach the saved proxy to a profile

For a profile that already exists:

1. On the profile list, click the ⋮ next to the profile and choose Edit.
2. Open the Proxy tab, choose Proxy Library and click Select from Proxy Library. Pick the proxy you just saved.
3. Save, then Launch the profile from the list.

For a new profile, click Create profile, give it a name, and leave Use free Incogniton proxies switched off: those are shared addresses that Incogniton itself says may change between sessions. Click Create, then set the proxy on the Proxy tab as above. If you would rather not use the library at all, the same tab has Custom proxy, which takes the same fields straight into the profile.

One proxy, one profile. The profile list has a Proxy column, so a quick scroll down it shows whether two profiles have ended up on the same address. If they have, every site they both visit sees one visitor, not two, and a block on that address stops both.

Adding many proxies and profiles at once

Bulk add to the Proxy Library

In the Add proxy form, click Bulk add at the bottom left. Paste one proxy per line in the same ip:port:username:password shape, or use Load from file to read a CSV with one proxy per row. Choose a Group for the whole batch and click Add. They land under the All Proxies tab, ready to pick from.

Create profiles from a CSV, each with its own proxy

Click the arrow next to New profile and choose Import from CSV. Upload the file with Choose CSV file or paste it into the text box. The Detected headers panel shows which columns Incogniton recognised; Possible headers lists every column it knows. Click Next, check the table, and click Import.

Only profile_name is required, and the file must have a header row. These are the column names from Incogniton’s reference that matter for a proxy per profile:

profile_name,Proxy_connection_type,Proxy_proxy_url,Proxy_proxy_username,Proxy_proxy_password,Timezone_fill_timezone_based_on_ip,WebRTC_behavior,Geolocation_behavior,Geolocation_fill_geolocation_based_on_ip
acme-uk-ads,HTTP,IP:PORT,USER,PASS,true,altered,Allow,true
acme-fr-ads,HTTP,IP:PORT,USER,PASS,true,altered,Allow,true
qa-de-checkout,SOCKS5,IP:PORT,USER,PASS,true,altered,Allow,true

Two warnings from the same reference. A wrong proxy URL, username or password does not stop the import: the profile is created anyway and simply fails to connect until you fix it by hand. And the docs list Proxy_proxy_url as free text without saying which shape it wants. So import one row first, open it, run the check, and only then import the other forty-nine.

Timezone, language, WebRTC and location in Incogniton

Incogniton can take all four from the proxy. Where each switch lives, and what its docs recommend:

• Language: on the profile’s Details tab, keep Fill language based on IP on. Turning it off and choosing languages by hand sticks, even if you change the proxy later.
• Timezone: under Browser & Navigator, Fill timezone based on IP. A timezone that disagrees with the IP is, in Incogniton’s words, an easy signal for sites to flag.
• WebRTC: under Privacy & Network, the options are Altered, Real, Disabled and Only proxy. Incogniton recommends Altered with Fill WebRTC public IP based on the IP on. Never pick Real on a proxied profile: it reports your actual IP.
• Geolocation: same tab, Prompt, Allow or Block. Incogniton suggests Allow with Fill location based on IP on, so the location a site gets matches the proxy’s region.

All of that is only as right as the IP’s country, so the country has to be one you chose, not one the proxy happened to land in.

Letting a team use the profiles

Incogniton’s team feature lives under Team → Invite member, and it is part of the paid packages; its docs name which. Each member gets a role, and roles are built on the Roles tab from four kinds of permission: administration, Proxy library permissions, general group permissions and specific group permissions. That split is handy: a contractor who runs one client’s profiles can get that client’s group without being able to edit the saved proxies everyone else relies on.

Turn on Active session lock for shared profiles, in the profile’s Advanced → Other tab. It stops the same profile being opened on two computers at once, which Incogniton warns causes sync errors, and which would also put one profile on two different networks at the same moment.

Check the profile’s exit IP

1. Launch the profile and open https://httpbin.org/ip. The origin should be the IP from your dashboard.
2. Run a WebRTC leak test page in the same profile. Your own IP should appear nowhere on it.
3. To rule Incogniton out, test the proxy on its own. Incogniton’s docs suggest Firefox with FoxyProxy; our FoxyProxy setup guide walks through it. From a terminal it is one line:

curl -x http://USER:PASS@IP:PORT https://httpbin.org/ip

Incogniton proxy not working? The fixes

A red cross, or the profile will not launch

Incogniton’s own checklist, in its order: the connection type must match what the provider issued; an IPv6 proxy only works on sites that support IPv6; the authentication method must match (username and password, or IP authorisation); and the port must be in the address field as ip:port. If you get in with an allowlisted IP rather than a password, leave the username and password fields empty.

If curl gets a 407, the credentials are wrong; see 407 Proxy Authentication Required. If curl hangs, nothing is answering on that IP and port; see connection timeouts.

A red lightning bolt next to a green tick

Not a failure. Incogniton uses that icon for a slow proxy. The proxy connects; it is just taking its time.

The proxy works everywhere except Incogniton

If curl and FoxyProxy are happy and Incogniton is not, Incogniton’s explanation is that its server could not fetch the IP-dependent data it uses to fill the profile in. Its fix: turn off Fill timezone based on IP, Fill WebRTC Public IP based on the IP and Fill location based on IP, then enter the proxy’s timezone, public IP and coordinates by hand.

The check passes but shows the wrong country

Incogniton checks locations against IPstack by default, and any location database gets some IPs wrong. Open the proxy, switch Proxy provider from Main provider to Backup provider or Second backup provider, and check again. Nothing about the connection changes; only the lookup does. If every database disagrees with the country you bought, tell us which IP it is.

Which proxy to put behind an Incogniton profile

A profile you open again next week wants an address that is still there next week. That is a static ISP proxy from us, in the country you pick at checkout, or a datacenter one where the sites involved do not mind hosting ranges. Our residential gateway is the wrong fit here: it changes address per connection and cannot be pinned to a country. The antidetect browser proxy guide has the longer argument.

And the usual line, because it matters: separate profiles are for work like client accounts you are authorised to run, ad checks and QA. Not for farming accounts or getting round a ban, and each platform’s terms still apply. The acceptable use policy is where we say so formally. Comparing Incogniton with the others before you commit? Five antidetect browsers, compared on the proxy side. Stuck? Bring a screenshot, credentials blurred, to Discord.