Multilogin proxy setup
Multilogin asks for the proxy on each profile, under the Proxy tab. Choose an external HTTP proxy over the bundled one, fill in the gateway, and the profile browses from a residential IP you control the country of — priced by the GB rather than folded into a seat licence.
Connection details
Swap PROXY_USER / PROXY_PASS for the credentials on your dashboard. New here? Create an account to generate a key.
Multilogin proxy fields
Steer the exit IP from the username
Tips & gotchas
- Use the Check proxy button before saving — it reports the exit IP and country, which is the only confirmation your targeting string parsed.
- Multilogin matches the profile's timezone and WebRTC to the proxy. Pin the IP with a sessid or those two drift apart on the next request.
- Add a city with ;city.newyork after the country when a profile's history should stay local to one metro — that precision is a Residential Premium capability.
Multilogin, answered
How do I use an external proxy in Multilogin?
In the profile's Proxy tab, set the connection type to HTTP (or SOCKS5) rather than the built-in option, then enter gw.proxmint.com, the port, and your username and password. Country targeting goes on the end of the username.
Why does Multilogin flag a timezone mismatch?
It derives the expected timezone from the exit IP. If the IP rotates between checks the two disagree, so pin the profile with a sticky session id and the timezone stays put for the life of that session.
Can I target a city, not just a country?
Yes. Append ;city.newyork to the username after the country key, e.g. PROXY_USER__cr.us;city.newyork;sessid.ml01. Standard residential targets by country only — state, city, ZIP and ASN precision comes with Residential Premium.
Ready to route Multilogin through residential IPs?
Create an account, paste the code above, and we'll add your first 1 GB of residential free on your first top-up. Pay by the GB after that — no subscription.