Antidetect BrowserHTTP, HTTPS, SOCKS5About 5 minutes

How to Set Up a Proxy in BitBrowser

BitBrowser is a Chromium-based fingerprint browser built for running a lot of accounts side by side. Every browser profile keeps its own fingerprint, cookies, and proxy, and the app adds groups, RPA automation, and profile sharing across a team on top of that. Its proxy panel takes HTTP, HTTPS, and SOCKS5, and it will split a full ip:port:user:pass string across its own fields for you, so moving FleetProxy credentials over is mostly copy and paste.

Get your proxies Sign up with Google

Full BitBrowser setup, start to finish

What You Need

An active FleetProxy plan (residential rotating, static residential, mobile rotating, or datacenter)
BitBrowser installed and signed in
Your proxy credentials from the FleetProxy dashboard

Not sure which proxy type fits? Rotating residential works for most multi-account setups, while static IPs suit accounts you keep long term.

Get Your FleetProxy Credentials

Every BitBrowser profile needs a host, port, username, and password. Here is where to find them in the dashboard.

1
Open Active Proxies
Log in to the FleetProxy dashboard and click Active Proxies in the left sidebar. It lists every plan you already own.
2
Manage the plan you want to use
Find the product you are connecting, then click Manage. Each product has its own host and ports, so pick the one you actually plan to route traffic through.
3
Generate and copy your proxy
Open the Generator tab. Choose country, state, city, or ISP if you need a specific location, pick HTTP/HTTPS or SOCKS5, then set rotation to Random IP or Sticky IP. Your credentials appear on the right, ready to copy.

Host and port for every product

FleetProxy host and port by product
Product	Host	HTTP / HTTPS	SOCKS5
Residential Rotating	residential-v2.fleetproxy.io	5000	5000
Mobile Rotating	mobile.fleetproxy.io	5000	5000
Datacenter Rotating	datacenter.fleetproxy.io	9000	9000
Static Residential (ISP)	Your assigned IP address	50100	50101

BitBrowser Proxy Setup, Step by Step

1
Switch the format to ip:port:user:pass
Still in the FleetProxy generator, open the Format dropdown and choose {host}:{port}:{user}:{pass}, then click Copy. BitBrowser reads that single line and fills in its own host, port, username, and password fields from it, so picking the format here saves you retyping four values later.
2
Open Browser Profiles
Launch BitBrowser and click Browser Profiles in the left sidebar. This is the list of every profile you have, and each one runs on its own fingerprint and its own IP.
3
Click Add and name the profile
Press Add to open the new profile dialog and give it a name you will recognize later. The rest of the Basic tab can stay on its defaults unless you need it. Note that Platform, Username, and Password here belong to the site you plan to log in to, not to your proxy.
4
Scroll down and pick your proxy type
Scroll to the Proxy section and leave Method on Custom. Open the Type dropdown and choose HTTP, HTTPS, or Socks5, matching whichever you generated in the dashboard. Leaving Lookup Channel on IP2Location lets BitBrowser report back where the IP actually lands.
5
Paste the proxy, check it, then confirm
Paste the copied line into the Host field. BitBrowser splits it up and fills Port, Username, and Password on its own. Click Check Proxy and it returns the IP along with country, city, and timezone. If that matches the location you picked, click Confirm to save the profile.

If you are using static residential (ISP) proxies

For static residential (ISP) proxies there is no gateway domain to use. Put the IP address assigned to you in the dashboard into Host, then set the port to 50100 for HTTP or 50101 for SOCKS5. Username and password do not change.

Verify It Actually Works

Open httpbin.org/ip inside the launched profile. The address it returns should be your FleetProxy IP rather than your own. The Check Proxy result inside BitBrowser is a good first signal, but testing from inside the running profile is what proves traffic is really being routed.

You can also run the address through our IP lookup tool to confirm the country and provider, or use the proxy tester to check the connection responds before you start working in the profile.

Troubleshooting BitBrowser Proxy Errors

Check Proxy fails

Check the port against the table above. Residential rotating takes 5000 for HTTP and SOCKS5 alike, while static ISP keeps the two on separate ports, so a mismatch there stops the connection. Then re-copy the credentials from the dashboard, since a trailing space is the most common cause.

Pasting the proxy did not fill the other fields

BitBrowser only splits the line when it is in ip:port:user:pass order. Go back to the FleetProxy generator, switch the Format dropdown to {host}:{port}:{user}:{pass}, copy again, then paste into Host.

Profiles are getting linked to each other

Give every profile its own IP instead of sharing one across several. Match the profile timezone and language to the country of its proxy as well, since a mismatch there is easy for a platform to spot.

Still getting blocked once everything connects? That is usually an IP reputation problem rather than a setup problem, and our guide on avoiding IP bans covers what to change.

BitBrowser Proxy Setup FAQ

Does BitBrowser support SOCKS5 proxies?

Yes. The Type dropdown in the proxy settings offers HTTP, HTTPS, and Socks5 alongside SSH and a direct connection mode. Pick whichever you generated in the dashboard. On residential rotating the port is 5000 either way.

Can each BitBrowser profile use a different proxy?

It can, and it should. Proxy settings live on the individual profile, so every account browses from its own IP. That separation is what stops platforms from tying your accounts together.

Do I have to enter host, port, username and password separately?

No. Paste the whole ip:port:user:pass line into Host and BitBrowser spreads it across the four fields itself. That is the reason the first step sets the FleetProxy generator to that format.

Which proxies work best with BitBrowser?

Residential rotating suits volume work that needs fresh IPs, while static ISP addresses suit accounts you hold long term. Mobile IPs carry the most trust on mobile-first platforms.