How to Set Up Proxies in AdsPower and Multilogin (2026)

AdsPower and Multilogin are the two anti-detect browsers we get asked about most after GoLogin and Dolphin Anty. The fingerprint side is handled by the browser — canvas, WebGL, fonts, audio context — but the IP is still the first thing every platform checks. A perfect fingerprint on a flagged or shared IP gets accounts linked and banned anyway.

This guide walks through proxy configuration in both browsers step by step: single profiles, bulk import for farms, verification, and the failure modes that actually cause bans. If you use GoLogin or Dolphin Anty instead, see the GoLogin & Dolphin Anty setup guide.

Before You Start: What You Need

From your proxy provider's dashboard you need four values. With JIBAO Proxy they look like this:

• Host: us.jibaoproxy.com (region-specific gateway)
• Port: 913 (supports both HTTP and SOCKS5)
• Username: your account username, with optional country and session parameters
• Password: your proxy password

As a single connection string: socks5h://USERNAME:[email protected]:913

One decision before configuring anything: static or dynamic. For accounts you plan to keep for months (social media, marketplace seller accounts, ad accounts), use one static residential IP per profile — platforms treat a stable IP as a trust signal. For accounts you create in batches and discard, dynamic residential with sticky sessions is cheaper and gives you a fresh IP per batch.

AdsPower Proxy Setup

Step 1: Create or Edit a Profile

1. Open AdsPower and click New Profile.
2. Pick the platform preset if you're targeting a specific site (Facebook, Amazon, TikTok) — AdsPower tunes some defaults per platform.
3. Under Fingerprint settings, leave the defaults unless you have a reason not to. Randomized-per-profile is what you want.

Step 2: Configure the Proxy

1. Scroll to the Proxy section in the profile editor.
2. Set Proxy type to SOCKS5 or HTTP.
3. Fill in:
   • Proxy host: us.jibaoproxy.com
   • Proxy port: 913
   • Proxy username: USERNAME-session-profile001 — the session suffix pins this profile to one IP for the session lifetime. Use a different session ID per profile, always.
   • Proxy password: your password
4. Click Check proxy. AdsPower shows the exit IP, country, and latency.

AdsPower also accepts a one-line paste in type://user:pass@host:port format — paste socks5://USERNAME:[email protected]:913 into the host field and it auto-fills the rest.

Step 3: Match Timezone and Language to the IP

In Fingerprint settings, set Timezone to Based on IP and Language to Based on IP. This is the single most common mistake in AdsPower setups: a US proxy with the machine's real Asia/Shanghai timezone is an instant inconsistency flag. AdsPower can derive both from the proxy automatically — turn it on and forget it.

Step 4: Bulk Import (for Farms)

Running 50+ profiles? Don't configure proxies one at a time:

1. Go to Profiles → Import and download the XLSX template.
2. Fill the proxy columns in host:port:username:password format, one row per profile, each with a unique session suffix in the username (USERNAME-session-p001, USERNAME-session-p002, …).
3. Import. AdsPower creates one profile per row with the proxy attached.

Multilogin Proxy Setup

Multilogin (now Multilogin X) handles proxies per browser profile, with a connection check built into the profile creation flow.

Step 1: Create a Profile

1. Click New profile, choose Mimic (Chromium) or Stealthfox (Firefox). Mimic is the safer default — most real users run Chrome.
2. Name the profile after the account it will hold, not "test1" — you will have 80 of these in three months.

Step 2: Configure the Proxy

1. In the profile editor, open the Proxy tab.
2. Select SOCKS5 (or HTTP) as the connection type.
3. Enter:
   • Address: us.jibaoproxy.com
   • Port: 913
   • Username: USERNAME-session-ml001
   • Password: your password
4. Click Check proxy. Multilogin verifies connectivity and shows the external IP and country.

Step 3: Let Multilogin Sync Fingerprint to IP

Multilogin reads the proxy's geolocation and offers to set timezone, geolocation API, and WebRTC public IP to match. Accept all three. Its WebRTC masking replaces the real IP with the proxy IP rather than disabling WebRTC — this looks more natural than a disabled WebRTC, which is itself a (weak) bot signal.

Step 4: Validate Before Real Use

Launch the profile and run through this checklist once per new profile:

1. IP check — the shown IP must be the proxy exit, not your real IP.
2. Timezone consistency — browser timezone matches IP country.
3. WebRTC — no local or real public IP leaking.
4. DNS — resolvers should belong to the proxy path, not your local ISP. (With SOCKS5, use socks5h semantics so DNS resolves through the proxy.)

AdsPower vs Multilogin: Proxy Handling Compared

Feature	AdsPower	Multilogin
Proxy per profile	Yes	Yes
One-line paste parsing	Yes (type://user:pass@host:port)	No (separate fields)
Bulk import with proxies	XLSX template	API / CSV (X plans)
Timezone from IP	Yes, opt-in	Yes, suggested on check
WebRTC handling	Replace / disable	Replace with proxy IP (recommended)
Built-in proxy check	Yes	Yes

Which Proxy Type per Use Case

Use case	Proxy type	Why
Long-term social accounts	Static residential	Same IP every login; IP changes on seller/ad accounts trigger review
Account creation batches	Dynamic residential, sticky 10–30 min	Fresh IP per batch, stable through the signup flow
Warming up profiles	Static residential	Consistency is the entire point of warming
Research / scraping profiles	Dynamic residential, rotating	No session state needed, maximize IP diversity

Pricing reference: static residential runs $5.88/month per IP with unlimited bandwidth; dynamic residential is billed per GB ($6.8/GB, less with deposit bonuses). Details on the pricing page.

Troubleshooting

"Proxy check failed" in either browser

• Protocol/port mismatch is the #1 cause — confirm the proxy type dropdown matches what your endpoint expects.
• Copy credentials from the dashboard; a trailing space in the password field fails silently.
• Try the same credentials with curl -x from a terminal. If curl works, the issue is in the browser fields, not the proxy.

Profile works, but accounts still get linked

• Two profiles sharing one IP — check that every profile has a unique session suffix or dedicated static IP.
• Timezone/language not derived from IP — the fingerprint says Germany, the IP says Texas.
• You logged into the same account from your real browser once. That link never goes away.

IP changes mid-session on dynamic proxies

• Sticky sessions have a TTL. If your workflow runs longer, re-use the same session ID — you'll keep the IP if it's still healthy — or switch that profile to a static IP.

Summary

Both browsers make proxy setup straightforward: paste host, port, username (with a unique session suffix per profile), password, hit check, and let the browser align timezone and WebRTC with the IP. The rules that actually keep accounts alive are boring and absolute: one IP per profile, residential only for social platforms, timezone always derived from the IP, and verify leaks before first login.