Multilogin is a leading antidetect browser: every profile gets its own browser fingerprint. Add a KnoxProxy residential, ISP, or mobile IP so the identity and the IP match.
Launch Multilogin X and go to your profile list.
Click "New Profile" or edit an existing one. Go to the Proxy tab.
Select "HTTP" or "SOCKS5" as the connection type.
Fill in the proxy fields.
Host: gw.knoxproxy.com
Port: 7000 (HTTP) or 7001 (SOCKS5)
Username: your_username
Password: your_passwordFor country targeting, modify the username.
Username: your_username-country-us
# This gives the profile a US residential IPClick "Check Proxy" in Multilogin to verify the connection works and see your exit IP.
{
"proxy": {
"type": "HTTP",
"host": "gw.knoxproxy.com",
"port": 7000,
"username": "your_username-country-us",
"password": "your_password"
}
}Multilogin profiles hold a single proxy identity. For rotation, use -session-{profileId} in the username to get a consistent IP per profile, or omit session for a new IP on each browser launch.
| Problem | Fix |
|---|---|
| Proxy check failed | Verify gw.knoxproxy.com:7000 and your dashboard credentials. Test with curl first. |
| Profile shows wrong country | Add -country-{cc} to username (e.g., -country-gb for UK). |
| Slow page loads | Use ISP proxies for faster, stable connections. Check target-country match. |
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 a different -country-{cc} flag in the proxy username field for each Multilogin profile, and every profile gets its own geo-targeted KnoxProxy IP independently. Profile A can run on US residential IPs while Profile B runs on German IPs at the same time, since the country flag lives in that profile's own proxy configuration.
ISP proxies, also called static residential proxies, work best for Multilogin because they hold one consistent IP address over time instead of rotating, which matches how a real person's browser identity behaves. That stability combines with residential-grade trust to keep each Multilogin profile looking like the same genuine device and network across every session.
Yes, each Multilogin profile should get its own unique proxy identity rather than sharing one IP across profiles. Add -session-{profileId} to the KnoxProxy username for every profile, using that profile's own ID as the session value, so each one holds a consistent IP over time instead of colliding with another profile's traffic on the same address.
Yes. The Multilogin X API accepts the exact same proxy parameters as the desktop app: host, port, username, and password. Pass your KnoxProxy details in the proxy object of the API request body when creating or updating profiles programmatically, including any -country or -session flags in the username, and API-created profiles pick up the proxy right away.
Multilogin randomizes the canvas, WebGL, and font fingerprint for every profile. Detection risk mostly comes from mismatches, not from either tool alone, so give each profile a KnoxProxy IP in the same country as its fingerprint's timezone and language, then keep that pairing fixed with -session-{profileId}.
Rotating residential proxies -- 3 minutes setup, instant activation, 14-day money-back guarantee.