Afina Antidetect Browser Proxy Setup
Pair SotaProxy residential or ISP proxies with Afina for maximum account trust and session isolation.
Afina (afina.io) is an antidetect browser built for multi-account management. It creates isolated browser profiles with unique fingerprints - canvas, WebGL, fonts, timezone, and more - so each profile appears as a distinct device to target platforms. To complete the isolation, each profile needs its own unique IP address. SotaProxy residential and ISP proxies are the recommended proxy type for Afina users: these IP ranges have genuine ISP assignments and high trust scores on social media platforms, ad networks, and e-commerce sites.
Setup guide
Open Afina and navigate to Profile settings
Launch Afina. On the Profiles tab, click "New Profile" to create a profile, or click the edit icon on an existing one. This opens the profile configuration panel.
Go to the Proxy section
Inside the profile editor, locate the "Proxy" section (usually in the left sidebar or as a tab). Select the proxy type - choose HTTP or SOCKS5 depending on your preference. SotaProxy supports both.
Enter SotaProxy credentials
Host: proxy.sotaproxy.com:10000
Port: 10000
Username: YOUR_USERNAME_s_1001_ttl_1h
Password: YOUR_PASSWORDEnter your SotaProxy host, port, username, and password. Append a unique session ID to the username (e.g. _s_1001_ttl_1h) to pin this profile to a stable IP. Use a different session ID for each profile.
Proxy format reference
YOUR_USERNAME:YOUR_PASSWORD@proxy.sotaproxy.com:10000
# With sticky session (same IP per profile):
YOUR_USERNAME_s_1001_ttl_1h:YOUR_PASSWORD@proxy.sotaproxy.com:10000
# With geo-targeting (US residential):
YOUR_USERNAME_c_US_s_1001_ttl_1h:YOUR_PASSWORD@proxy.sotaproxy.com:10000The proxy URL format above works anywhere Afina asks for proxy connection string. Combine session IDs and country codes as needed.
Test the proxy and save
Click the "Check proxy" or "Test" button in Afina's proxy section. Afina will display the resolved IP address and country. Verify the location matches your intent, then save the profile.
Recommended proxy type for Afina
For social media accounts (Instagram, Facebook, TikTok, Twitter/X): use Residential or Mobile (4G) proxies. For ad verification, e-commerce, and platforms that check ASN type but allow static IPs: use ISP proxies. Avoid datacenter proxies for any account that requires high trust score.
Full example
Complete proxy string formats for common Afina use cases
# Standard rotating residential (new IP each session):
YOUR_USERNAME:YOUR_PASSWORD@proxy.sotaproxy.com:10000
# Sticky residential - same IP for entire profile session:
YOUR_USERNAME_s_1001_ttl_1h:YOUR_PASSWORD@proxy.sotaproxy.com:10000
# US residential sticky (Instagram account registered in US):
YOUR_USERNAME_c_US_s_1001_ttl_1h:YOUR_PASSWORD@proxy.sotaproxy.com:10000
# UK ISP proxy for e-commerce (high trust, static ASN):
YOUR_USERNAME_c_GB_s_1002_ttl_1h:YOUR_PASSWORD@proxy.sotaproxy.com:10000
# SOCKS5 format (if Afina profile uses SOCKS5 type):
socks5://YOUR_USERNAME_s_1001_ttl_1h:YOUR_PASSWORD@proxy.sotaproxy.com:10000Automate it with the SotaProxy API
Everything above works without opening the dashboard. With an API key, Afina 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
Afina asks for five fields and nothing else. Residential targeting rides inside the login, so you never need a separate endpoint per country:
Afina imports proxies from Excel, which is the fastest way to set up a fleet: generate one row per profile with its own session id and import the file.
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.
Importing the same login for every row
A spreadsheet copied down the column repeats the session id. Number them before importing, and use Afina's proxy checker afterwards to confirm each profile sees a different address.
Notes & tips
- •Always assign one unique proxy session per Afina profile. Sharing the same session ID between two profiles will route them through the same IP, breaking isolation.
- •Residential and ISP proxies have the highest trust scores on social media platforms. Datacenter IPs are frequently flagged on Instagram, Facebook, and TikTok.
- •Match the proxy geo to the account's registered country. A UK Instagram account should use a UK proxy (_c_GB).
- •If a platform forces re-verification after login, try switching to a Mobile (4G) proxy - mobile IPs have the highest platform trust.
- •Afina's "Test proxy" button resolves the IP before you save. Always verify the correct location is shown.
FAQ
Which SotaProxy type gives the best results in Afina?
Residential proxies for most use cases. Mobile (4G/LTE) proxies for the highest trust score on Instagram, TikTok, and Facebook. ISP proxies when you need a fast, stable IP with a legitimate ISP assignment.
How do I keep the same IP across an entire Afina session?
Append _s_{id}_ttl_15m to your SotaProxy username. For example: YOUR_USERNAME_s_1001_ttl_1h. All requests from that profile use the same IP until the sticky window expires or you change the session ID.
Can I import a list of proxies into Afina in bulk?
Yes. Afina supports bulk proxy import. Format each line as host:port:username:password and import via the proxy manager.
Why did my Afina profile get flagged even with a proxy?
Platform flags are usually fingerprint or behavior-related, not just IP-related. Ensure Afina's browser fingerprint settings are correctly configured for each profile. Also verify your proxy geo matches the account's expected location.
Get your proxy credentials
Sign up, top up your balance, and copy your endpoint into Afina. Takes under 5 minutes.
Get started