How to set up a proxy in BitBrowser: add it, check it, fix the errors

To add a proxy in BitBrowser, open Browser Profiles, click Add (or edit a profile) and go to Proxy. Keep Method on Custom, set Type to HTTP for port 8080 or Socks5 for port 1080, paste host:port:user:pass into Host, click Check Proxy and Confirm. Give every profile its own sticky session. Below: each field, bulk import and a fix for each error.

BitBrowser keeps each browser profile apart: its own cookies, its own fingerprint and its own proxy. The proxy decides which IP address and which country the sites see, and BitBrowser takes the profile's time zone and language from that IP. Four values are enough to set it up, and a wrong type or a cut username is behind most failed checks. The field names below are the ones in BitBrowser's own documentation and in its current app, version 7.2.0; the values come from the QuanticData endpoint generator.

What you need before you start

• BitBrowser installed, with an account. Its documentation says a new account gets 10 free browser profiles; more profiles need a paid plan.
• A proxy plan. Residential Premium, ISP or mobile: all three work in BitBrowser, and each has its own section below.
• The four values: host, port, username and password. In the QuanticData dashboard they are under My proxies, on the plan's page, in the Endpoint generator.

The fields of BitBrowser's Proxy section

The Proxy section is the same when you add a profile and when you edit one. This is what each field does and what goes in it with a QuanticData Residential Premium line:

Field	What it does	QuanticData value
Method	Custom (you type the proxy), Extract By API (a provider's extraction link) or Proxy Management (a proxy you saved before)	Custom, or Proxy Management for a saved line
Lookup Channel	The service BitBrowser uses to look up the exit IP when you click Check Proxy	Leave the default
Type	HTTP, HTTPS, Socks5 or SSH; Direct Connection Mode means no proxy	HTTP for port 8080, Socks5 for port 1080
Protocol	IPv4 or IPv6 address of the proxy host	IPv4
Host	The proxy address; a whole Host:Port:Username:Password line pasted here is split into the four fields	residentialpremium.quantumproxies.io
Port	The proxy port	8080 or 1080
Username, Password	Optional in BitBrowser, needed for username and password plans	The whole username, with the targeting, and the password
Refresh Proxy	A refresh URL from providers that change the IP through a link	Leave empty
UDP	Shown for Socks5: lets WebRTC use UDP traffic	Optional; the steps here leave it off

Step by step: add a proxy to a BitBrowser profile

1. Generate the line. In the QuanticData dashboard open My proxies, then your plan. In the Endpoint generator choose the Country (and a Region or City if the profile needs one), set Session to Sticky, set Session TTL (minutes) to at least the time the profile stays open, choose the Protocol and keep the Output format on host:port:user:pass. The Preview shows the line.
2. Open the profile in BitBrowser. Go to Browser Profiles and click Add for a new profile, or open an existing profile to edit it. Scroll to the Proxy section.
3. Keep Method on Custom. Leave Lookup Channel on its default and Protocol on IPv4.
4. Set Type to match the port. HTTP for port 8080, Socks5 for port 1080.
5. Paste the whole line into Host. BitBrowser splits it into Host, Port, Username and Password. Check that Username holds the full string, with everything after the first dash.
6. Click Check Proxy. On the right BitBrowser shows the IP, Country/Region, State/Province, City, Lng/Lat, Timezone and Zip of the exit. The country has to match the -country- in the username.
7. Leave Refresh Proxy empty. It is for providers that change the IP through a URL; with QuanticData a new IP comes from a new session ID, explained below.
8. Click Confirm, then Open the profile. The profile's time zone and language follow the proxy's IP by default.

The line from the generator looks like this, with your own username and password in place of USER and PASS:

# Type HTTP, pasted into Host
residentialpremium.quantumproxies.io:8080:USER-country-nl-sid-p01-ttl-60m:PASS

# Type Socks5, the same session on the SOCKS5 port
residentialpremium.quantumproxies.io:1080:USER-country-nl-sid-p01-ttl-60m:PASS

In the username, -country-nl picks the exit country, -sid-p01 names the session and -ttl-60m keeps it for 60 minutes. A username cut at the first dash still logs in, but the profile then leaves from a random country on a new IP at every request.

One sticky session per profile

An antidetect profile is meant to look like one person on one connection. A rotating proxy changes IP on every request, which is fine for scraping and wrong for a profile that logs in. A sticky session keeps one IP for as long as the session lives, and the session lives in the username, so the line never changes once it is saved in the profile.

# profile 1: Netherlands, one session for a working day
residentialpremium.quantumproxies.io:8080:USER-country-nl-sid-p01-ttl-480m:PASS

# profile 2: same plan, its own session (never reuse p01)
residentialpremium.quantumproxies.io:8080:USER-country-nl-sid-p02-ttl-480m:PASS

# profile 3: Netherlands, open all day
residentialpremium.quantumproxies.io:8080:USER-country-nl-sid-p03-ttl-1440m:PASS

• A different session ID in every profile. Two profiles on the same line share one IP, which is what an antidetect browser is there to avoid.
• A lifetime longer than the work. The generator accepts up to 1440 minutes, a full day. When the session ends, the next request gets a new IP, and a site can see that as a new login location.
• The country in the username. Without -country- the exit can be anywhere, and the profile's time zone will not match what you planned.

Residential Premium, ISP and mobile proxies in BitBrowser

Residential Premium

Everything above is a Residential Premium setup: one sticky line per profile, with country, region, city or ISP in the username. Premium plans use username and password only, so Username and Password are always filled in. It is the right start for most profiles: home IPs in the country you choose. The plans are on the page for QuanticData residential proxies.

ISP

ISP plans give fixed IPs, listed on the plan's page under Assigned IPs. Choose HTTP / HTTPS or SOCKS5 above the list and the output format IP:Port:Username:Password, then copy one line per profile and paste it into Host: BitBrowser splits it the same way. Set Type to HTTP for the HTTP / HTTPS list and to Socks5 for the SOCKS5 list. An ISP IP stays the same for the life of the plan, so it suits accounts that should keep one address for months; there is nothing to rotate and Refresh Proxy stays empty. More on the page for ISP proxies.

Mobile

Mobile plans use the host mobile.quantumproxies.io with a Global, USA, EU or Asia gateway, HTTP on port 8080 or SOCKS5 on port 1080, and -type-mobile in the username. With Session set to Sticky the line goes into Host exactly like a residential one:

mobile.quantumproxies.io:8080:USER-country-nl-type-mobile-sid-p01-ttl-60m:PASS

Mobile plans also offer IP whitelist authentication: add your IP in the dashboard, take the host:port list it gives, and leave Username and Password empty in BitBrowser, since both are optional there. For which platforms mobile IPs suit, see mobile proxies for antidetect browsers; the plans are on the page for QuanticData mobile proxies.

Adding proxies to many profiles at once

1. Make the lines. In the generator, set Session to Sticky and the Quantity you need, ten by default, then Generate, and Copy all or Download. Every line has its own session ID.
2. Add the type to each line. BitBrowser's Batch Add reads the type from the start of the line, followed by ://. A line without a type is stored as Socks5, so HTTP lines on port 8080 need http:// in front. A name for the proxy can go at the end in curly brackets.
3. Store them in BitBrowser. Open Proxy IP, then Proxy Management, open the Add menu and choose Batch Add. Paste one proxy per line, up to 100 at a time, click Batch Detection to see the detected IP of each line, then Confirm.
4. Bind each proxy to a profile. Use the Bound Profiles icon in the proxy list, or open a profile and pick the saved proxy with Method set to Proxy Management. For profiles that already exist, More, then Batch Proxy Settings, on the Browser Profiles screen changes the proxy of the selected profiles.

http://residentialpremium.quantumproxies.io:8080:USER-country-nl-sid-p01-ttl-60m:PASS{NL profile 01}
http://residentialpremium.quantumproxies.io:8080:USER-country-nl-sid-p02-ttl-60m:PASS{NL profile 02}
http://residentialpremium.quantumproxies.io:8080:USER-country-nl-sid-p03-ttl-60m:PASS{NL profile 03}

To create the profiles and their proxies in one go, Batch Import on the Browser Profiles screen takes BitBrowser's Excel template: a proxy type column (http, https, socks5 or ssh) and the proxy as Host:Port:Username:Password, up to 1,000 rows per import.

A new IP for a profile

With QuanticData Residential Premium and Mobile the IP belongs to the session ID in the username, so a new session ID, for example -sid-p02 instead of -sid-p01, gives a new IP: change it in Username, click Check Proxy and Confirm. The old line keeps working until its lifetime ends. ISP proxies are static addresses by design: one IP per profile, for months. In all three cases Refresh Proxy stays empty.

BitBrowser proxy not working: errors and fixes

A proxy that fails shows up in three places: Check Proxy in the profile returns no result, the Detected IP column of Proxy Management shows a dash instead of an address, or the profile does not open. BitBrowser's documentation lists three causes for a profile that fails to launch: the proxy connection, your local internet connection, or the fingerprint settings. These are the cases behind the first one, in the order to check.

What you see	Usual cause	Fix
Check Proxy gives no result, or Detected IP shows a dash	The type does not match the port: Socks5 on 8080 or HTTP on 1080, often a Batch Add line without http://	Edit the proxy: Type HTTP with 8080, Socks5 with 1080, then check again
The same, with the right type	The username was cut, a colon is missing, or a space came with the paste	Copy the line again from the generator's Preview and paste it whole into Host
The check worked yesterday, fails today	The plan expired or its traffic is used up	Check the plan in My proxies: status, remaining traffic, expiry date
Wrong country or time zone	No -country- in the username, or Worldwide chosen in the generator	Generate the line with a country; let the profile take its time zone from the IP
Right country, a different city than expected	Lookup services place the same IP differently; BitBrowser's documentation notes the gap between its channels	Check the country and the IP; switch Lookup Channel to compare
The IP changes in the middle of a session	The session lifetime ended, or two profiles share one session ID	A longer -ttl- and a different -sid- in every profile
Check Proxy works, pages do not load	Your local network, not the proxy: BitBrowser's documentation separates the two	Run the test below from the same computer; if it works, contact BitBrowser support

One test outside the browser settles most cases in a minute. If this returns an address in the right country, the proxy works and the problem is in the profile's fields:

curl -x http://residentialpremium.quantumproxies.io:8080 \
  -U "USER-country-nl-sid-test-ttl-10m:PASS" https://ipinfo.io/json

If the same command fails on your network but works from another one, a firewall or your provider is blocking the connection to the proxy port.

HTTP or Socks5 in BitBrowser

Both work for browsing, and every QuanticData network offers both. HTTP on port 8080 is the simpler choice and the one to start with; it carries HTTPS sites too. Socks5 on port 1080 passes any kind of connection, not only web pages, which matters for tools inside the profile that do not speak HTTP; the details are on the page for SOCKS5 proxies. What breaks a profile is never the choice itself, only a type that does not match its port. For a wider view of why each profile needs its own address, see residential proxies for antidetect browsers.

Before you run accounts

A proxy changes where a profile's traffic comes from, not what the profile is allowed to do. Keep to each platform's terms and to the law where you work, and use one profile, one session and one identity per account.