Keep Each Afina Profile on Its Own IPOasis IP

To keep Afina profiles from sharing one IP address, assign a separate IPOasis IP to each profile used for account login. Use a rotating proxy pool for research tasks. Afina isolates cookies, local storage and browser fingerprint. The proxy provides the public IP address that websites see.

These two layers do different jobs. Two isolated browser profiles can still look related if they use one office IP, home router or reused proxy server. At the same time, a proxy will not fix mixed cookies if two accounts run in the same browser environment. If the jobs must stay independent, separate both layers: create a separate browser profile with its own browser fingerprint and proxy settings, then assign it the right IPOasis IP address.

This setup does not guarantee that a platform will keep an account active. It only prevents two Afina profiles from using the same exit IP. Behavior, account history, payment data, recovery data and platform rules still matter.

Why an Afina profile needs a proxy

An Afina profile isolates the browser side of the session. It stores cookies, local storage, extensions and browser fingerprint settings separately from other workflows, so different accounts do not use one Chrome session. The proxy handles the network layer. It defines the public IP address, country and ASN that the site sees.

This difference is easy to miss. Teams often split store logins across antidetect profiles but route them through one network. The site may not see shared cookies, but it still sees one exit IP. If the work needs separation, browser profile settings and proxy settings must match.

Match the country, language and timezone to the proxy exit IP. A US residential IP with a Tokyo timezone creates a mismatch. A German research profile with a US static IP also creates conflicting signals. Check the network settings first, then launch the profile.

What one IP per Afina profile means

One IP per Afina profile means each login profile uses a dedicated address that is not assigned to another login profile. This is a convenient pattern for long sessions, repeated access from one place and workflows where cookies should be used from the same network.

Before cloning a working profile, create a matching table. Record the assigned proxy in the profile table to avoid reusing the same IP address by accident.

Keep the naming pattern. Assign a separate dedicated IP address to each new login profile. If two profiles use one exit IP, websites may see a shared network signal.

It also helps to decide what happens to an address when work pauses or ends. Do not return an IP to the general pool immediately after it was used for an account with a long session history. Mark it as reserved, paused or retired, so another teammate does not attach it to a new profile by habit. This matters most for static residential IPs. The address may still be technically available, but for one account it already has login history, geography and behavioral context. If the IP has to be replaced, close the session first, update the proxy in the profile, check the country and only then launch the account again.

Which proxy type to attach

The proxy type should match the task. Long login sessions usually need a stable IP address. Data collection, geo checks and speed tests can use rotation or datacenter proxies. The same principle applies when choosing proxies for scraping, research and account workflows.

For a login profile, order one dedicated static residential IP and keep it only on that profile. For independent page checks, use a rotating residential proxy pool and change IP between tasks, not during an active check. If the team does not have credentials yet, create an IPOasis account before copying host and port into Afina.

Do not use a rotating pool for a long login session. Do not choose datacenter proxies for tasks that need a residential network. Define the task first, then fill in the Proxies tab.

Rotating residential traffic from IPOasis does not expire. This is useful for research profiles that sit idle between tasks. Still, a rotating pool does not become a stable login IP because of that.

How account work differs from data collection

Account work means a long session where cookies are used from one address. Data collection consists of independent requests where the IP can change between tasks. If one Afina profile is used for account login and data collection through rotating proxies, the IP change can break session stability.

Use a stricter setup for account work:

• one Afina profile, one dedicated static IP
• IP country matches the profile language and timezone
• no proxy replacement inside a stable session
• do not assign one exit IP to two login profiles that must work independently

Data collection and geo checks allow more flexible settings because they do not need the same session continuity. The main rule is to change IP between tasks, not while one page check is open.

• rotating residential or datacenter proxies are usually enough
• each market check can use a new exit IP
• session pinning helps keep the same IP until the task ends

A US store login and a Germany price check need different settings. Use two Afina profiles and two exit IP addresses for them. A workflow with a browser profile and real device follows the same principle: the identity layer and the network layer should stay separate.

How to copy host and port from the dashboard

Host and port define the server address and connection port for the Afina profile. Copy them from IPOasis together with the username, password and protocol. Select the country in the dashboard first, so Check Proxy does not show another region after you enter the settings.

1. log in and open the selected product. Use static proxies for account logins, rotating residential or datacenter proxies for data collection
2. copy protocol, host, port, username and password
3. if the task needs a country, set that country first, then copy the line

A US profile with a UK proxy creates a mismatch that is sometimes noticed only after testing. It is better to check the country in the dashboard beforehand.

When copying credentials, do not mix fields from different rows. In proxy dashboards, the host can be the same for several locations, while country, session or rotation behavior is controlled through the username. If you copy the host from one row and the username from another, Afina may connect, but Check Proxy can show the wrong country or session type. Check the protocol as well. HTTP(S) and SOCKS5 credentials can look almost identical, but the profile must use the same protocol that the dashboard issued. Errors such as auth failed, timeout or an empty Check Proxy response usually start with username, password, port and protocol, not with rebuilding the whole browser profile.

Leave the optional IP Change URL field in Afina empty unless the IPOasis product documentation provides a rotation URL. Static residential proxies do not need it. In rotating plans, rotation parameters are usually set through the username or session settings, not through a separate URL.

How to add a proxy in Afina Browser

In Afina, open Edit Account, go to the Proxies tab, choose Set Proxy and enter the host, port, username and password for HTTP or SOCKS5. Before launch, click Check Proxy.

After checking the connection, save the profile settings. In the matching table, record which IPOasis IP address is assigned to each Afina profile.

Read the Check Proxy result as a final consistency check, not only as proof that the internet works. If the IP appears but the country, provider or address type does not match the profile task, do not launch the account. Go back to the IPOasis settings, check the selected location and make sure Afina does not still contain old credentials from a previous proxy. For team workflows, it is useful to store the last check time, the Check Proxy result and a short note about the account that should use this address. That makes it easier to see whether a problem comes from the proxy or from profile settings.

If the profile has already been used, do not replace the proxy in the middle of an active session. Close the profile, let open tasks finish and only then update network settings. For long logins, this reduces abrupt signals: the website does not see old cookies, a new exit IP and an unfinished page action at the same time. For test or research profiles the rule can be softer, but it is still cleaner to check a new proxy set before opening the working tab, not after the page is already loaded.

Start using Afina with IPOasis

See the current IPOasis plans before attaching a host to a profile. This material is provided for informational and educational purposes only.

Download