AdsPower Proxy Setup: HTTP and SOCKS5 Guide

AdsPower manages browser profiles, while Databay supplies the network route. AdsPower's official proxy-list documentation explains that the browser does not include its own proxy service, so a profile must use a direct connection or credentials from an external provider. That boundary matters: changing a proxy changes the route seen by a destination, but it does not change who owns an account, what the destination permits, or whether a workflow is authorized.

For Databay, the reusable endpoint is gw.databay.co on port 8888. The dashboard provides the username and password that select the purchased network and any supported location or session options. AdsPower stores those values on one profile or in its saved Proxies list. Keep profile settings and proxy settings conceptually separate: browser state belongs to AdsPower; exit selection and session behavior belong to the Databay credential.

This guide covers the controls documented by AdsPower for one profile, saved proxies, and bulk profile creation. It deliberately excludes Local API payloads because those fields and plan requirements should be tested against the current API before publication.

Use the values shown in your Databay dashboard rather than reconstructing a credential from examples. In AdsPower, choose HTTP or Socks 5 as the proxy type, enter gw.databay.co as the host, 8888 as the port, and place the complete dashboard-issued values in Proxy username and Proxy Password. Do not add http:// to the host field when the protocol is already selected in the dropdown.

The same gateway can expose more than one proxy protocol, but protocol choice does not turn a residential exit into a datacenter exit or make a rotating route static. Those are separate purchasing and credential decisions.

AdsPower's proxy-type guide documents HTTP, HTTPS, Socks5, and SSH controls. Databay publishes HTTP proxying, HTTPS CONNECT tunnelling, and SOCKS5 access on the shared gateway. Start with the client's HTTP proxy setting, which handles HTTP proxying and HTTPS CONNECT, for an ordinary browser profile unless a tested application requirement specifically calls for SOCKS5; it is simpler to diagnose because browser navigation and proxy authentication use the familiar HTTP proxy path.

Choose SOCKS5 when the exact AdsPower workflow has been validated with SOCKS authentication and you need that client-to-gateway protocol. SOCKS5 is not an encryption claim: destination TLS still provides HTTPS protection, and certificate validation should remain enabled. DNS behavior can also vary by client, so verify the destination name resolves through the intended path rather than assuming a protocol label proves remote DNS.

If location matters, choose the Databay network and supported target in the dashboard before copying the username. Premium Residential is the relevant product for state or city requests, subject to live exit availability. A sticky session requests temporary route continuity; it is not a dedicated, permanent, or exclusive IP.

AdsPower documents proxy configuration inside the new-profile workflow. Use this reproducible sequence and record the AdsPower version if the labels differ:

1. Select + New Profile and open the profile's Proxy section.
2. Choose HTTP or Socks 5 under proxy type.
3. Enter gw.databay.co and port 8888, then paste the complete Databay username and password into their dedicated fields.
4. Run the proxy check before saving. AdsPower documents a passed or failed connection result; a pass shows that AdsPower could use the submitted route at that moment, not that every destination will accept it.
5. Save the profile, launch it, and perform the independent in-browser verification described below.

AdsPower also documents a combined host:port:username:password paste format. Dedicated fields are easier to audit and avoid ambiguity when a credential contains a reserved character. If a team uses the combined format, generate it from a secret-management process, test one non-sensitive profile first, and never paste a real password into tickets, chat, recordings, analytics, or source control.

Leave a provider-specific change-IP URL empty unless the current Databay dashboard explicitly supplies one for the purchased product. Databay route behavior is selected through the issued credential and connection lifecycle, not by inventing an AdsPower refresh URL.

A green AdsPower check is only the first layer of evidence. Launch the saved profile and open Databay's What Is My IP page through that same profile. Record the observed IP address, country or region estimate, ASN, protocol choice, profile name, and UTC time. Compare the result with the location requested in the dashboard. If city or state precision is material, use a second named geolocation source and define in advance whether both must agree.

Next, open a non-sensitive URL you own or are authorized to test. Compare it with a direct-route control while holding account, language, cookies, browser version, and time window constant. This separates a routing issue from a destination-specific response. Do not use a login checkpoint, CAPTCHA, restriction, or access refusal as a reason to rotate through more exits.

For a sticky route, repeat the IP check during the required work window and record any exit change or connection failure. A matching address demonstrates continuity only for those observations. It does not prove exclusive assignment, future reuse, or a permanent static proxy. The static versus rotating guide explains those boundaries in more detail.

For repeated work, AdsPower's Proxies list can store purchased external proxies and assign a saved entry to a profile. Create names and remarks that describe the route requirement rather than a person or account, for example databay-residential-us-sticky-qa. The label is operational metadata; it does not control the Databay exit.

Store a separate saved record whenever the dashboard username represents a materially different network, location, or session policy. Reusing the same host and port is expected, but overwriting one saved entry for unrelated work makes later evidence ambiguous. Limit who can view or edit the proxy password, and treat exported proxy lists as secrets.

When assigning a saved entry, check that the selected profile is authorized for that route, run AdsPower's proxy check again, then verify the observed exit inside the launched profile. Do not infer that separate saved rows guarantee separate IPs, or that two profiles with different labels cannot receive the same shared exit. If distinctness is an actual requirement, test and record it; if exclusive assignment is required, this shared residential product is not a dedicated proxy.

AdsPower's Bulk Create documentation supports Excel and TXT templates. Its documented fields include proxytype, a proxy value in Host:Port:Username:Password order, and proxyid when assigning an already saved proxy. Build and approve one profile manually before expanding the same mapping to many rows.

1. Export or download the current template from the installed AdsPower version rather than copying an old column layout.
2. Set the documented proxy type to http or socks5.
3. Place gw.databay.co:8888 before the dashboard-issued username and password in the proxy value, or reference a reviewed saved Proxy ID.
4. Give each row an operational name that can be traced to its owner and approved purpose.
5. Import a two-row pilot, run the proxy check for both rows, and verify the route inside each launched profile.

A successful import proves that AdsPower parsed the template. It does not prove that geography, session continuity, or destination access matches the plan. Preserve the redacted import file, template version, and verification results as change evidence. Never use random assignment when a specific regional or sticky route is part of the acceptance criteria.

AdsPower does not choose the Databay pool or geography. Make those decisions in the Databay dashboard and copy the resulting complete username into the profile. Premium Residential supports one country, state, city, ZIP, coordinate, or ASN request at a time where eligible exits are available. Residential Flex supports one country or continent target at a time. Shared datacenter and mobile routes also support one country or continent target at a time; do not assume that a country-capable product can satisfy a city requirement.

Choose rotating behavior for independent, authorized observations that do not share login or cart state. Choose a sticky target when one approved workflow needs temporary network continuity. Keep the same issued credential for the duration of that workflow and verify the observed exit at the start and at meaningful checkpoints. Connection reuse can affect when an exit changes, so claims such as “a new IP on every request” are too broad.

Write the requested network, geography, session window, and acceptance rule beside each AdsPower profile before rollout. If a target asks for a dedicated or permanent IP, do not relabel a sticky shared route as equivalent. Confirm live location availability with the smallest practical order before provisioning a fleet.

Change one layer at a time and keep the failed result. A broad “proxy failed” label hides several different problems:

The proxy checker can help separate a reachable endpoint from an application-specific problem. Keep credentials out of diagnostic URLs and logs.

An AdsPower proxy can provide a documented route for an authorized client workspace, owned-site localization test, approved advertising check, or other work the destination permits. Profile isolation and network routing do not authorize false identities, account farming, fake engagement, ban evasion, or attempts to bypass a security control.

Name the accountable owner, approved accounts, destinations, request budget, evidence to retain, and stop conditions before creating profiles. Use platform roles and official APIs or preview tools before browser automation where they cover the task. Stop on a checkpoint, CAPTCHA, restriction, rate limit, or authorization ambiguity, and escalate through the platform's support path.

Compare AdsPower with other supported tools in the partner directory, choose the network class on the proxy product hub, and review Databay's Acceptable Use Policy. The least privileged route that completes the approved task is the correct one.