VMLogin Proxy Setup
Give every VMLogin profile its own address and keep it there.
VMLogin runs isolated browser profiles with separate fingerprints and storage. The part it does not solve is the address: two profiles behind one IP are linked no matter how different their fingerprints look. Pointing each profile at its own session id fixes that.
Setup guide
Open the profile proxy settings
Create or edit a profile in VMLogin and find the proxy section of its settings.
Fill in the five fields
Type: HTTP or SOCKS5
Host: proxy.sotaproxy.com
Port: 10000
Login: YOUR_USERNAME_c_US_s_1001_ttl_1h
Password: YOUR_PASSWORDThe country, session id and lifetime are suffixes on the username. Change the number after _s_ for every profile you create.
Check the proxy before launching
Use the built-in check in the proxy form. It returns the exit address, which confirms the suffix parsed. A country you did not ask for means the login string is malformed.
Automate it with the SotaProxy API
Everything above works without opening the dashboard. With an API key, VMLogin can pull fresh proxy credentials, buy new proxies, and renew expiring ones - straight from code.
# Every active proxy on your account (ip, ports, login, password as JSON)
curl -H "Authorization: Bearer $KEY" https://api.sotaproxy.com/api/v1/proxies
# Buy more when you scale (price-check first with POST /quote)
curl -X POST https://api.sotaproxy.com/api/v1/orders \
-H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
-H "Idempotency-Key: my-unique-order-id" \
-d '{"product":"ipv4","countryId":565,"periodId":"1m","quantity":5}'What goes into the profile proxy form
VMLogin asks for five fields and nothing else. Residential targeting rides inside the login, so you never need a separate endpoint per country:
VMLogin has a proxy check built into the form. Run it before you launch the profile for the first time: it reports the exit address, which is the only way to confirm the suffix parsed rather than silently falling back to rotation.
One session id per profile, forever
The number after _s_ is what ties a profile to an address. Give every profile its own and never reuse one, because two profiles on the same id share an address and that link is the cheapest signal a platform can compute:
Login strings for a fleet
profile_01 -> login_c_US_s_1_ttl_1h
profile_02 -> login_c_US_s_2_ttl_1h
profile_03 -> login_c_GB_s_3_ttl_1h
profile_04 -> login_c_DE_s_4_ttl_1h
# a static address instead of residential:
# host is the IP from your dashboard, port 50100, no suffixes- One hour is the longest sticky lifetime we offer, and a residential device can drop earlier. For accounts that must never see an address change, buy an ISP address instead and put it in the same form.
- Match the profile timezone, locale and language to the proxy country. An account on a German address reporting a Warsaw timezone contradicts itself.
- Check the address inside the profile before the first login, not from your own browser. What matters is what the profile sees.
- Keep a note of which session id belongs to which profile. Rebuilding that mapping after a crash is painful and mistakes cost accounts.
What gets accounts linked
Two profiles on one address
Whether through a shared session id or a shared static address, this is the fastest way to lose a cluster: one flagged account takes the rest with it.
Changing country under a live account
An account that always logged in from Poland suddenly appearing on a German address reads as a takeover, and the platform asks for a phone number you may not have.
Rotation under a logged-in session
When a sticky hour expires mid-session the platform sees the session teleport. Long-lived accounts belong on ISP addresses.
Cloning a profile along with its proxy
A cloned profile carries the proxy string with it. Change the session id right after cloning, or the original and the copy sit on one address.
Notes & tips
- •Static addresses go in the same form: the host is the IP from your dashboard, the port is 50100, and there are no suffixes.
- •Match the profile timezone and language to the proxy country, or the address and the browser will contradict each other.
FAQ
Can two VMLogin profiles share one proxy?
They can, and it is the most common way to lose a cluster of accounts. Two profiles on one address are linked regardless of their fingerprints. Give each profile its own session id.
Why does my profile show a different country than I asked for?
The login string did not parse, so you got plain rotation instead of targeting. Check that the country code is upper case and that suffixes follow the order country, city, session, lifetime.
Should I use residential or ISP for account work?
ISP if the account must never see an address change: it is static and dedicated for the term. Residential with a one hour sticky session works for lighter work, but a home device can drop earlier than the hour.
Get your proxy credentials
Sign up, top up your balance, and copy your endpoint into VMLogin. Takes under 5 minutes.
Get started