Antidetect browser proxy setup

Antidetect browser proxy setup involves adding a connection, checking its exit IP, assigning it to a browser profile, and configuring time zone and language settings. WGBrowser supports HTTP, HTTPS, and SOCKS5, with a separate proxy assignment for each profile and an exit check before it opens.

Have the host, port, and authentication method from your proxy provider ready. The provider supplies the network connection; the browser manages profile fingerprints and website session data separately. This guide starts with a fixed proxy connection, then covers extraction sources and troubleshooting. See proxy features for an overview.

Updated 2026-11-01

Add the proxy and authentication details

Open Proxies → Proxy library and select New proxy. Choose HTTP, HTTPS, or SOCKS5 according to the service your provider supplies, then enter its host and port. The protocol describes the proxy connection; the fact that your target website uses HTTPS does not tell you which proxy protocol to select.

For credential-based authentication, enter the proxy user name and password. These are separate from your store or social account credentials. For a provider that uses an IP allowlist, authorize the connecting computer's exit as instructed by the provider. Recheck that requirement when changing networks or giving another member access.

Collect the protocol, host, port, and authentication method. Keep a provider's extraction URL separate from its fixed proxy address.
Save the connection with a name that identifies its account, store, or purpose.

Check the actual exit IP

Select Check and inspect the returned exit IP, country or region, city, and time zone. The host used to connect to a proxy and its final exit IP describe different points in the connection. Record the detected exit when verifying an account's network setup.

The proxy library lets you check saved connections together. Start by confirming one connection, then use the same process for others. If it cannot connect, inspect the protocol and authentication. If it connects through the wrong region, keep the result and review the provider's route or regional parameters before assigning it to a profile.

Assign the proxy to a browser profile

Create or edit the intended profile, open Proxy, and select Library to choose a checked connection. You can also select Custom and enter a proxy for that profile. Keep the profile name, platform account, and proxy purpose consistent so you can identify the correct setup when several windows are open.

Save the profile and open it to check the intended website and account. A proxy change does not require regenerating the entire fingerprint; see fingerprint settings for the device parameters. If you need a persistent exit IP, confirm that the provider offers it and check the result on later launches. Keeping the same host and port alone does not establish that the exit is unchanged.

Set time zone, language, and location

In the profile's fingerprint settings, choose Follow IP for Time zone, Language, and Location when those values should match the detected exit. Before the profile opens, the client checks the connection and applies the values. Review the profile's resulting settings; this does not require changing your computer's system language or time zone.

For WebRTC, choose Proxy only or Disabled according to the website's needs. Then check the exit, time zone, language, and WebRTC behavior from inside that profile. The browser fingerprint guide explains what the reported signals mean. A check helps verify the configuration; it does not determine whether a website will accept a login or account.

Connect a proxy extraction source

Open Proxies → Sources and select New source. Use URL template for a provider endpoint that returns text or JSON: configure the request and response parsing rules. Integration script supports providers requiring signing, token exchange, multiple requests, or a special response format. Sources are shared with the team, and creating, editing, or deleting them requires Manage proxies permission.

The Test panel can run the current configuration before you save it. Inspect the extracted host and port, exit check, and response body. An HTTP success response alone does not establish that a usable proxy was returned. Configure the source's success and failure rules to match the provider's response.

After testing, select Extraction for the profile's proxy kind and choose the source, region, and When to extract setting. Every time it opens requests a proxy for each launch; Only when the last IP stops working checks the previous connection before extracting again. Choose based on the proxy lifetime and account workflow. See proxy API extraction for more detail.

Test parsing and connection results before binding the source to a working profile.
For a script written or changed by someone else, use Approve script to review it, then Allow on this device before running it locally.

Troubleshoot connection and region errors

If extraction returns a proxy but the exit check fails, inspect the protocol, credentials, and expiration. If the extraction request itself fails, inspect the provider's allowlist, key, balance, and request parameters. Correct configuration errors before retrying. For a rate limit, adjust request timing according to the response.

If the selected region has no available proxies, opening a profile does not automatically switch to another region. Workflow plugins can explicitly configure regional fallback, but that is separate from normal profile launch behavior. If the detected exit is unsuitable, stop using that configuration, review its regional parameters and test result, and decide whether to change the proxy.

Recheck proxy access on another computer

When moving a profile, check both its cloud sync data and proxy authentication on the new computer. Extraction requests are sent directly from the local computer. A provider using an IP allowlist must permit that computer's exit, and an integration script needs local approval on the new device.

Read proxy warnings after importing a profile or claiming a share. If its extraction source cannot be reused or created, the result may report that the profile now uses no proxy. Resolve that warning before opening it. For multiple accounts, complete one profile's connection check first, then apply the same checks to the remaining profiles.

FAQ

Why does my proxy fail in an antidetect browser?

Check the proxy protocol, host, port, credentials, expiration, and any IP allowlist requirement. For an extraction proxy, inspect the provider response separately from the exit check: receiving a host and port does not establish that the connection works. If the source request fails, review its key, balance, and parameters before repeating it.

Why is my proxy exit IP in a different city?

Use the detected exit result to check the connection, then review the provider's route, regional request parameters, and returned data. A proxy name or selected city does not confirm the final exit. Normal profile launches do not automatically choose another region when resources are unavailable. Correct the setup before using it for work that requires a specific location.

Can a profile get a new proxy whenever it opens?

Yes. Bind an extraction source and choose Every time it opens under When to extract. You can instead choose Only when the last IP stops working. The provider's available resources determine the returned IP, so requesting a proxy on each launch does not guarantee a different IP or a persistent exit address.

Do I need to update my proxy allowlist on another computer?

Check the provider's authentication requirements if the new computer connects from a different exit IP. Extraction requests originate directly from that computer, so its exit may need to be added to the provider's allowlist. Team members should verify this on their own devices. A copied or synced profile does not automatically authorize a new network connection.