Team-focused antidetect browser with powerful API-driven profile management. Connect KnoxProxy to Octo Browser for reliable fingerprint masking with geo-targeted residential and ISP proxies across all your team profiles.
Launch Octo Browser and navigate to your profile list.
Click "Create Profile" or open an existing profile for editing.
In the profile editor, switch to the "Proxy" section.
Choose "HTTP" or "SOCKS5" from the connection type dropdown.
Fill in the proxy fields with your KnoxProxy credentials.
Host: gw.knoxproxy.com
Port: 7000 (HTTP) or 7001 (SOCKS5)
Username: your_username
Password: your_passwordClick "Check Proxy" to verify KnoxProxy connects and shows the correct IP and location.
// POST https://app.octobrowser.net/api/v2/automation/profiles
{
"title": "KnoxProxy US Profile",
"fingerprint": {
"os": "win"
},
"proxy": {
"type": "HTTP",
"host": "gw.knoxproxy.com",
"port": 7000,
"login": "your_username-country-us",
"password": "your_password"
}
}Append -session-{profileId} to the username for a sticky IP per profile, or omit the session flag to get a fresh IP on each profile launch.
| Problem | Fix |
|---|---|
| Proxy check failed in Octo Browser | Verify gw.knoxproxy.com with port 7000 (HTTP) or 7001 (SOCKS5) and check your dashboard credentials. |
| Profile shows wrong country | Add -country-{cc} to your username, e.g. your_username-country-de. |
| API returns 401 Unauthorized | Regenerate your API token from the Octo Browser dashboard under Settings > API. |
USER-country-de-city-berlin-session-profile07Order matters -- geo flags before the session flag. The session name is free text; use the profile ID so the mapping is self-documenting. Password stays as issued; no flags belong there. HTTP on :7000, SOCKS5 on :7001, same credentials.
Yes. Set -country-{cc} in the proxy username field for each profile individually, for example your_username-country-us for a US profile and your_username-country-de for Germany. Each profile then connects to KnoxProxy through the same gw.knoxproxy.com gateway but exits from a different country, with no extra configuration beyond the username.
Yes. Each team member can use their own KnoxProxy credentials in Octo Browser, or the whole team can share one account with session-based separation, appending a different -session-{profileId} to the username per profile. This keeps each team member's traffic on a distinct exit IP while still using a single KnoxProxy account.
Append -session-{profileId} to your KnoxProxy proxy username in the profile's Proxy tab. This pins a sticky exit IP to that specific profile across restarts and relaunches, so the same profile always appears from the same address instead of rotating to a new IP each time you open Octo Browser.
Yes. POST to the /api/v2/automation/profiles endpoint and pass your KnoxProxy host, port, login, and password inside the proxy object for each profile, as shown in the sample JSON payload above. Add a -country-{cc} suffix to the login field so every bulk-created profile launches with its own geo-targeted KnoxProxy exit IP.
Rotating residential proxies -- 3 minutes setup, instant activation, 14-day money-back guarantee.