Back to Blog

10 Mistakes When Setting Up Proxies in Dolphin Anty and AdsPower: How to Fix Each in 5 Minutes

Proxies not working, accounts getting banned, connections dropping — all these are consequences of common setup mistakes. We analyze the 10 most frequent issues and explain how to fix each one in 5 minutes.

📅April 28, 2026
```html

You bought a proxy, entered the data into an anti-detect browser — and nothing works. Or it works, but accounts still get banned. Or the site throws a captcha on every request. Sound familiar? Almost always the reason is not the proxy itself, but one of the ten typical setup mistakes made by beginners. In this article, we will analyze each of them and provide specific solutions.

Mistake #1: Wrong type of proxy for the task

The most common mistake is buying the first proxies you find and trying to use them for any task. Proxies come in different types, and each is suitable for specific scenarios. If you use the wrong type, you will either get banned, experience low speeds, or simply waste your money.

Here is the basic logic for choosing:

Proxy Type Suitable for Not suitable for
Residential Facebook Ads, Instagram, TikTok, account registration Mass scraping (expensive)
Mobile Account warming, TikTok Ads, high-trust tasks Large volume scraping
Datacenter Scraping Wildberries, Ozon, Avito, SEO monitoring Social networks, advertising accounts

How to fix: Clearly define the task before purchasing. For working with Facebook Ads and Instagram, you need residential proxies — they have IPs of real home users and raise minimal suspicion with the platform's algorithms. For scraping marketplaces, datacenter proxies are sufficient — they are faster and cheaper.

Mistake #2: Confused HTTP and SOCKS5 protocols

When entering proxies in Dolphin Anty, AdsPower, GoLogin, or any other anti-detect browser, you need to specify the protocol. Beginners often choose HTTP where SOCKS5 is needed, and vice versa. The result is that the proxy "doesn't work," when in fact the wrong protocol has simply been selected.

What's the difference:

  • HTTP/HTTPS — works only with web traffic. Suitable for browser tasks but does not transmit other types of traffic.
  • SOCKS5 — a universal protocol. Transmits any traffic, supports UDP, works faster with proper configuration. Recommended for most tasks in anti-detect browsers.

How to fix: Open the profile settings in your anti-detect browser → find the "Proxy Type" or "Protocol" field → select SOCKS5. If the provider gave you the data without specifying the protocol — contact support and clarify. In most cases, SOCKS5 is the preferred option for working with social networks and advertising accounts.

Mistake #3: One proxy for multiple accounts simultaneously

This is a classic mistake that can get multiple accounts banned at once. The principle is simple: one proxy = one account. If two profiles in Dolphin Anty use the same IP address, Facebook or Instagram sees this as an attempt to manage multiple accounts from one device and blocks both.

This is how so-called "chain bans" happen — when one account is blocked, all others associated with the same IP are automatically banned. For arbitrageurs, this is particularly painful: you can lose several warmed-up advertising accounts at once.

How to fix: A strict rule — each profile in the anti-detect browser is assigned a unique proxy. No exceptions. If you manage 30 Instagram accounts, you need 30 different IP addresses. Check all profiles in AdsPower or Multilogin: open the profile list → sort by proxy → find duplicates → replace them with unique addresses.

⚠️ Important for arbitrageurs

If you have already received a ban on an account that used a specific proxy — do not use that IP for a new account. Facebook remembers the IP history and will immediately flag the new profile as suspicious.

Mistake #4: Proxy geolocation does not match the account

Imagine: you registered a Facebook account from Russia, and now you are accessing it through a proxy with an American IP. To Facebook's security system, this looks like a hack — and the account is immediately blocked or requests verification.

The proxy geolocation must match the country specified in the account and the login history. This is especially critical for:

  • Facebook Ads and Google Ads accounts
  • Instagram accounts with activity history
  • TikTok accounts with a linked phone number
  • Marketplace accounts (Wildberries, Ozon) with order history

How to fix: When purchasing proxies, always choose a country that corresponds to your account. In the profile settings of Dolphin Anty or GoLogin, ensure that the browser language, time zone, and GPS geolocation match the proxy's country. For example, if the proxy is American — set the time zone to America/New_York and the language to en-US.

Mistake #5: Incorrect format when entering proxy data

It seems simple to just copy and paste the proxy data — what could go wrong? In practice, this is one of the most common reasons why a proxy "doesn't work." An incorrect input format means the connection won't establish at all.

The standard format for proxy data looks like this:

IP:PORT:LOGIN:PASSWORD
or
IP:PORT
(if the proxy does not require authentication)

Example:
192.168.1.100:8080:mylogin:mypassword

Common mistakes when entering:

  • Extra spaces at the beginning or end of the string (especially when copying)
  • Confused order of fields: entered LOGIN:PASSWORD:IP:PORT instead of IP:PORT:LOGIN:PASSWORD
  • Copied data with line breaks — the browser interprets this as two different proxies
  • Incorrect port specified (for example, 8080 instead of 1080 for SOCKS5)

How to fix: In Dolphin Anty, open profile settings → "Proxy" section → manually enter the data into separate fields (host, port, login, password), rather than one line. This eliminates formatting errors. In AdsPower, similarly: use the form with separate fields, not the import string, if you are unsure of the format.

Mistake #6: Proxy not checked for functionality before use

Many beginners insert proxies into the anti-detect browser and immediately start working with accounts — without checking if the proxy works at all, whether the IP is exposed, or if it has been blacklisted. This is a direct path to bans.

Before using any proxy for working with advertising accounts or social media accounts, you need to check three things:

  1. Functionality — does the proxy respond and pass traffic
  2. IP reputation — is the address on spam lists and blacklists
  3. Geolocation compliance — is the IP really from the country you ordered

How to check in 2 minutes:

  • Built-in check in Dolphin Anty: when adding a proxy, click the "Check" button — the browser will show the IP, country, and ping
  • Service ip-score.com or scamalytics.com — shows IP reputation and risk score
  • Service whoer.net — checks for DNS leaks, geolocation, and anonymity
  • GoLogin and AdsPower also have built-in proxy checks directly in the interface

If the risk score of the IP is above 50 out of 100 — it's better to replace the proxy. Using a "dirty" IP for advertising accounts is almost a guaranteed ban.

Mistake #7: Mixing proxies and real IP in one session

This mistake is particularly insidious because beginners often don't even realize they are making it. The scenario looks like this: you open an account through Dolphin Anty with a proxy, then accidentally open the same Facebook in a regular Chrome browser — already with your real home IP. The platform sees two different IPs for one account in a short time and triggers the protection system.

Another option: you are working through a proxy, but at the same time, a regular browser is open on the same computer, logged into the same account. Cookies and session data may overlap, which also raises suspicions.

How to fix: Establish a strict rule — accounts that work through an anti-detect browser with a proxy are NEVER opened in a regular browser. If you need to urgently check an account — do it only through the same profile in Dolphin Anty or AdsPower, with the same proxy. Also, disable account auto-sync in Chrome or Firefox, so the browser doesn't "pull" data automatically.

💡 Tip for SMM specialists

If you manage client accounts through Multilogin or Octo Browser — create a separate profile for each client and never log into their accounts through your personal browser, even "for a second." This is one of the most common reasons for losing client Instagram accounts.

Mistake #8: Ignoring DNS leaks

Many think: "I connected a proxy — so my real IP is hidden." This is not always the case. Even with an active proxy, DNS requests (requests to domain name servers) may go through your real internet provider. This is called a DNS leak — and it can reveal your real geolocation, even if the IP address is hidden.

For most tasks in anti-detect browsers, DNS leaks are not a critical problem, but for arbitrageurs working with Facebook Ads in gray niches, or for those using proxies to bypass geo-restrictions — this is important.

How to check and fix:

  1. Go to dnsleaktest.com through the anti-detect browser profile with the proxy enabled
  2. Click "Extended test" — the service will show which DNS servers are being used
  3. If you see your provider's servers in the results (instead of the proxy's country servers) — there is a leak
  4. To fix: in the profile settings of Dolphin Anty or GoLogin, find the DNS parameter and specify public DNS servers corresponding to the proxy's country (for example, for the USA: 8.8.8.8 or Cloudflare 1.1.1.1)

In Multilogin and Incogniton, there are built-in DNS settings — be sure to check them when creating a new profile.

Mistake #9: Using cheap shared proxies for advertising accounts

The desire to save money is understandable, but in the case of proxies for advertising accounts, saving turns into direct losses. Cheap shared proxies (shared proxies used simultaneously by dozens or hundreds of other users) are one of the main sources of bans for arbitrageurs and SMM specialists.

The problem is that you don't know what was done with this IP before you. If the previous user violated Facebook's rules or sent spam — the IP is already blacklisted. You connect to it, register an account, and get an instant ban — not because of your actions, but because of the "reputation" of the IP.

Parameter Shared Private
Number of users on IP 10–100+ Only you
IP reputation Unpredictable Clean
Speed Unstable Stable
Ban risk High Low
Suitable for Facebook Ads ❌ No ✅ Yes

How to fix: For working with Facebook Ads, TikTok Ads, and Instagram accounts, use only private residential or mobile proxies. Mobile proxies work particularly well for warming up accounts — their IP addresses belong to real mobile operators, and platforms trust them the most.

Mistake #10: Lack of IP rotation when scraping

If you are scraping prices on Wildberries, Ozon, or Avito — or collecting data from any other site — and using one static IP, you will be blocked very quickly. Marketplace protection algorithms can identify scrapers by request patterns: too many requests from one IP in a short time = automatic blocking.

IP rotation is the automatic change of the address at set intervals or after a certain number of requests. Without rotation, even the "cleanest" proxy will be blocked within minutes of intensive scraping.

How to set up rotation:

  • Residential proxies with rotation — most providers offer a special endpoint (one address), which gives a new IP from the pool with each new connection. This is the most convenient option for scraping.
  • Pool of static proxies — use a list of 20–50 proxies and set up rotation in your scraper: each request is sent through a random IP from the list.
  • Delays between requests — even with IP rotation, add random pauses between requests (1–5 seconds). This simulates the behavior of a live user.

For scraping marketplaces in large volumes, datacenter proxies with rotation are well-suited — they provide high speed and sufficient anonymity for collecting data on prices and products.

Conclusion: checklist before launching proxies

Most proxy problems are not technical failures, but banal setup mistakes that can be fixed in 5 minutes if you know where to look. Remember the main rules: the right type of proxy for the task, one IP per account, matching geolocation, checking before use, and no mixing with real IP.

✅ Checklist before launch

  • The correct type of proxy is selected for the task (residential / mobile / datacenter)
  • The protocol is specified correctly (SOCKS5 for anti-detect browsers)
  • Each account is assigned a unique proxy
  • The geolocation of the proxy matches the country of the account
  • The data is entered in the correct format, without extra spaces
  • The proxy is checked through the built-in test or ip-score.com
  • The account is not opened in a regular browser simultaneously
  • DNS leaks are checked through dnsleaktest.com
  • Private, not shared proxies are used for advertising accounts
  • For scraping, IP rotation is set up with delays between requests

If you are just starting to work with multi-accounting in Facebook Ads or Instagram and want to avoid bans from the very start — we recommend using residential proxies: they provide real IPs of home users, minimal risk of blocking, and are compatible with all popular anti-detect browsers — Dolphin Anty, AdsPower, GoLogin, and Multilogin.

```