Browsers
Multilogin profiles on a ProxyGuys proxy
In Multilogin the proxy is part of the browser profile. Whoever opens the profile, on whichever computer, goes out through the same mobile IP. That makes it a good fit for teams, as long as the proxy is set up with sharing in mind. Below: attaching the proxy, then the points that matter once several people use it.
What to have ready
- A ProxyGuys proxy with the status Running. If it's Pending, press Start proxy in My Proxies.
- The host and SOCKS5 port from the proxy's SOCKS5 proxy box in the Connection column.
- The username and password, via Copy username and Copy password under Credentials.
- The Multilogin app, signed in to your workspace.
Add the proxy to a profile
In Multilogin, go to Profiles, then Browser, and press Create. In the General section, pick a name your teammates will recognise. Giving the proxy the same name in My Proxies (pencil icon) helps; it's only a label.
Open the Proxy section, choose Custom and set the protocol to SOCKS5.
Multilogin takes the proxy as one line, IP:port:login:password. Build it from the host, the SOCKS5 port, the username and the password, or take it ready-made from ⋮ then Details, whose line already carries the SOCKS5 port.
Multilogin tests the proxy by itself once the line is in. Wait for Proxy check passed; Proxy check failed means a detail is wrong.
Press Create, then find the profile under Profiles and press Start.
Prefer HTTP? It works just as well, provided the profile's port comes from the HTTP proxy box rather than the SOCKS5 one. Write that line by hand, because the Details line holds the SOCKS5 port.
When a team shares the profile
- Use username and password, not the whitelist. The IP whitelist lets listed addresses connect without a login, but teammates in different places connect from different addresses, and every one of them would need to be listed. A login travels with the profile instead.
- Changing the proxy password. Under Credentials, New password (or Set password) opens a field; type 6 to 100 characters using letters, digits and ! # $ % & *, then Save password. Update the profile straight away, since everyone using it needs the new one. This is also the step to take when someone leaves the team.
- Change-IP links. ⋮ then Copy change-IP link gives a link that changes the IP when opened, with no login. Anyone who has it can use it. If it has been shared too widely, ⋮ then New change-IP link replaces it and the old one stops working.
- Give teammates their own dashboard. In Team you can add sub-accounts, assign your proxies to them and revoke access later, so nobody needs your own login to see a proxy's details.
Check from inside the profile
With the profile running, open httpbin.org/ip. The "origin" value is the IP websites see. Teammates checking a location on a geolocation site may get a town or state that doesn't match the dashboard; those sites rely on their own data, which is often off for mobile IPs.
Troubleshooting
- Proxy check failed straight away: look at the port. The SOCKS5 protocol needs the SOCKS5 port; the HTTP port only answers HTTP.
- It worked yesterday and not today: someone may have saved a new password, or pressed Change gateway IP, which moves every proxy on the account to a new host. Copy the host and password again and update each profile that uses them.
- Login rejected: the password was probably retyped by hand. Paste it from Copy password instead.
More on access without a login is in the IP whitelisting guide, and on timed IP changes in the IP rotation guide.