How to set up residential proxies in Multilogin
Published: 23 July 2026 · 5 min read
TL;DR: In Multilogin X, open a profile's Proxy step, set connection type to SOCKS5 (or HTTP), host gw.roamproxy.com, port 41080, and your Roam gateway username and password. Give each profile its own sticky IP so the fingerprint and the exit IP stay consistent, click Check proxy to confirm the country, then launch. The mismatch that gets antidetect profiles flagged is a rotating IP behind a fixed fingerprint - avoid it by pinning one session per profile.
Why the proxy matters in an antidetect browser
Multilogin gives each profile a distinct, believable browser fingerprint. That fingerprint only holds up if the network behind it is just as believable. A clean, unique fingerprint coming out of a datacenter IP - or a residential IP that changes city between requests - is a contradiction that fraud systems are specifically built to catch. The proxy is not an add-on to your antidetect setup; it is half of it.
The rule that follows from this is simple: one profile, one sticky residential IP. Set it once, keep it for the life of the account.
Step 1: Open the Proxy step of a profile
In Multilogin X, create a new profile or edit an existing one. Choose the browser core you need - Mimic (Chromium-based) or Stealthfox (Firefox-based) - then open the Proxy section of the profile settings.
Step 2: Enter the Roam gateway details
Fill in the proxy fields:
| Field | Value |
|---|---|
| Connection type | SOCKS5 (or HTTP) |
| Host / Address | gw.roamproxy.com |
| Port | 41080 |
| Login | your Roam gateway username |
| Password | your Roam gateway password |
Your gateway username is where geo-targeting and session control live. To keep one country and one sticky IP for this profile, use a sticky session in the username - see rotating vs sticky sessions for how the session string works. Assign a different sticky session to each profile so no two profiles ever share an exit IP.
Avoid special characters in the password. Multilogin builds a connection string from these fields, so a #, @, /, or : inside the password can break the parse and make an otherwise-correct proxy fail its check. If your password contains one, regenerate it without those characters rather than fighting the encoding.
Step 3: Check the proxy before you launch
Click Check proxy. Multilogin will connect through Roam and report the detected IP and its geolocation. Confirm the country matches what you targeted. If the check fails, work through the FAQ below - it is almost always credentials, protocol/port mismatch, or your own network not being able to reach the gateway.
Once the check passes, save and launch the profile. From that point every request the profile makes - page loads, XHR, WebRTC - exits from the Roam residential IP, matched to the fingerprint Multilogin assigned.
Step 4: Verify from inside the profile
Launch the profile and visit an IP-check site such as https://ip.sb. It should show the Roam exit IP and the country you selected, not your real address. For a more thorough check, a fingerprint/leak test page will confirm there is no WebRTC or DNS leak exposing your real IP alongside the proxy.
If the profile opens but pages do not load, see proxy connected but websites won't load.
Scaling to many profiles
When you run tens or hundreds of profiles, the discipline is always the same:
- One sticky session per profile - never reuse an exit IP across profiles you want kept separate.
- Match the geo to the account - a profile posing as a Berlin user should exit from Germany, consistently.
- Pay for what you use - Roam is $2/GB pay-as-you-go, so idle profiles cost nothing and a burst of activity is billed by the gigabyte, not per profile.
For antidetect work specifically, our proxies for antidetect browsers page covers the wider setup, and we have matching guides for AdsPower, GoLogin, and Hubstudio.
FAQ
Should each Multilogin profile have its own proxy?
Yes, and it should be its own consistent IP. The whole point of an antidetect browser is that each profile looks like a separate real person, and a real person does not change ISP and city between page loads. Give every profile a sticky residential session so its exit IP stays put for the life of the account. Sharing one IP across many profiles, or letting a profile rotate IPs mid-session, is the pattern that links accounts together or trips a fraud score.
Should I pick SOCKS5 or HTTP in Multilogin?
Either works with Roam on the same gateway; the practical difference is small for browser traffic. SOCKS5 is a lower-level tunnel that also carries DNS to the exit, which is what you want for geo-accurate results. Choose SOCKS5 unless you have a specific reason to use HTTP. In Multilogin the setting is the Connection type dropdown in the profile's Proxy step.
Multilogin says the proxy check failed - what do I look at first?
Three things, in order. First, the credentials: a special character such as # in the password can break the connection string - if in doubt, generate a password without #, @, /, or :. Second, the protocol: make sure Connection type matches the port you entered. Third, reachability: if your own network cannot reach gw.roamproxy.com:41080 at all, the check will time out regardless of credentials - test the gateway from a plain browser or curl first.
Does this work with both Mimic and Stealthfox profiles?
Yes. The Proxy step is identical whether the profile uses the Mimic (Chromium) core or the Stealthfox (Firefox) core - same connection type, host, port, and credentials. Pick the core you need for the site you are working with; the Roam proxy configuration does not change.
Roam gives you SOCKS5 and HTTP access to rotating residential IPs at $2/GB and dedicated static residential IPs at $4/IP per month, on one gateway that drops straight into Multilogin. Create an account and get 300MB of free trial traffic to test a profile end to end before you scale.