Enterprise-grade antidetect browser with a REST API for large-scale profile management. Integrate KnoxProxy with VMLogin to automate profile creation with geo-targeted proxies across hundreds of browser profiles.
Launch VMLogin and log into your account.
Click "New Browser Profile" from the main profile list.
In the profile editor, navigate to the "Setting Proxy Server" section.
Choose "HTTP Proxy" or "Socks5 Proxy" from the proxy type dropdown.
Input your KnoxProxy gateway details in the proxy form.
IP Address: gw.knoxproxy.com
Port: 7000 (HTTP) or 7001 (SOCKS5)
User: your_username-country-us
Password: your_passwordClick "Test Proxy" to verify KnoxProxy connectivity. Save the profile when the test passes.
// POST http://127.0.0.1:35000/api/v1/profile/create
{
"name": "KnoxProxy US Profile",
"os": "Windows",
"browser": "Chrome",
"proxyType": "HTTP",
"proxyHost": "gw.knoxproxy.com",
"proxyPort": 7000,
"proxyUser": "your_username-country-us-session-vm001",
"proxyPass": "your_password",
"langBasedOnIp": true
}Use -session-{vmProfileId} in the proxy username for persistent IPs per profile. Remove the session parameter for a new IP on every profile launch.
| Problem | Fix |
|---|---|
| Test Proxy returns "Connection timed out" | Whitelist gw.knoxproxy.com on ports 7000 and 7001 in your firewall and antivirus settings. |
| API returns 500 when creating profile | Verify proxyHost, proxyPort, proxyUser, and proxyPass fields. Ensure proxyType is exactly "HTTP" or "Socks5". |
| Profile opens with direct connection | Re-open the profile editor, verify proxy is set, save, then restart the profile. |
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. POST to the local REST API at 127.0.0.1:35000/api/v1/profile/create with proxyType, proxyHost, proxyPort, proxyUser, and proxyPass fields set to your KnoxProxy details, exactly as shown in the sample payload. This lets you create and launch hundreds of profiles programmatically instead of configuring each one by hand in the GUI.
There is no KnoxProxy-side limit on concurrent profiles; each profile simply requests its own gateway connection to gw.knoxproxy.com. Your VMLogin subscription tier, Standard or above, determines the maximum number of simultaneous profiles you can run, so check your plan limits before scaling up large-scale automation with KnoxProxy.
HTTP on port 7000 is sufficient for most web browsing and covers the majority of VMLogin profile use cases. Choose SOCKS5 on port 7001 instead if your workflow requires non-HTTP traffic or UDP, then select "Socks5 Proxy" from the protocol dropdown in the profile's Setting Proxy Server section and enter the same credentials.
Yes. Launch a profile through the local REST API at 127.0.0.1:35000, retrieve its WebDriver debug port from the response, then point Selenium's remote driver at that port. KnoxProxy handles the proxy layer transparently underneath, so your Selenium script never needs to configure the proxy itself, only navigate and interact with pages.
Rotating residential proxies -- 5 minutes setup, instant activation, 14-day money-back guarantee.