Multilogin With a Mobile Proxy: Adding ProxyGuys to a Browser Profile
Updated
Multilogin keeps every browser profile apart, each with its own cookies, storage and fingerprint. For a profile to pass as a separate person, its traffic also needs its own address, and that is the part a ProxyGuys mobile proxy supplies. This walkthrough covers what to copy from the dashboard, where it goes in Multilogin, how to confirm it works, and how to keep profiles steady over weeks of use.
Step 1: get the proxy ready
In My Proxies, the proxy should read Running; press Start proxy if it is still Pending. Then collect its details from one of two places:
- ⋮ menu → Details shows the proxy as
host:port:username:password, plus a SOCKS5 URL. The port in that line is the SOCKS5 port. - The proxy itself: the HTTP proxy and SOCKS5 proxy addresses (host and port), Copy username under Credentials, and the eye button (Show / hide) or Copy password for the password.
Handy habit: rename the proxy after the profile it serves, using the pencil icon next to its name (up to 60 characters). The name is only a label; the login does not change.
Step 2: decide between HTTP and SOCKS5
Each proxy accepts both, on different ports, and either is fine for a browser profile. What matters is that the type you choose in Multilogin matches the port you enter: the HTTP port for HTTP, the SOCKS5 port for SOCKS5. A mismatch is one of the usual reasons a proxy check fails.
Step 3: enter the proxy in the profile
Create a new profile, or open the settings of an existing one, and go to its proxy section. Multilogin's screens change between versions, so the steps below describe the settings rather than exact labels:
- Choose to use your own (custom) proxy.
- Set the type to HTTP or SOCKS5.
- Enter the host shown on your proxy.
- Enter the port that matches the type.
- Enter the username and password from the Credentials column.
- If your version offers a connection check, run it before saving.
Some versions accept a pasted proxy line. If yours takes the host:port:username:password format, the line from ⋮ → Details can go in as it is, with the type set to SOCKS5: its port is the SOCKS5 port, so it will not work as an HTTP proxy.
Step 4 (alternative): connect by IP whitelist
If the computer running Multilogin has a stable public IPv4 address, you can drop the username and password entirely. Do this from that same computer:
- Open the proxy's ⋮ menu → IP whitelist.
- Press the + your IPv4 chip to add the address you are on, or type one and press Add. Up to 15 addresses fit, and saving replaces the whole list.
- Pick the Protocol (HTTP or SOCKS5) and press Enable IP auth.
- Press Copy endpoint, then enter that address in Multilogin with the matching type and leave the login fields empty.
The username and password keep working on the normal ports alongside the whitelist. On a few servers the whitelist is not available; the window tells you when that is the case.
Step 5: check from inside the profile
Launch the profile and open https://api.ipify.org?format=json. You should see a mobile IP rather than your own. If you look that IP up, the city may differ from the one on your proxy: lookup databases often place mobile IPs in a different city or state, which is normal for mobile networks.
Keeping profiles steady
- One proxy per profile. Two profiles behind the same IP look related to the sites they visit.
- Keep the fingerprint consistent with the IP. Timezone, language and geolocation should agree with the proxy's location. Anti-detect browsers can often fill these in from the IP, which is usually safer than typing values by hand.
- No timer rotation for logged-in accounts. Leave the Rotation setting on No rotation and use Change IP between sessions; it keeps the same city and carrier.
- Expect the odd IP change you did not make. Carriers reassign addresses, and if a phone drops, the proxy moves to another phone at the same location.
- After a Change gateway IP, every proxy on the account sits on a new host IP, so update the host in each profile.