Antidetect BrowserHTTP, SOCKS5, SSHAbout 5 minutes

How to Set Up a Proxy in Kameleo

Kameleo is an antidetect browser that ships two of its own browser kernels: Chroma, which is built on Chromium, and Junglefox, built on Firefox. Each profile keeps its own fingerprint, cookies, and proxy, so the accounts you want held apart stay apart. It also emulates Android and iOS profiles rather than desktop only, which is worth knowing if you plan to pair a mobile profile with a real carrier IP. The proxy fields sit inside the profile form itself, and there is a Test Proxy button right beside them. So you find out the connection works before you save, not after.

Get your proxies Sign up with Google

Full Kameleo setup, start to finish

What You Need

An active FleetProxy plan (residential rotating, static residential, mobile rotating, or datacenter)
Kameleo installed on Windows or macOS
Your proxy credentials from the FleetProxy dashboard

Not sure which proxy type fits? Rotating residential works for most multi-account setups, while static IPs suit accounts you keep long term.

Get Your FleetProxy Credentials

Every Kameleo profile needs a host, port, username, and password. Here is where to find them in the dashboard.

1
Open Active Proxies
Log in to the FleetProxy dashboard and click Active Proxies in the left sidebar. It lists every plan you already own.
2
Manage the plan you want to use
Find the product you are connecting, then click Manage. Each product has its own host and ports, so pick the one you actually plan to route traffic through.
3
Generate and copy your proxy
Open the Generator tab. Choose country, state, city, or ISP if you need a specific location, pick HTTP/HTTPS or SOCKS5, then set rotation to Random IP or Sticky IP. Your credentials appear on the right, ready to copy.

Host and port for every product

FleetProxy host and port by product
Product	Host	HTTP / HTTPS	SOCKS5
Residential Rotating	residential-v2.fleetproxy.io	5000	5000
Mobile Rotating	mobile.fleetproxy.io	5000	5000
Datacenter Rotating	datacenter.fleetproxy.io	9000	9000
Static Residential (ISP)	Your assigned IP address	50100	50101

Kameleo Proxy Setup, Step by Step

1
Open Profiles and click New
Launch Kameleo and stay on Profiles in the left sidebar. Click New in the top right to start building one. If a banner tells you this is an accountless session, that is fine for a first run, though Kameleo asks for a free account before the rest of its features open up.
2
Name the profile, then switch Proxy to With Proxy
Give the profile a name you will recognize later, then work down the form: Language, Device, OS, and Browser. Chroma is the Chromium kernel and Junglefox is the Firefox one. Pick Mobile under Device if you are going to run a mobile IP, because a desktop fingerprint sitting on a carrier address is an obvious mismatch. Then set Proxy to With Proxy. The overview panel on the right updates as you go, so you can read back what the profile will report before you commit to it.
3
Pick your protocol and paste the FleetProxy details
Three tabs appear: HTTP, SOCKS5, and SSH. Choose whichever you generated in the dashboard. The gateway goes in the wide field and the port in the small one after the colon, so residential-v2.fleetproxy.io and 5000 for residential rotating. Username sits below that, password below that again. Kameleo also reads a full ip:port:username:password string, or username:password@ip:port, if you would rather paste one line than fill four boxes.
4
Run Test Proxy before you save
Click Test Proxy. Kameleo shows the server details it is about to use, then runs six checks: direct connectivity, direct HTTPS, proxy IPv4, proxy IPv6, proxy HTTPS, and the location the IP resolves to. All six should pass. The location line at the bottom should name the country you picked in the generator, so read it rather than skimming past it.
5
Save, or Save and Start
Save puts the profile in your list for later. Save & Start does the same and opens the browser straight away. Either way that profile now carries the IP every time it launches, and nothing you do inside it touches your own connection.

If you are using static residential (ISP) proxies

For static residential (ISP) proxies, drop the gateway domain. Put the IP address assigned to you in the dashboard into the host field instead, then use port 50100 for HTTP or 50101 for SOCKS5. The username and password do not change.

Verify It Actually Works

Test Proxy already reports the country, but if you want to see it from inside the browser, open httpbin.org/ip in the launched profile. The address that comes back should be your FleetProxy IP. If your own address appears instead, the profile started without the proxy, so reopen it and check the Proxy row is still set to With Proxy.

You can also run the address through our IP lookup tool to confirm the country and provider, or use the proxy tester to check the connection responds before you start working in the profile.

Troubleshooting Kameleo Proxy Errors

Test Proxy passes the direct checks but fails the proxy ones

That split is useful, because the direct checks passing means your own connection is fine and the problem is the proxy line. Re-copy the username and password from the dashboard first, since a trailing space is the usual cause. Then check the port against the tab you picked. Residential rotating takes 5000 on HTTP and SOCKS5 alike, but static ISP keeps them on 50100 and 50101, so a mismatch there will not connect.

The profile opens but pages will not load

Try the other protocol, HTTP instead of SOCKS5 or the reverse. If that changes nothing, check the plan still has bandwidth left in your dashboard, and confirm the proxy is still active there.

Test Proxy connects but reports the wrong country

The proxy is working. It landed somewhere you did not ask for, that is all. Go back to the generator, set the country, state, or city you want, then copy the credentials again. A rotating gateway hands you a different exit each session unless you asked for a sticky IP.

Accounts in separate profiles are still getting linked

Every profile needs its own IP. One address shared across several profiles undoes the fingerprint work, because the address is the first thing platforms compare. Line the profile up with its proxy too: a Mobile device profile belongs on a mobile IP, and the language and timezone should match the country the IP sits in.

Still getting blocked once everything connects? That is usually an IP reputation problem rather than a setup problem, and our guide on avoiding IP bans covers what to change.

Kameleo Proxy Setup FAQ

Does Kameleo support SOCKS5 proxies?

Yes. The profile form offers HTTP, SOCKS5, and SSH, and the protocol is set per profile rather than once for the whole app. SOCKS5 is the common pick for antidetect work because it passes traffic through without rewriting HTTP headers, though HTTP is fine for ordinary browsing.

Can every Kameleo profile use a different proxy?

It can. The proxy is part of the profile and is set when you create it, so each profile browses from its own address. That separation is the point of the exercise. Fingerprints can be flawless and accounts will still be linked if they all share one IP.

What are Chroma and Junglefox?

They are Kameleo's two browser kernels. Chroma is built on Chromium and covers Chrome, Edge, Safari, and mobile profiles. Junglefox is built on Firefox. Both are modified at engine level, so the fingerprint masking is already in place before any page script runs.

Does Kameleo come with proxies included?

No. It handles fingerprints and profile isolation, and you supply a proxy for each profile yourself. That is normal for antidetect browsers, and it works in your favor, because you choose the network instead of being tied to whatever the browser bundles.

Which proxies work best with Kameleo?

Residential rotating suits volume work that needs fresh addresses. Static ISP suits accounts held long term, since the address stays put. Mobile IPs are the strongest option on mobile-first platforms, and they pair naturally with the Mobile device profiles the browser can generate.