How Do You Add a Proxy to a Kameleo Profile Without Wasting a Launch?
To set a Kameleo proxy, open the profile, go to its Proxy settings, and either paste a connection string in the form user:password@host:port or fill in host, port and credentials by hand, then run Test Proxy before you launch. Kameleo stores the proxy per profile, resolves DNS through it, and stops the browser from starting when the test fails — so a broken proxy never quietly falls back to your own IP address.
📌 TL;DR Executive Summary
- Core Takeaway: Kameleo takes HTTP/HTTPS, SOCKS5 and SSH proxies per profile, and the built-in Test Proxy tool checks reachability through Google, Archive.org and Wikipedia before the browser opens.
- Key Risk/Challenge: A failed test returns HTTP 503 and the profile will not launch at all, while a partial_success result means the proxy works but is degraded — often because it has no IPv6 route.
- Recommended Solution: Test the endpoint first, set the proxy while the profile is stopped, then confirm the real exit IP in the browser instead of trusting the test alone.
Before You Start: What a Kameleo Proxy Setup Actually Requires
Kameleo’s built-in Proxy Manager supports HTTP/HTTPS, SOCKS5 and SSH, and it resolves DNS through the proxy rather than locally. UDP-based proxies are not supported, so an endpoint that only tunnels UDP traffic for one workload will not behave the way you expect inside Kameleo.
Out of the box, a profile with no proxy configured connects straight from your machine’s own IP. That default matters: an empty proxy field is not neutral, it is your real network. If you keep a batch of profiles for client accounts or storefronts you are authorised to manage, give each one its own endpoint rather than leaving any of them blank.
Have these ready before you open the app: the proxy protocol, hostname, port, username and password, and a note of the country and city the exit IP belongs to. You will need that location to line up language and timezone later. Test the same credentials in a terminal first — if a curl request through the proxy fails before Kameleo ever sees it, the problem is on the provider side, not in the profile.
One budgeting point surprises most people: Kameleo’s paid tiers are priced mainly by how many browsers run at once, not by how many profiles you save. The Free tier gives 2 concurrent browsers, 100 cloud profiles, 300 browser minutes a month and 3 team members; Startup is €59/month (€45/month billed annually) with 10 concurrent browsers; Business is €299/month with 100; Enterprise is €1,499/month with 1,000. If you plan to run thirty profiles at once with thirty proxies, concurrency is the line item that decides your bill — Kameleo pricing across the four plans breaks down where each tier lands.
Step-by-Step: Setting a Kameleo Proxy in the Desktop App
- Open the profile’s Proxy tab. Create a new profile or select an existing one and open its settings. Proxy settings live at profile level, so what you enter here applies to that profile only, never to the whole app.
- Choose the protocol before the address. The dropdown changes which fields are required. Switching protocol after you have typed credentials tends to leave stale values behind, so pick first and type second.
- Paste the connection string. Kameleo parses username:password@hostname:port automatically and fills host, port, username and password for you. Typing the four fields manually produces the same result — use whichever you find faster.
- Check what got parsed. Confirm the port did not get swallowed into the password, and that the hostname carries no scheme prefix such as http:// or socks5://. A stray prefix makes a perfectly good proxy fail instantly.
- Run Test Proxy. Do this before saving and launching. The tool tries a connection through Google, Archive.org and Wikipedia, moving to the next site when one is unreachable.
- Read the result rather than the spinner. Success means the endpoint is reachable and forwarding traffic. Partial success means it works but degraded. Failure means this profile will not open at all.
- Align language, timezone and WebRTC with the exit location. A German residential IP paired with a US English locale and a New York timezone is an obvious mismatch. Set both to match the proxy, not your own desk.
- Save, then check the profile list. Each row shows the profile’s protocol and IP:port in the Proxy column next to its run state. It is the fastest way to spot a profile you forgot to configure before you open ten at once.
When the connection string will not parse
Two edge cases break the parser. Passwords containing special characters such as @, :, / or # may need URL encoding, so encode the password and paste again. IPv6 addresses must be wrapped in square brackets, otherwise the parser reads the address’s own colons as port separators. If the port ends up in the password box, that is the parser telling you one of these two rules was broken.
Setting one default proxy for every new profile
Settings contains a “Default proxy for new profiles” option. Fill it in once and every new profile starts pre-filled with the same endpoint, which saves time when a client’s whole account set sits behind one static residential gateway. Individual profiles can still override it, so it is a starting point rather than a lock. Remember that this panel only applies inside Kameleo — it does not change the system proxy for browsers or apps outside the app.
How to Test a Kameleo Proxy Before You Launch
The Test Proxy tool answers one question: can Kameleo reach the public web through this endpoint? It checks three sites in sequence and falls back when one is unreachable, which is why a proxy that works in another tool can still test badly here.
| Test result | What it means | What to do |
|---|---|---|
| Working | The endpoint forwards traffic and the check sites respond. | Launch and verify the exit IP in the browser. |
| Partial success | The proxy works but is degraded, commonly because it has no IPv6 route. | Usable for browsing; expect slow or failing IPv6 requests. Ask the provider about IPv6 support if it matters. |
| Failing / HTTP 503 | The test failed, so the browser does not start. SDK calls raise an exception. | Check credentials, port and protocol; test the same endpoint outside Kameleo. |
| Timeout, no response | Nothing came back — usually a firewall, wrong port or an expired subscription. | Confirm the port is open and the plan is active in the provider dashboard. |
HTTP vs SOCKS5 vs SSH: Choosing the Right Kameleo Proxy Type
| Protocol | Best for | Watch out for |
|---|---|---|
| HTTP / HTTPS | Standard browsing, account work, storefront and CMS sessions | Cheap HTTP endpoints are often shared datacenter IPs, so check what you are buying |
| SOCKS5 | Mobile-network setups and profiles that should look like a phone connection | No UDP tunnelling in Kameleo; IPv6 gaps show up as partial_success |
| SSH | Servers you already control, tunnelled traffic for technical teams | Needs an SSH host and credentials prepared in advance, outside the proxy dashboard |
Setup walkthroughs for Kameleo usually suggest SOCKS5 for mobile profiles and HTTP/HTTPS for ordinary browsing and account management. That split is pragmatic: mobile endpoints are commonly sold as SOCKS5, while static residential HTTP endpoints keep the same exit address for as long as the session holds. If you are still choosing between protocols generally, this SOCKS5 proxy explained walkthrough covers what changes at the transport level.
Adding a Kameleo Proxy Through the Local API and SDKs
Kameleo’s Local API runs at http://localhost:5050 by default. The desktop app must be running, and port 5050 must not be blocked by a firewall, or every call fails with a connection error that looks like a proxy problem but is not. SDKs exist for Python, JavaScript and C#, and the free tier is documented at 60 API requests per minute.
You can test an endpoint without creating a profile at all: pass host, port and credentials directly to the general test_proxy / testProxy call. That is the cheapest way to screen a list of proxies before you attach any of them. Creating a profile with a proxy attached uses create_profile; re-testing an attached proxy uses test_profile_proxy; changing it uses update_profile — and the profile must be stopped first.
from kameleo.local_api_client import KameleoLocalApiClient
from kameleo.local_api_client.models import (
Server,
UsernamePasswordCredentials,
CreateProfileRequest,
)
client = KameleoLocalApiClient(endpoint="http://localhost:5050")
proxy = Server(
host="gate.example.com",
port=1080,
id="socks5",
secret=UsernamePasswordCredentials(username="user", password="pass"),
)
# 1. Screen the endpoint on its own - no profile needed.
# A failing test comes back as HTTP 503 and the SDK raises.
try:
result = client.test_proxy(body=proxy)
status = result.status
except Exception as exc:
status = "failing: {}".format(exc)
print(status) # working / partial_success / failing
# 2. Only build the profile if the proxy answered.
if status == "working":
profile = client.create_profile(body=CreateProfileRequest(proxy=proxy))
print(profile.id)
How to Confirm the Exit IP and Geo After Launch
A passing test proves reachability, not location. Open the profile, load api.ipify.org, and compare that IP with the one shown in your proxy provider’s dashboard. If they differ, traffic is leaving through a different gateway than you configured — usually a rotating endpoint that has already moved on.
Next, check the clock. Your browser’s timezone should match the city of the exit IP, and the page language should match the locale you set in the steps above. WebRTC is the third check: a leak test should report the proxy’s address, never your home IP. Kameleo resolves DNS through the proxy, so a DNS result showing your internet provider means traffic is not being carried the way you assumed.
Pitfalls That Break a Kameleo Proxy Setup
1. Changing the proxy while the profile is running
Kameleo does not support rotating the proxy mid-session. The profile must be stopped before its proxy settings are changed. Editing the fields while the browser is open either fails silently or leaves you looking at an IP that no longer matches the configuration on screen.
2. Special characters in the password
An @ or : inside a password breaks the connection-string parser. URL-encode the password and paste again, or skip the string format and fill in the individual fields, which is not affected by special characters.
3. IPv6 addresses without brackets
An IPv6 proxy address must be wrapped in square brackets in a connection string, or the parser reads the colons as port separators. If your provider hands you an IPv6 endpoint, format it carefully the first time and store the working string.
4. Misreading partial_success as a failure
A partial success is a usable proxy with a degraded path, frequently an IPv6 problem. For static browsing it usually changes nothing. If you are loading heavy web apps and seeing timeouts, ask the provider whether the endpoint has an IPv6 route.
5. Assuming the setting is system-wide
Kameleo’s proxy panel applies inside Kameleo only. Other browsers and desktop apps on the same machine keep using your normal connection. If you need the whole device behind a proxy, that is a separate configuration outside the app.
6. Rotating proxies that move mid-session
A rotating endpoint can hand you a new IP between the test and the launch, which breaks the timezone and locale you aligned. For long account sessions, use a static residential endpoint and keep rotation for short reads. The trade-offs are laid out in this rotating proxy setup guide.
7. Budgeting by profile count instead of concurrency
Kameleo’s tiers are built around how many browsers run at once. Buying 200 proxies for 200 saved profiles when your plan allows 10 concurrent browsers wastes most of that spend. Match proxy count to your concurrency limit first, then scale both together.
🏆 Send.win Verdict
Kameleo gives you fine-grained proxy control and a scripting layer, and this guide exists because that control has sharp edges. If your work is hands-on rather than scripted, Send.win takes a different route: every isolated browser profile carries its own proxy — residential proxies included on Pro and Team, or your own HTTP/SOCKS5 endpoint — and timezone, locale, WebRTC and geolocation follow the proxy’s exit IP automatically, so the alignment step is not something you can forget. Profiles are shared with paid teammates who open them already signed in, and the whole thing runs as a desktop app for Windows, macOS and Linux or as a cloud browser on Send.win’s server in Helsinki. Every profile is opened and managed by hand, and there is no free trial — the free cloud demo is the way to look before you buy.
See Send.win plans — Pro from $19/mo (or $83.88/yr) with 150 profiles, 5 GB of proxy bandwidth and 6 seats, backed by a 7-day money-back guarantee on your first card purchase. Try the free cloud demo first if you want a look with no card.
Frequently Asked Questions
How do I add a proxy to a Kameleo profile?
Open the profile’s Proxy settings, choose the protocol, then paste a connection string in the form username:password@hostname:port or fill in the host, port and credential fields manually. Run Test Proxy before saving, and confirm the protocol and IP:port appear in the profile list’s Proxy column.
Which proxy type should I use in Kameleo, HTTP or SOCKS5?
Use HTTP/HTTPS for standard browsing and account work, and SOCKS5 for mobile profiles, which is how most providers sell mobile endpoints. SSH is for tunnels you control yourself. Kameleo handles DNS through the proxy in all three cases, but it does not support UDP-based proxies.
Why does Kameleo’s Test Proxy fail when my proxy works elsewhere?
The test relies on Google, Archive.org and Wikipedia, so a provider that blocks or throttles those domains causes a failure even though the endpoint is healthy. Check whether your other tool used a different port, protocol or IP allowlist before you change anything in Kameleo.
Can I change a Kameleo profile’s proxy while it is running?
No. The profile must be stopped before its proxy settings are changed, and rotating the proxy mid-session is not supported. Stop the browser, edit the endpoint, re-run the test, then launch again and re-check the exit IP.
How do I confirm Kameleo is really using my proxy’s IP?
Open the launched profile, load api.ipify.org, and compare the result with the IP shown in your proxy provider’s dashboard. Then check that the browser timezone and page language match the exit location, and that a WebRTC check reports the proxy address rather than your home connection.
Is Kameleo’s free plan a trial or a permanent tier?
It is a permanent €0 plan rather than a countdown trial: 2 concurrent browsers, 100 cloud profiles, 300 browser minutes a month and 3 team members, with the Local API and SDKs included at 60 requests per minute. Paid tiers start at Startup, €59/month or €45/month billed annually.
Do I need a separate proxy for each Kameleo profile?
Use the endpoint that matches the network and region the account actually belongs to, rather than putting every profile on one shared exit IP. If the profiles hold different accounts you own or are authorised to manage, a single shared address also makes locale and timezone alignment impossible to get right for all of them at once. Where a platform limits how many accounts one person may hold, follow its rules and use its official multi-account route.
How does Send.win assign a proxy to each profile?
Each isolated profile in Send.win has its own proxy setting: the residential proxies bundled with Pro and Team, or your own HTTP/SOCKS5 endpoint. Timezone, locale, WebRTC and geolocation follow that proxy’s exit IP automatically, so language and clock alignment is not a separate manual step. Pro ships 5 GB of proxy bandwidth a month and Team 20 GB, with extra bandwidth at $6 per GB.
How Send.win Helps With Kameleo Proxy
Send.win is a browser profile manager for professionals and teams: every account gets its own isolated browser profile.
- Isolated profiles – separate cookies, storage and sessions per profile
- Fingerprint protection – each profile keeps its own consistent browser fingerprint, so profiles never share one browser identity
- Desktop app + cloud browser – native app for Windows, macOS and Linux, or run profiles in the cloud with no install
- Residential proxies included – on Pro and Team, with timezone and locale matched to the proxy
- Team sharing – share a signed-in profile with a teammate without sharing the password
Try the free cloud demo — no install — or download the desktop app. Paid plans start at $19/month, and your first card purchase is covered by a 7-day money-back guarantee (see pricing).