To do a Multilogin proxy setup, open the profile's Proxy section, choose a custom proxy, pick SOCKS5 and paste your proxy as HOST:PORT:USER:PASS. Multilogin then checks the connection for you.
An Elusive proxy is SOCKS5 with a username and password. That is exactly what Multilogin's custom proxy option takes, so there is nothing to convert. Use one proxy per profile and you are done in a few minutes.
The rest of this guide covers the steps, the checks to run afterwards and the errors people hit most.
Key takeaways
- Add the proxy in the profile's Proxy section: Custom, protocol SOCKS5.
- Paste the whole line from the dashboard: HOST:PORT:USER:PASS.
- Check the connection, then set timezone, language and location to match the proxy IP.
- Run a DNS and WebRTC leak check in the profile before you log in anywhere.
- Keep one proxy per profile for accounts you plan to keep.
What you need
You need two things: a Multilogin profile and an Elusive SOCKS5 proxy. Pick the proxy in the catalog, and copy the line shown in your dashboard. It looks like HOST:PORT:USER:PASS.
For accounts you log into again and again, a sticky residential or mobile proxy is the usual choice. Residential uses real home connections, mobile uses 4G/5G carrier IPs. Hosting proxies are fast and cheap but trusted less by consumer platforms. Which proxy for which job explains the differences.
Sticky proxies are rented per proxy, with no bandwidth cap. You can see them and their filters (country, city, ISP and more) on the pricing and catalog section.
Add the proxy to a new Multilogin profile
Menu names change between versions, so match the steps below to what your app shows. They follow Multilogin's own help pages.
- Create a new browser profile, or open an existing one for editing.
- Find the Proxy section in the profile settings.
- Choose Custom as the proxy type.
- Choose SOCKS5 as the protocol.
- Paste the proxy in the format IP:port:login:password, which is the same as HOST:PORT:USER:PASS.
- Save the profile.
Multilogin's help says it checks the proxy automatically after you enter it and tells you whether it connected.
Check the connection
Do not trust the first green message alone. Start the profile and open an IP lookup page inside it. The IP you see should be the proxy's IP, and the country and city should match the listing you picked.
Different lookup sites sometimes name a different city for the same IP, because their location databases do not agree. A small difference is normal. A different country is not, and it is a reason to contact support. If your proxy is a sticky one, a failed live test within its first hour can be refunded to your balance.
Make timezone, language and location follow the proxy
An account that logs in from Texas while the browser says it is in another timezone looks odd to a platform. Set the profile's timezone, language and geolocation to match the proxy IP.
In Multilogin's settings, look for options that take these values from the proxy's IP. The wording differs between versions, so use whichever setting in your profile ties them to the IP. If you set them by hand, copy the proxy's city and its local language. The full walkthrough is in match timezone to proxy.
Run a leak check in the profile
Before the first login, open the profile and run two tests.
- A DNS test, to see that no DNS server from your own provider shows up: DNS leak check.
- A WebRTC test, to see that your real IP is not shown next to the proxy IP: WebRTC leak test.
Do this once for each new profile. If either test shows your own network, fix the profile before you open any account.
One profile per proxy
For accounts you keep, give each account its own profile and its own proxy. Then each account has one steady location, and its logins look consistent from one day to the next. Do not move a proxy between profiles, and do not run two accounts through the same profile.
A proxy does not make anything allowed that a platform's rules forbid. Follow each platform's terms, and use its own team tools, such as staff accounts or business managers, where they exist.
Common errors
HTTP chosen instead of SOCKS5. Elusive proxies are SOCKS5 only. If the protocol is set to HTTP or HTTPS, the check fails. Switch it to SOCKS5.
Spaces from copy-paste. A space before or after the line, or inside it, breaks the login. Paste again and make sure there is nothing before HOST and nothing after PASS.
An expired sticky proxy. A sticky proxy keeps its IP up to 24 hours. After that it is gone, and the profile shows a failed check. Pick a new proxy and replace it in the profile.
A proxy that is offline. Residential and mobile proxies run on real devices. A device can be switched off, or the ISP can change its IP, so a sticky IP can drop before 24 hours. Choose another proxy from the catalog.
Limits
A proxy only changes the IP and location the site sees. It does not set up your profile for you, and it does not fix a leaking setup. If a profile uses an IP you want to keep for months, a sticky proxy is not the right tool, and the which-proxy guide linked above will point you to a better fit.
FAQ
Does Multilogin support SOCKS5 proxies with a password?
Yes. Multilogin's custom proxy option lists SOCKS5, and it takes a login and password along with the host and port.
Can I paste the whole proxy line at once?
Multilogin's help describes the IP:port:login:password format for custom proxies in regular profiles. That is the same order as HOST:PORT:USER:PASS from your Elusive dashboard.
Why does my Multilogin proxy check fail?
Check the protocol first, then look for spaces in the pasted line. If both are fine, the proxy may be offline or past its sticky time, so try another one.
Do I need a new proxy for every profile?
For accounts you keep, yes. One proxy per profile keeps each account on one steady location.