Kameleo Proxies

Proxies for Kameleo

Kameleo patches fingerprints at the browser kernel and refuses to launch a profile whose proxy fails its own test. Give it a gateway that passes: residential, datacenter, mobile and IPv6 IPs over HTTP or SOCKS5, with a sticky session per profile and the same credentials working through the Local API.

Get Started Now See Pricing

Sticky IP per profile   HTTP & SOCKS5   Passes the launch test

100M+IP Pool
StickyOne IP per profile
195+Countries
HTTP / SOCKS5Protocols
One IP per profile Residential & mobile City & country targeting Local API on every plan Real human support
Why Proxy Rotator

Built for Kameleo's two kernels

Chroma on Chromium, Junglefox on Firefox. The proxy attaches the same way to both, and ours passes the pre-launch check.

Residential & mobile IPs

Real home and cellular IPs from a 100M+ pool are what account work needs behind a kernel-level fingerprint. Datacenter and IPv6 are on the same plan for speed-first jobs.

Passes the pre-launch test

Kameleo tests a proxy before it starts the browser and refuses to launch if the test fails. We do not restrict traffic to an approved domain list, so its checks connect normally.

Sticky IP per profile

Give each profile its own sticky port and it holds one address across launches, so the fingerprint and the IP stay consistent with each other.

HTTP, HTTPS and SOCKS5

Kameleo's Proxy Manager takes HTTP, HTTPS, SOCKS5 and SSH. Our gateway covers the first three from one set of credentials, so pick whichever the profile needs.

Local API on every plan

Kameleo exposes its Local API on all tiers, free included. The proxy lives on the profile, so scripted launches inherit the IP without handling credentials.

Rotating on the same plan

Point a profile at the rotating endpoint for a fresh IP per connection when you are collecting data rather than holding an account. See rotating proxies.

Setup

Add Proxy Rotator to Kameleo

Four steps from gateway credentials to a profile browsing on your own IP.

Before you start. Install Kameleo and sign in. Their free tier covers two concurrent browsers and unlimited local profiles, which is enough to test this integration end to end, and the Local API is available on every plan including free.

Copy your gateway details

Open Proxy Gateways in your Proxy Rotator dashboard. Copy the host, the port for the proxy type and location you want, and your username and password. Each type lists a rotating port and a range of sticky ports, take a sticky port for account work.

Open the profile's proxy settings

Create a new profile or edit an existing one and find the connection setting in Kameleo's built-in Proxy Manager. Change it from a direct connection to HTTP / HTTPS or SOCKS5. If a profile is already running, stop it first, Kameleo will not change a proxy on a live session.

Enter the gateway

Fill in the host, port, username and password. Kameleo also accepts a pasted connection string, which is quicker and avoids typos.

Kameleo - Proxy settings
SOCKS5  (or HTTP / HTTPS)
gateway.proxyrotator.com
8080
USER
PASS

Kameleo's Proxy Manager filled in with Proxy Rotator gateway details.

Test it, then launch

Run the proxy test before you start the profile. Kameleo connects out through the gateway and tries several well-known sites in turn until one answers. Once it passes, launch the profile and the browser runs on that IP.

This test is not optional. Kameleo re-tests the proxy every time it starts a profile, and if the test fails the browser does not launch at all. A proxy that only works sometimes will show up as a profile that only opens sometimes, so fix any test failure before you build on it.

Paste a connection string instead

Kameleo's Proxy Manager accepts the standard single-line formats, so you can paste one line rather than filling four fields. Both of these describe the same gateway.

Kameleo proxy connection string
# Plain host:port:username:password
gateway.proxyrotator.com:8080:USER:PASS

# Or the URL form, with the scheme in front
socks5://USER:PASS@gateway.proxyrotator.com:8080
http://USER:PASS@gateway.proxyrotator.com:8080

# IPv6 hosts go in square brackets
[2001:db8::1]:8080:USER:PASS
Watch the password. In the URL form, a password containing @, : or / has to be percent-encoded or the string will parse wrong. The plain host:port:user:pass form has no such problem, so use that if your password has symbols in it.

For a batch of profiles, keep the host and credentials identical and change only the sticky port on each line. Each port is an independent session that holds its own IP, which is exactly what one-profile-one-identity requires.

One line per profile
# Same host and credentials, a different sticky port each time.
# Take the range from Proxy Gateways in your dashboard.
gateway.proxyrotator.com:11001:USER:PASS
gateway.proxyrotator.com:11002:USER:PASS
gateway.proxyrotator.com:11003:USER:PASS
Reference

Field mapping

What belongs in each field, in the interface and in the API.

Kameleo fieldWhat to enterAPI field name
Connection typeSOCKS5, or HTTP / HTTPSvalue
HostYour gateway hostnameextra.host
PortThe port for that proxy type and locationextra.port
UsernameYour gateway usernameextra.id
PasswordYour gateway passwordextra.secret
Direct connectionNo proxy at allproxy = null
SSHNot applicable to our gateway—

Note the API names: the username goes in id and the password in secret, not username and password.

Setting the proxy from the Local API

Kameleo runs its Local API on http://localhost:5050 and ships SDKs for Python, JavaScript and C#. It is available on every plan, including the free tier, so you can script profile creation from day one.

The proxy is described by a small object with two parts: value for the protocol, and extra for the server itself. This is the part that catches people out, because the credential fields are not called what you would expect.

Python (Kameleo Local API proxy object)
# Kameleo Local API: http://localhost:5050
# Attach this object to the profile, and the browser launches behind it.

proxy = {
    "value": "socks5",                     # 'http', 'https', 'socks5' or 'ssh'
    "extra": {
        "host": "gateway.proxyrotator.com",
        "port": 8080,
        "id":     "USER",                  # username lives in 'id'
        "secret": "PASS"                   # password lives in 'secret'
    }
}

# Set it on the profile request when you create or update the profile.
# Use proxy = None for a direct connection with no proxy at all.

Two behaviours worth designing around. Kameleo tests the proxy before every launch and will not start the browser if the test fails, so wrap profile starts in a retry and surface the failure rather than assuming the browser opened. And a profile has to be stopped before its proxy can be changed, so swap the proxy between runs, not during one.

Bypass lists and WebRTC

Kameleo can hold a bypass list of hosts and CIDR ranges that connect directly rather than through the proxy, which is useful for an internal service you do not want tunnelled. It can also restrict WebRTC to proxied TCP connections, which closes the leak where WebRTC reports your real address while everything else goes through the gateway. Both are worth switching on for account work.

Working outside Kameleo too? The gateway is protocol standard, so the same credentials drop straight into Playwright, Selenium and Scrapy on any machine, with no desktop app involved.

Keep DNS and UDP in mind

Kameleo resolves DNS through the proxy, which is what you want: lookups leave with the traffic instead of going to your own resolver, so there is no trail of hostnames on your real connection. It does not support UDP-based proxies, so anything UDP-only is out, but HTTP, HTTPS and SOCKS5 all work, and those are what our gateway serves.

Match the profile to the exit IP as well. Set the timezone and language to the country you targeted, and if the profile does anything location-aware, line up the geolocation too. City-level targeting on residential makes this easy: pin the profile to one city, set the matching timezone once, and every launch tells the same story.

Rotating vs sticky for Kameleo

For accounts, use sticky proxies. One IP per profile, held for the session, so the account looks like the same returning person each time. Pairing a kernel-level fingerprint with an IP that changes underneath it defeats the purpose.

Use rotating proxies for collection work, where a fresh IP per connection is the advantage. Same gateway, same plan, different port.

Troubleshooting

Kameleo proxy test failing?

Because a failed test blocks the launch, most Kameleo proxy problems look like a browser that will not open.

SymptomLikely causeFix
Browser will not launch at allThe pre-launch proxy test failed, so Kameleo stoppedRun the proxy test on its own and fix the failure it reports
Test fails, cURL worksProvider blocks the sites Kameleo tests againstUse a gateway with no domain allow-list. Ours has none
Authentication rejectedPassword with symbols broke the URL-form stringUse plain host:port:user:pass, or percent-encode it
Connection refusedProtocol does not match the portConfirm SOCKS5 vs HTTP / HTTPS against your dashboard
Proxy change did not applyThe profile was running when you edited itStop the profile, change the proxy, start it again
Local API unreachableKameleo not running, or port 5050 blocked locallyStart the app and allow localhost:5050 through the firewall
Real IP visible in a leak testWebRTC not restricted to the proxied connectionTurn on the WebRTC restriction in the profile settings
IP changes between launchesPointed at a rotating portSwitch to a sticky port from the range in your dashboard

Before you blame Kameleo, confirm the credentials independently. This should print an IP that is not yours.

cURL verify
curl -x http://USER:PASS@gateway.proxyrotator.com:8080 https://api.ipify.org
Also supported

Running more than one antidetect browser?

One plan and one set of credentials covers every tool here.

Octo Browser

Proxy Manager, bulk add and local API automation.

View setup guide

Incogniton

Proxy Library, bulk import and a sticky IP per profile.

View setup guide

Multilogin

Sticky IPs across the Mimic and Stealthfox engines.

View setup guide

AdsPower

Per-profile proxies for multi-account work.

View setup guide

Playwright & Puppeteer

Native proxy auth per browser context, no desktop app.

View setup guide

All integrations

Every supported tool, with copy-paste setup guides.

Browse all guides
FAQ

Proxy Rotator with Kameleo FAQ

How do I add a proxy to Kameleo?
Open the profile's connection setting in Kameleo's built-in Proxy Manager, change it from a direct connection to SOCKS5 or HTTP / HTTPS, then enter your gateway host, port, username and password. You can also paste a connection string such as gateway.proxyrotator.com:8080:USER:PASS. Run the proxy test, then launch the profile.
Why will my Kameleo profile not launch?
Kameleo tests the proxy before it starts the browser, and if that test fails it does not launch at all. So a profile that will not open is usually a proxy problem, not a browser problem. Run the proxy test on its own to see the failure, and confirm the protocol matches the port you were given.
Kameleo's proxy test fails but the proxy works elsewhere. Why?
Kameleo tests by connecting to several well-known sites in turn. Some providers restrict traffic to an approved list of domains, so those test connections are blocked even though the proxy itself is fine. Our gateway does not use a domain allow-list, so the test connects normally.
Does Kameleo support SOCKS5?
Yes. Kameleo's Proxy Manager supports HTTP, HTTPS, SOCKS5 and SSH. Our gateway serves HTTP, HTTPS and SOCKS5 on the same credentials. Note that Kameleo does not support UDP-based proxies, which does not affect us since our gateway is TCP.
What are the API field names for a proxy in Kameleo?
The proxy object has value for the protocol, one of http, https, socks5 or ssh, and an extra object holding the server. Inside extra, the username goes in id and the password in secret, not username and password. Setting the whole proxy to null gives a direct connection.
Which proxy type is best for Kameleo profiles?
For account work, sticky residential or mobile IPs, since they come from real home and cellular connections and hold one address per profile. Datacenter suits speed-sensitive work, IPv6 suits high volume. All four are on one plan from $24.95/mo.
Can I change a proxy while a Kameleo profile is running?
No. The profile has to be stopped before its proxy settings can change. If you are scripting this, stop the profile, apply the new proxy, then start it again, rather than trying to swap mid-session.
Does every Kameleo profile need its own proxy?
For separate accounts, yes. Profiles sharing an IP can be linked by platforms regardless of how different their fingerprints are, which undoes the work the kernel-level fingerprinting is doing. Give each profile its own sticky port so it keeps a distinct, stable address.
How do I stop WebRTC leaking my real IP in Kameleo?
Kameleo can restrict WebRTC to the proxied TCP connection, which stops it reporting your real address while the rest of the traffic goes through the gateway. Turn that on in the profile settings, then confirm with a browser leak test before using the profile.
Is the Kameleo Local API available on the free plan?
Yes, the Local API is available on every tier including free, and it runs on http://localhost:5050. That means you can script profile creation and proxy assignment while you are still evaluating, using the same gateway credentials you would use in production.
Do I need a separate plan for each antidetect browser?
No. One Proxy Rotator plan works everywhere at once. The same credentials go into Kameleo, Octo Browser, Incogniton and every other tool on our integrations list. See pricing to size the concurrency you need.

Power your Kameleo profiles with clean IPs

Residential, mobile, datacenter and IPv6 on one plan, with a sticky IP per profile and a gateway that passes Kameleo's pre-launch test. From $24.95/mo.

Get Started Now See Pricing
Copied!