AdsPower proxy setup: a static IP for every browser profile

AdsPower keeps each browser profile’s cookies, storage and fingerprint separate, and leaves the network to you: every profile needs a proxy you bring. This AdsPower proxy setup guide adds a password-protected proxy to a new profile, saves a batch of proxies to AdsPower’s proxy list for reuse, sets timezone and WebRTC from the IP, and works through the “Connection test failed” and proxy failure errors.

Checked against AdsPower docs in September 2026. The AdsPower help centre’s proxy pages have the current screens if yours differ.

What you need from your dashboard

For each proxy: the IP, the port, the username and the password. One static IP per profile, kept for the profile’s whole life, is the setup that works; the guide to proxies for antidetect browsers covers why, and which of our lines to pick.

How to add a proxy in AdsPower

In the new profile window, open the Proxy section, click Custom, choose the proxy type, enter IP:PORT in Host:Port, and the username and password in their own fields. Click Check Proxy, then OK.

Step by step:

1. Click New profile in the upper left corner.
2. In the Proxy section, click Custom.
3. Set Proxy type to HTTP. AdsPower also offers HTTPS, Socks5 and SSH; use Socks5 only if you want it, with the details your dashboard lists for the order.
4. Enter IP:PORT in Host:Port, then the username in Proxy username and the password in Proxy Password. The one-line IP:PORT:USER:PASS format belongs in the saved proxy list, below.
5. Leave Change IP URL empty. AdsPower’s docs describe it as a link for proxies whose IP changes on request, which a static IP does not need.
6. Click Check Proxy. You want Connection test passed. Connection test failed means AdsPower could not connect; jump to the fixes below.
7. Fill in the rest of the profile if you like (name, group, tag) and click OK. Then find the profile on the Profiles page and click Open.

Save proxies to the AdsPower proxy list

If you manage more than a handful of profiles, keep your proxies in AdsPower’s Proxies section and pick from them, rather than pasting into each profile.

1. Open Proxies and click Add Proxy.
2. Read the Description in the top left corner. It shows the accepted formats.
3. In the box on the right, paste one proxy per line. A remark in curly brackets at the end becomes the proxy’s label:

IP:PORT:USER:PASS{client-a}
IP:PORT:USER:PASS{client-b}

4. Check the parsed list that appears below the box, then click OK. The proxies join the Proxy list.

Now, when you create or edit a profile, click Saved Proxies in its Proxy section and choose one. The Proxy list also has a Check proxy button that tests many at once. In the Outbound IP column, green means the check passed, red means it failed, and grey means it is still waiting.

One button to leave alone: the blue loop next to Saved Proxies, which assigns a proxy at random. That is handy for a one-off check, but a profile you keep should always leave from the same address, so choose its proxy on purpose.

For many profiles at once, click the + beside New profile and choose Quick Create; the proxy can be set there too.

Timezone, location, language and WebRTC in AdsPower

These live in the profile’s Fingerprint section, under Preferences. AdsPower’s defaults already follow the proxy for three of them:

• Timezone: Based on IP by default. The other options are Real, your computer’s timezone, and Custom. Keep Based on IP.
• Location: Based on IP by default, with a choice of Ask each time or Always allow when a site requests it. Custom and Block are the alternatives.
• Language: Based on IP by default, or Custom. The separate Display language only changes the browser’s menus, and websites cannot see it.
• WebRTC: Disabled by default, which stops leaks but also breaks video calls in the profile. Replace reports the proxy’s IP instead, and suits a profile that needs calls. Never use Real with a proxy: it shows your actual IP.

Based on IP only helps if the IP is in the right country. Static ISP proxies come in the country you pick when you buy them, so a profile for a UK client gets a UK timezone and UK English without further fiddling.

How to check the proxy inside the profile

1. Open the profile, and visit https://httpbin.org/ip. The origin must be the IP from your dashboard.
2. Run a WebRTC leak test page in the same profile. Your home IP should not appear anywhere.

If the page shows your own IP rather than the proxy, look first for a VPN or another proxy tool running on your computer; AdsPower’s troubleshooting names those too.

AdsPower proxy not working? What to check

“Connection test failed” or a proxy failure on opening

AdsPower’s troubleshooting runs in three steps, and they are the right ones:

1. Check the details: Host:Port, username and password, exactly as your dashboard shows them, and that the order has not ended.
2. Turn off any VPN or proxy running on your computer, then restart the computer. They get between AdsPower and the proxy.
3. Try the proxy on another network or another device. If it works there, the problem is your connection; if it fails there too, it is the proxy, so tell us.

A one-line test outside AdsPower does the same job as step three:

curl -x http://USER:PASS@IP:PORT https://httpbin.org/ip

The check fails straight away with bad credentials

That is usually a 407: the proxy rejected the username or password. Paste them again without stray spaces. The 407 error guide lists the other causes.

The check hangs, then fails

A timeout means nothing answered at that IP and port. Check both, and check the proxy type: Socks5 selected against an HTTP port, or the reverse, fails the same way. The connection timeout page has more.

The profile shows the wrong country

Geolocation databases disagree about some IPs, and the checker AdsPower uses may not agree with the site you work on. Go by the site you actually use. If every checker shows the wrong country, send us the IP.

What these profiles are for

Separate profiles on separate addresses suit client account management you are authorised to do, ad verification and testing across locales. We do not support fake-account farms or getting round a platform’s ban, and each platform’s own terms still apply. The antidetect browser guide and our acceptable use policy spell it out. Want a second pair of eyes on a setup? Ask in Discord.