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} in the proxy username for each profile. Profile A can use US IPs while Profile B uses German IPs.
ISP (static residential) proxies are ideal for Multilogin because they provide a stable, consistent IP with residential trust for each browser identity.
Each profile should use a unique proxy identity. Use -session-{profileId} in the username so each profile gets its own consistent IP.
Yes. The Multilogin X API accepts the same proxy parameters. Pass KnoxProxy details in the proxy object when creating profiles via API.
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}.
Free trial on rotating residential -- 3 minutes setup, no credit card.