Kameleo proxy setup

Protocols

HTTP / HTTPS, SOCKS5 and SSH, with optional username and password

UDP

From 5.3, HTTP/3 (QUIC) goes through SOCKS5 in Chroma 152 and later; WebRTC over SOCKS5 UDP is an experimental opt-in

Where the setting is

The proxy settings of a profile, when you create or edit it

Line format

user:pass@host:port

Works with

Residential and mobile proxies

Before you start

• Kameleo installed, version 5.3 or later if you want HTTP/3 (QUIC) to go through SOCKS5.
• Your proxy login and password from the Residential or Mobile page of the dashboard. The product needs traffic, or the gateway answers 402.
• A clear purpose for each profile: your own accounts, clients' ads accounts you manage with their access, or QA and testing, within each platform's rules.

Add the proxy

1. Click New Profile and choose the base fingerprint as usual. To change an existing profile, stop it before you edit the proxy.
2. In the profile's proxy settings, change Direct connection (No proxy) to HTTP for port 7000, or SOCKS5 for port 7001.
3. Paste one string in the order Kameleo reads, user:pass@host:port (a format the generator offers): LOGIN:[email protected]:7000. Kameleo splits it into host, port, username and password. Or type the host and port, switch on Authentication, and fill in the username and password.
4. Kameleo guesses the type from the port, so check it still says HTTP for 7000 or SOCKS5 for 7001.
5. Click Test Proxy, then save the profile and start it.

HTTP or SOCKS5

Both work for browsing. From Kameleo 5.3, with the Chroma 152 kernel or newer, SOCKS5 also carries HTTP/3 (QUIC) as UDP, and our port 7001 relays UDP through the same exit IP. The same release added WebRTC over SOCKS5 UDP as an experimental option that stays off until you turn it on.

Check the proxy

Test Proxy tries Google, Archive.org and Wikipedia through the proxy in turn, without starting the profile; one success means the proxy works. Since version 5.2 a failed test explains the cause in plain language and builds a report to copy for support. Kameleo also tests before every launch and does not start the browser if the test fails.

Kameleo's own advice is to leave Timezone, Geolocation and WebRTC on Automatic under Advanced Settings → Location, so they follow the proxy IP, and to match the profile language to the proxy country. Once the profile runs, open the IP checker for the IP, location and any WebRTC or DNS leak.

Rotating or sticky

Kameleo advises one proxy per profile, kept over time, or one from the same region when it has to change. One sticky line per profile, with its own -sid- key and fixed targeting, does that.

LOGIN-cc-us-st-newyork-city-newyork-sid-kam01-ttl-60:[email protected]:7000
LOGIN-cc-us-st-newyork-city-newyork-sid-kam02-ttl-60:[email protected]:7000

A sticky IP lasts at most 60 minutes (-ttl-60). Then the same string gets a new IP targeted at New York City, so the automatic time zone and location stay right. No setting keeps one residential or mobile IP for days.

For many profiles, Kameleo's API takes the proxy (type, host, port, username and password) when it creates a profile, so a script can give each one its own line from our proxy list API.

If it does not work