Browsers

BitBrowser with ProxyGuys proxies

People reach for BitBrowser when they run a lot of profiles side by side, each with its own fingerprint. Setting up the first profile is quick. Keeping a long list of them paired with the right proxies is the harder part, so this guide covers both.

One profile, one proxy

Start in My Proxies. A proxy that shows Pending needs Start proxy before it carries traffic. From the SOCKS5 proxy box in the Connection column, take the host and the SOCKS5 port; under Credentials, use Copy username and Copy password. Then, in BitBrowser:

  1. Press Add on the profile list (Browser Profiles, or Browsers in some versions) and give the new profile a name.

  2. In the Proxy section, keep Proxy Method on Custom and set Proxy Type to SOCKS5.

  3. Fill in Host, Port, Username and Password: the host, the SOCKS5 port and your login.

  4. Press Check Proxy. It should return an IP with a US location. Then press Confirm to save the profile.

  5. Press Open on the profile to launch its browser window.

HTTP is an equally good option. Whichever type you set in BitBrowser, the port must come from the dashboard box of the same name.

Gathering logins for many proxies

For a handful of proxies, ⋮ then Details on each one gives a ready line in the form host:port:username:password. BitBrowser's batch import takes proxies in that same order, alongside a proxy type you set to match. Check which port the line holds before you use it, because the type you pick in BitBrowser has to match it.

For more than a handful, the API is quicker. Make a key with Create key on the API page, then:

# Create a key on the API page first; it is shown only once.
export PROXYGUYS_API_KEY="YOUR_API_KEY"

# Every proxy on the account, with host, HTTP and SOCKS5 ports and username
curl -H "Authorization: Bearer $PROXYGUYS_API_KEY" \
  https://proxyguys.com/api/v1/proxies

# One proxy's full login, password included (pp123456 is its API id)
curl -H "Authorization: Bearer $PROXYGUYS_API_KEY" \
  https://proxyguys.com/api/v1/proxies/pp123456/credentials

The list gives host, ports and username; the credentials call adds the password. The API id (it looks like pp123456) is not the proxy's username, so don't paste it into BitBrowser.

Keep profiles and proxies paired

  • Rename each proxy with the pencil icon in My Proxies so it carries the same name as its BitBrowser profile. It's just a label; the login stays as it was.
  • If you sort profiles into groups in BitBrowser, a matching word in the proxy names makes the two lists easy to compare.
  • Pressing Change gateway IP moves every proxy on the account to a new host. After that, every profile needs the new host, so only do it when you're ready to update them all.
  • Renew Proxies at the top of My Proxies renews several proxies in one go from balance, card or crypto. Renewing keeps the same proxy, location and settings, so the profiles need no changes.

Spot-check the IPs

Open a few profiles and visit api.ipify.org in each. Every profile should show a different IP. If two match, they are on the same proxy. Judge by the IP itself, not by the town a lookup site prints next to it: those databases frequently misplace mobile addresses.

When the check fails

  • Refused or timed out: an HTTP port under a SOCKS5 type, or the other way round. If the values came from a Details line, check which port it holds.
  • Authentication failed: the password didn't paste cleanly. Copy it again with Copy password.
  • Only some profiles fail: those proxies may be Pending or no longer Running. Start or renew them from My Proxies.
  • Whitelist endpoint in use: it only accepts the IPs on that proxy's list. See the IP whitelisting guide or switch back to the normal ports with a login.