AdsPower Proxy Setup with Node4: HTTP, SOCKS5 and Bulk Import

Fill AdsPower's proxy form with a Node4 host, port and login, pass Check Proxy, then load many profiles at once from the Mass import txt template.

Before you open AdsPower you need an active Node4 plan and its endpoint: the host and port of each static proxy are listed on the Proxies page, and the account credential (one username and password for every product you hold) is on Proxies and under Auth & IP Access. If you have not chosen a product yet, choosing the right proxy type matches the common jobs to one, and which Node4 proxy for which job covers store logins, ads, social and scraping specifically.

Add a proxy to a new profile

1. Click New Profile and open the Proxy section of the form.
2. Choose Custom so you can type your own proxy rather than pick from Saved Proxies.
3. In Proxy type, pick HTTP to use a Node4 HTTP port, or Socks 5 to use a SOCKS5 port. Leave HTTPS alone: Node4's HTTP ports take a plain proxy connection and carry HTTPS sites inside it.
4. Fill Host:Port with the host and port from the table below, separated by a colon.
5. Enter your Node4 username in Proxy username and the password in Proxy Password.
6. Click Check Proxy, wait for the result described in the next section, then click OK to create the profile.

A shortcut from AdsPower's own help: paste a whole HOST:PORT:USERNAME:PASSWORD line into Host:Port and it splits the line into the other fields for you.

The free tier is static shared datacenter over HTTP only: choosing Socks 5, or pointing the profile at one of the gateway hosts, needs a paid plan, and a free credential is refused there.

Check the proxy before saving

Check Proxy makes AdsPower open a connection through the details you typed. Connection test passed means the host, port, type and credential were all accepted; Connection test failed means AdsPower could not get through, and the last section of this page takes it from there.

A pass proves the proxy answers, not that the profile will use it the way you expect. Open the profile, load https://api.ipify.org, and compare the address with the one listed for that proxy on Proxies. On a gateway there is no fixed address to compare, so check the country instead with https://ipinfo.io/json. If the page shows your home address, AdsPower's proxy failure page points at a VPN or system proxy running on the same computer; turn it off and reopen the profile.

Proxies you store in AdsPower's Proxies section can be checked together: select them and click Check proxy, and the Outbound IP column turns green for a pass and red for a failure.

One proxy per profile

Give each account its own profile and each profile its own address: one IP per account is what keeps two stores or two ad accounts from appearing to share a connection. The browser profile separates cookies and fingerprints; the proxy only separates the address.

How long a profile keeps its address depends on the product. A Dedicated proxy is one fixed address that no other customer uses, so the profile reopened next week leaves from the same IP while the plan is paid. The gateways choose an exit per connection. Adding a session id to the username pins one exit for up to 30 minutes on the rotating gateways, and residential sessions are best effort with a ceiling of 30 minutes, so a gateway profile opened tomorrow leaves from a different address in the same targeted country. Sticky and rotating sessions explains the session id in full.

Use IP whitelisting instead of a password

Register the public address of the computer running AdsPower under Auth & IP Access, then leave Proxy username and Proxy Password empty in the profile. The whitelist works on every product, with different results: a static proxy behaves exactly as it does with a password, a rotating gateway gives an untargeted exit unless you still type the username and leave only the password empty, and a whitelisted residential connection sends no username at all, so it is untargeted and can exit anywhere in the pool.

The address to register is the one your computer reaches the internet from, not the address the profile shows after the proxy. If your home connection changes address, every whitelisted profile fails at once until you update the entry. IP whitelisting best practices covers changing connections and the per-plan limit.

Import many profiles at once

AdsPower's bulk path is the "+" icon beside New Profile, then Mass import, which takes an Excel or txt template. In the txt template each profile is a block of key=value lines, profiles are separated by a line of asterisks, proxytype takes http or socks5, and proxy takes Host:Port:Username:Password:

name=store-01
proxytype=http
proxy=HOST:PORT:USERNAME:PASSWORD
************************************
name=store-02
proxytype=socks5
proxy=gw-residential.node4.io:1082:USERNAME-country-us-session-store02:PASSWORD

Node4 reads location from the username, so put the country there rather than in the template's countrycode, regioncode or citycode keys. Quick Create is the other mode: it makes a number of blank profiles with one proxy setting, which suits a test batch but not one address per profile.

Where the lines come from:

• Dedicated or Shared: select the proxies on Proxies and use Export as TXT with Port and Username & Password ticked (the export leaves credentials out unless you tick it) and Protocol Prefix left off. Each line comes out as host:port:user:pass with the HTTP port, which is exactly the proxy value for a proxytype=http block; for a proxytype=socks5 block, replace the port with the SOCKS5 port shown on that proxy's row.
• Rotating gateways: on the gateway's Connect panel, open Generate proxy list, leave Type on sticky (the default), choose the line format and generate; each line carries its own session id, so each profile gets its own pinned exit. For a single profile, the Sticky session switch on the same panel gives one pinned line.
• Residential: write one line per profile with a different -session- value in each username, as in the second block above.

The colon is the field separator in this format, so a password containing :, @ or # splits in the wrong place and the profile fails with a 407. The 407 guide's special-character section shows how to recognize it; the fix is a credential without those characters, created under Auth & IP Access.

You can also store the lines in AdsPower's Proxies section with Add Proxy (one per line, socks5:// in front for SOCKS5) and point the template's proxyid key at them.

When the check fails

A 407 when the profile opens

The credential reached Node4 and was refused. Check that the host belongs to a product your account holds (a residential host with only a datacenter plan is refused), that the password survived the paste, that every targeting key in the username is spelled right (a misspelled key such as -contry-us is refused with a 407, not ignored), and, if you whitelisted, that your computer's current address is the registered one. Fixing a 407 walks through each cause.

A timeout, or a failed test with no 407

The type and the port disagree far more often than the proxy is down: Socks 5 selected with an HTTP port, or HTTP with a SOCKS5 port, waits and then fails. A free account on Socks 5 fails the same way, because SOCKS5 has no 407 to report. If type and port match, a firewall or antivirus on the computer may be blocking the outbound port; connection issues goes layer by layer.

The wrong country

The exit follows the username's segments; a misspelled key is a 407, covered above, so a profile that opens in the wrong country usually has no country segment at all, or a whitelisted connection with no username. Check the exit with https://ipinfo.io/json inside the profile. Node4's X-Node4-Country header is no help here: it is present only on plain-HTTP responses and on refusals, and an HTTPS tunnel or a SOCKS5 connection carries none, which covers almost every page a profile loads. Residential sends it only on a refused country, with the value unavailable. A whitelisted residential profile is untargeted by design, as described above.

When the profiles work and you want more addresses, the pricing page lists every plan, and the datacenter proxies page describes the Dedicated and Shared options for long-lived accounts. Running a different anti-detect browser? The same Node4 values go into BitBrowser and Hubstudio profiles.