Proxies for BitBrowser

Where Bit Browser specifically needs this

BitBrowser leans heavily on team features: shared profile pools, role based access and a local API for driving profiles from scripts. That makes it common in operations where several people touch the same set of accounts.

That sharing is exactly where the network side bites. If two operators open the same profile from different places, the fingerprint stays consistent but the exit address does not, and an account that suddenly moves country mid week looks compromised. Binding the profile to one sticky port keeps the address stable no matter who opens it.

Rotating or sticky for profiles

Use a sticky port for profile work. A profile that changes IP mid session looks like a hijacked account, which is the opposite of what you want. Each sticky port holds one address for the session, so assign a different port per profile.

Rotating ports suit collection and crawling, where a new address per request is an advantage rather than a red flag.

Setting it up

In the profile editor choose the proxy type, then enter host, port, username and password. BitBrowser will run a check before saving and shows the detected exit country, which is worth confirming matches the timezone you set.

If you drive profiles through the local API, set the proxy in the profile definition rather than passing it per launch, so scripted and manual sessions use the same address.

Where to go next

Running more than one tool against the same gateway is normal. These cover the others.

• All integration guides, setup notes for every tool we cover
• Guides and tutorials, the concepts behind the config, including when to rotate and when not to
• VMLogin setup, another antidetect browser, same one sticky IP per profile rule
• iXBrowser setup, another antidetect browser, same one sticky IP per profile rule
• Sticky proxies, why profile work needs a held address rather than rotation