GoLogin Proxy Setup
Assign a dedicated SotaProxy IP to each GoLogin profile.
GoLogin is an anti-detect browser for managing multiple accounts with separate fingerprints. Each profile should have its own dedicated proxy to prevent accounts from being linked by IP. SotaProxy works with GoLogin's built-in proxy configuration.
Setup guide
Open profile proxy settings
In GoLogin, open or create a profile. Navigate to the Proxy tab in the profile settings.
Set proxy type and credentials
Select "HTTP" or "SOCKS5" as the proxy type. Enter: Host: proxy.sotaproxy.com, Port: 10000, Username: YOUR_USERNAME, Password: YOUR_PASSWORD.
Use sticky sessions for account management
Username format: YOUR_USERNAME_s_1001_ttl_1h
Password: YOUR_PASSWORDAppend _s_{unique_id}_ttl_1h to your username. Each profile should have a unique session ID so they never share the same IP, even accidentally.
Geo-targeting for account location
Username format: YOUR_USERNAME_c_US_s_1001_ttl_1hMatch the proxy location to the account's intended location. A US Instagram account should use a US proxy. Append _c_US to the username.
Automate it with the SotaProxy API
Everything above works without opening the dashboard. With an API key, GoLogin 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
GoLogin asks for five fields and nothing else. Residential targeting rides inside the login, so you never need a separate endpoint per country:
GoLogin stores the proxy inside the profile, so the address travels with it when you open the profile from another machine or share it with a team member.
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
# static address instead of residential:
# host = 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.
Cloud profiles carry the proxy with them
A teammate opening the profile in another country still exits through your address, which is the point, but it also means one leaked profile exposes the account and the address together.
Notes & tips
- •Assign one proxy per profile. Never share a proxy between two profiles.
- •Use residential or mobile proxies for social media accounts. Datacenter IPs trigger platform security on most social networks.
- •Test the proxy in GoLogin's "Test proxy" button before saving the profile.
FAQ
Which SotaProxy type should I use with GoLogin?
Mobile proxies (4G/LTE) for Instagram and TikTok. Residential proxies for most other platforms. ISP proxies for fast, consistent sessions on platforms that check ASN type.
Can I import a proxy list into GoLogin?
Yes. GoLogin supports bulk proxy import via CSV. Format each line as: host:port:username:password.
Get your proxy credentials
Sign up, top up your balance, and copy your endpoint into GoLogin. Takes under 5 minutes.
Get started