Buy Clean Kameleo Proxy Servers

What is Kameleo, and why does it need proxies?

Kameleo is an antidetect browser and browser-profile management platform. It creates virtual profiles with coordinated fingerprint settings and supports browser automation through a local API.

Kameleo includes a built-in proxy manager, but it does not provide a bundled proxy network. Without an external proxy, a profile uses the IP address of the device running Kameleo.

NodeMaven supplies the connection layer with pre-filtered residential and mobile IPs, granular location targeting, rotating or sticky sessions, and static ISP proxies. This helps each Kameleo profile start with a cleaner, more suitable IP and keep its network identity aligned with its fingerprint settings.

Step 1

Generate a proxy in NodeMaven

Proxy type: Residential, Mobile, or ISP
Location: Select a country, region, city, or ISP where available
Session: Choose Sticky for a consistent profile IP, or Rotating when you need a new IP between stopped sessions
Filtering: Select the IP-quality option that fits your workflow
Protocol: HTTP or SOCKS5

For a browser profile that must keep the same IP over time, use a sticky residential or mobile session or a static ISP proxy. Do not rotate or replace the proxy while the Kameleo profile is running. Stop the profile before changing its IP.

WebRTC and UDP note: Kameleo automatically aligns its WebRTC values with the proxy IP. However, WebRTC traffic can still follow a non-proxied UDP route and expose a different public IP. Read our guide to WebRTC leaks and UDP routing for a detailed explanation.

NodeMaven ISP proxies support UDP in compatible applications, but Kameleo’s Proxy Manager does not accept UDP-based proxy connections. In Kameleo, connect the NodeMaven proxy through HTTP or SOCKS5 and use Kameleo’s WebRTC controls.

After launching the profile, open the NodeMaven Connection Checker inside the same Kameleo browser profile. It compares the regular HTTP exit with browser-reported WebRTC, STUN and TURN routes over UDP and TCP, and HTTP/3 status. Check that the tests do not expose an unexpected public IP. An unavailable UDP result does not automatically indicate a leak—it may mean that Kameleo, the browser, the firewall, or the network blocked that route.

Copy the generated host, port, username, and password.

Step 2

Create or open a Kameleo profile

Open Kameleo Desktop and click New Profile, or edit an existing profile. Select the device type, operating system, browser, language, and fingerprint, then continue to the profile settings.

Match the profile language and location settings to the proxy region to avoid inconsistent fingerprint signals.

Step 3

Enter the NodeMaven proxy details

In the profile’s Connection or proxy section, choose the protocol generated in NodeMaven and enter:

Host: The NodeMaven hostname or IP

Port: The generated port

Authentication: Enabled

Username: The complete generated NodeMaven username

Password: The NodeMaven proxy password

Kameleo can also parse the connection string USERNAME:PASSWORD@HOST:PORT. If the password contains reserved characters, URL-encode them before pasting the combined string.

Step 4

Test the proxy

Click Test Proxy. Kameleo checks the proxy before the browser starts. Continue when the test reports that the proxy works.

A failed test can be caused by an incorrect host, port, protocol, username, password, or an unavailable endpoint. A provider may also block one of the sites used by Kameleo’s test even when the proxy itself is reachable.

Step 5

Review the location and WebRTC settings

Open Advanced Settings > Location and leave Timezone, Geolocation, and WebRTC on Automatic, which is Kameleo’s recommended desktop configuration. Kameleo uses the external proxy IP to align these values.

Because HTTP and SOCKS proxies do not normally carry browser UDP traffic, run a WebRTC leak test after launch. If the workflow does not require WebRTC and the test exposes the original IP, use Kameleo’s Block option or configure TCP-only WebRTC through the local API.

Step 6

Save, start, and verify the profile

Click Save & Start. In the opened browser, visit an IP-check and WebRTC-leak test page. Confirm that the public IP and detected location match the NodeMaven proxy and that the original IP is not exposed.

Your NodeMaven proxy is now connected to the Kameleo profile.

Step 1

Start the Kameleo Engine and prepare Python

Open Kameleo Desktop and leave it running. Launching the desktop application starts the Kameleo Engine automatically. By default, its local API is available at:

http://localhost:5050

macOS or Linux
Open Terminal and create a separate Python environment:

python3 -m venv kameleo-env
source kameleo-env/bin/activate

Install Kameleo’s official Python SDK:

python3 -m pip install kameleo.local-api-client

Confirm that the SDK was installed:

python3 -m pip show kameleo.local-api-client

Windows PowerShell

Open PowerShell and run:

py -m venv kameleo-env
.\kameleo-env\Scripts\Activate.ps1
py -m pip install kameleo.local-api-client
py -m pip show kameleo.local-api-client

When the environment is active, the Terminal or PowerShell prompt should begin with:

(kameleo-env)

To confirm that the Kameleo Engine is running, open the following address in your browser:

http://localhost:5050/swagger

If the Kameleo API page loads and the SDK information appears in the terminal, the environment is ready.

Important: Kameleo recommends keeping the SDK’s major and minor version aligned with the installed Engine version.

Step 2

Store the NodeMaven proxy details securely

The Python script will read the proxy details from environment variables. This keeps the username and password outside the source code.

First, copy these values from the NodeMaven dashboard:

Protocol
Host
Port
Complete username
Password

Use the exact values displayed in NodeMaven. Do not enter placeholder values such as your_generated_host.

macOS or Linux

For an HTTP proxy, set the protocol, host, and port:

export NODEMAVEN_PROXY_TYPE="http"

export NODEMAVEN_PROXY_HOST="gate.nodemaven.com"

export NODEMAVEN_PROXY_PORT="8080"

Replace the host and port if your dashboard displays different values. If you generated a SOCKS5 endpoint, use:

export NODEMAVEN_PROXY_TYPE="socks5"

Enter the username and password through hidden prompts (enter line by line):

read -s -p "NodeMaven proxy username: " NODEMAVEN_PROXY_USER; echo

read -s -p "NodeMaven proxy password: " NODEMAVEN_PROXY_PASS; echo

export NODEMAVEN_PROXY_USER NODEMAVEN_PROXY_PASS

Nothing will appear when you paste the credentials. This is expected.

If macOS displays an error because Terminal is using zsh, use these commands instead:

read -s "NODEMAVEN_PROXY_USER?NodeMaven proxy username: "; echo

read -s "NODEMAVEN_PROXY_PASS?NodeMaven proxy password: "; echo

export NODEMAVEN_PROXY_USER NODEMAVEN_PROXY_PASS

Confirm that all five variables are set:

[ -n "$NODEMAVEN_PROXY_TYPE" ] && echo "Proxy type: set"

[ -n "$NODEMAVEN_PROXY_HOST" ] && echo "Proxy host: set"

[ -n "$NODEMAVEN_PROXY_PORT" ] && echo "Proxy port: set"

[ -n "$NODEMAVEN_PROXY_USER" ] && echo "Proxy username: set"

[ -n "$NODEMAVEN_PROXY_PASS" ] && echo "Proxy password: set"

Windows PowerShell

Set the protocol, host, and port:

$env:NODEMAVEN_PROXY_TYPE = "http"

$env:NODEMAVEN_PROXY_HOST = "gate.nodemaven.com"

$env:NODEMAVEN_PROXY_PORT = "8080"

Replace the host and port with the values from NodeMaven. Use socks5 instead of http only for a SOCKS5 endpoint.

Enter the username and password without displaying them:

$secureUser = Read-Host "NodeMaven proxy username" -AsSecureString

$env:NODEMAVEN_PROXY_USER = [System.Net.NetworkCredential]::new("", $secureUser).Password




$securePass = Read-Host "NodeMaven proxy password" -AsSecureString

$env:NODEMAVEN_PROXY_PASS = [System.Net.NetworkCredential]::new("", $securePass).Password

Confirm that the variables are set:

if ($env:NODEMAVEN_PROXY_TYPE) { "Proxy type: set" }

if ($env:NODEMAVEN_PROXY_HOST) { "Proxy host: set" }

if ($env:NODEMAVEN_PROXY_PORT) { "Proxy port: set" }

if ($env:NODEMAVEN_PROXY_USER) { "Proxy username: set" }

if ($env:NODEMAVEN_PROXY_PASS) { "Proxy password: set" }

Continue to the next steps in the same terminal session. If you close the terminal, you must set the variables again.

Step 3

Create the Python script

Make sure you are still using the terminal where (kameleo-env) is active and the proxy variables are set.

macOS or Linux

Create the script with Nano:

nano nodemaven_kameleo.py

Windows PowerShell

Open the script in Notepad:

notepad nodemaven_kameleo.py

Paste the following code:

import os




from kameleo.local_api_client import KameleoLocalApiClient

from kameleo.local_api_client.models import (

    BrowserSettings,

    CreateProfileRequest,

    Preference,

    ProxyChoice,

    Server,

)





client = KameleoLocalApiClient(

    endpoint="http://localhost:5050"

)

client.verify_engine_ready()




fingerprints = client.fingerprint.search_fingerprints(

    device_type="desktop",

    browser_product="chrome",

)




if not fingerprints:

    raise RuntimeError("No compatible fingerprint was found.")




profile = client.profile.create_profile(

    CreateProfileRequest(

        fingerprint_id=fingerprints[0].id,

        name="NodeMaven proxy profile",

        proxy=ProxyChoice(

            value=os.environ["NODEMAVEN_PROXY_TYPE"],

            extra=Server(

                host=os.environ["NODEMAVEN_PROXY_HOST"],

                port=int(

                    os.environ["NODEMAVEN_PROXY_PORT"]

                ),

                id=os.environ["NODEMAVEN_PROXY_USER"],

                secret=os.environ["NODEMAVEN_PROXY_PASS"],

            ),

        ),

    )

)




result = client.profile.test_profile_proxy(profile.id)

print("Proxy test:", result.result)




if result.result not in ("success", "partial_success"):

    raise RuntimeError("The proxy test did not pass.")




client.profile.start_profile(

    profile.id,

    BrowserSettings(

        preferences=[

            Preference(

                key="webrtc.ip_handling_policy",

                value="disable_non_proxied_udp",

            )

        ]

    ),

)

This script:

Connects to the locally running Kameleo Engine
Selects a desktop Chrome fingerprint
Creates a Chroma profile
Reads the NodeMaven proxy details from the environment variables
Tests the proxy before starting the profile
Prevents non-proxied WebRTC UDP connections
Starts the Kameleo browser profile

The WebRTC preference above is intended for a Chroma profile. For a Junglefox profile, replace it with:

Preference(

    key="media.peerconnection.ice.proxy_only",

    value=True,

)

Save the file in Nano

Press:

Control + O
Enter to confirm the filename
Control + X

In Notepad, choose File > Save, then close the editor.

Step 4

Check the script for syntax errors

Before running the integration, check that the Python file has valid syntax.

macOS or Linux

python3 -m py_compile nodemaven_kameleo.py

Windows PowerShell

py -m py_compile nodemaven_kameleo.py

If the command returns to the prompt without displaying an error, the syntax check passed.

For a clearer screenshot, run:

macOS or Linux

python3 -m py_compile nodemaven_kameleo.py \

  && echo "Python syntax check: passed"

Windows PowerShell

py -m py_compile nodemaven_kameleo.py

if ($LASTEXITCODE -eq 0) { "Python syntax check: passed" }

Step 5

Run the script and test the proxy

Keep Kameleo Desktop open and run the script from the same terminal session where the proxy variables were set.

macOS or Linux

python3 nodemaven_kameleo.py

Windows PowerShell

py nodemaven_kameleo.py

Kameleo tests the proxy before opening the profile. The terminal should report one of these results:

success: All proxy checks passed.
partial_success: The proxy is usable but one check, commonly IPv6, was unavailable.
failure: The connection checks failed. Kameleo normally returns this as a 503 error, and the profile will not start.

A successful run should open the Kameleo browser profile automatically.

If the connection fails, confirm that:

Kameleo Desktop and the local Engine are running
The host and port match the NodeMaven dashboard
The correct http or socks5 protocol was selected
The complete username and password were entered
Your NodeMaven plan is active
You are running the script in the same terminal where the environment variables were set

Note: Every execution of this example creates a new Kameleo profile. Remove unused test profiles from Kameleo after finishing your screenshots.

Step 6

Verify the IP and WebRTC routes

Inside the newly opened Kameleo browser profile, open the NodeMaven Connection Checker.

Check that:

The HTTP exit IP matches the NodeMaven proxy
The detected location matches the location selected in NodeMaven
WebRTC does not expose an unexpected public IP
STUN and TURN results do not reveal your original public address

An unavailable UDP result does not automatically mean that the proxy failed or leaked your IP. Kameleo, the browser, your firewall, or your local network may block that route.

For more information, read the guide to WebRTC leaks and UDP routing.

Important: Do not change the proxy while the Kameleo profile is running. Stop the profile first, update its proxy settings, test the new connection, and then restart it.

Your NodeMaven proxy is now connected to Kameleo through the local API.

Residential Proxies

Pre-filtered household IPs with rotating and sticky sessions and granular location targeting. Use a sticky session for an active Kameleo profile; rotate only after stopping it

Buy now

Mobile Proxies

Real 4G, 5G, and LTE carrier IPs for mobile-first targets and workflows that specifically require a mobile-network identity. Sticky mode is recommended during an active profile

Buy now

ISP proxies

Dedicated static residential IPs with long sessions, high speed, unlimited traffic, and UDP support in compatible applications. In Kameleo, configure them through HTTP or SOCKS5 because Kameleo does not accept UDP-based proxies

Buy now

Not sure which proxy type to choose?

Chat with us

A unique antidetect phone solution built for managing mobile accounts at scale

«NodeMaven works closely with Geelark to support reliable mobile multi-account workflows, tested and proven in daily use».

Cloud phones & multi-account platform built for social media management

«The only high-quality proxy provider we’ve chosen to integrate with. Nodemaven provides clean, stable traffic to power our workflows».

A leading antidetect browser trusted by users around the world

«We recommend NodeMaven as the #1 proxy service for multi-accounting.  It integrates closely with Dolphin Anty to ensure smooth setup».

The #1 Anti-detect Browser Trusted By 9M+ Users

«NodeMaven delivers reliable, high-quality proxies that integrate seamlessly with AdsPower. Together, we make multi-account management smoother, more stable, and easier to scale».

An all-in-one antid-etect browser built for secure and scalable multi-account management

«NodeMaven provides stable, high-quality proxies that work smoothly, supporting secure and efficient multi-account workflows».

The world's most trusted multi-account management expert

«BitBrowser partners with NodeMaven to create a robust anti-detect environment. Multi-account advertising and social media management can easily mitigate the risk of account locking. Using the NodeMaven security proxy ensures stability and protects local data privacy. Clean, high-quality, and stable. We recommend NodeMaven».

Anti-detect browser and cloud phone platform for secure multi-account management at scale

«NodeMaven is the proxy provider our users recommend most in our community. It delivers high-quality, stable IPs that matter most for multi-account professionals who need reliability at scale».

Yes. Add proxy details manually to a Kameleo Desktop profile, or use Kameleo’s local API through its official Python, JavaScript, or C# SDK. The Engine must be running for API-based setup.

Kameleo includes a built-in proxy manager, but it does not bundle a proxy network or subscription. You must connect a third-party proxy such as NodeMaven.

Kameleo accepts HTTP/HTTPS, SOCKS5, and SSH proxy inputs. NodeMaven residential, mobile, and ISP connections can be added using HTTP or SOCKS5.

Enter the host, port, username, and password in separate fields, or paste USERNAME:PASSWORD@HOST:PORT. URL-encode reserved characters when using the combined connection string.

Use sticky residential/mobile sessions or a static ISP proxy while a profile is active. If rotation is required, stop the profile first, change the proxy, retest it, and then restart the profile.

Kameleo automatically aligns WebRTC values with the external proxy IP when WebRTC is set to Automatic. Its developer documentation also warns that non-proxied UDP may expose the real IP, so test the launched profile and use the documented TCP-only setting for automation when needed.

How do I test a NodeMaven proxy in Kameleo?

Use Test Proxy before starting the profile. After launch, verify the public IP, detected location, DNS behavior, and WebRTC result with independent testing pages.

A partial result commonly means that IPv4 and location checks passed but the proxy has no IPv6 route. Kameleo describes this as usable but degraded for targets that do not require IPv6.

No. Kameleo advises stopping the profile before updating the proxy. Switching IPs mid-session can produce network inconsistencies and additional authentication challenges.

Check the protocol, host, port, complete username, password, account balance, and proxy availability. Confirm that the endpoint allows access to the sites used by Kameleo’s proxy test.

Free proxies are often shared, unstable, slow, or already blocked. A managed pre-filtered proxy service provides more predictable location targeting, session control, and IP quality for recurring Kameleo workflows.