How to set up a proxy in ClonBrowser: add it, bind it, fix the errors

To add a proxy in ClonBrowser, open New Browser, go to the Proxy tab, choose Custom, paste the line into Parse and click Parse, keep Protocol on http for port 8080, click Check network and then Create Browser. Give every browser its own sticky session. Below: each field, ISP and mobile lines, batch add, binding a saved proxy and the fixes when it fails.

ClonBrowser keeps every browser environment apart: its own fingerprint, its own cookies and, once you add one, its own proxy. The proxy decides which IP address and which country the sites see, and ClonBrowser's own guide recommends one independent proxy per environment. The field names below are the ones ClonBrowser shows in its Help Center, and the values come from the QuanticData endpoint generator.

What you need before you start

• ClonBrowser installed, with an account. It runs on Windows 10 or later (64-bit) and macOS 10.13 or later, and has a free plan with 10 browser environments.
• A proxy plan. Residential Premium, ISP or mobile: all of them work in ClonBrowser. The table further down says which one fits which browser.
• 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 proxy strings ClonBrowser accepts

ClonBrowser can read a whole proxy line and split it into its fields. Parse, in the proxy form, takes a proxy URL such as http://127.0.0.1:3000; Batch Add Proxy takes one line per row, and its note lists four layouts:

• host:port:username:password, with an optional name at the end.
• username:password@host:port.
• protocol://host:port:username:password, with an optional name at the end.
• protocol://username:password@host:port: what the QuanticData generator gives with the output format http://user:pass@host:port.

When a line starts with a protocol, ClonBrowser uses it; when it does not, it uses the protocol selected next to the field. A #name at the end of a line becomes the proxy's name. The same QuanticData proxy in the layouts that matter; the first one works in Parse and in Batch Add Proxy:

# protocol://username:password@host:port (the generator's http:// format)
http://USER-country-nz-sid-p01-ttl-60m:PASS@residentialpremium.quantumproxies.io:8080

# host:port:username:password, protocol taken from the selector
residentialpremium.quantumproxies.io:8080:USER-country-nz-sid-p01-ttl-60m:PASS

# SOCKS5 on its own port, with a name
socks5://USER-country-nz-sid-p01-ttl-60m:PASS@residentialpremium.quantumproxies.io:1080#nz-socks-01

The username is the whole string, with everything after the first dash: -country-nz picks the exit country, -sid-p01 names the session and -ttl-60m keeps it for 60 minutes. Copy it whole. A username cut at the first dash still authenticates, but the browser then leaves from a random country on a new IP at every request.

Step by step: add a Residential Premium proxy to a new browser

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 browser needs one), set Session to Sticky, set Session TTL (minutes) to at least the time the browser stays open, choose the Protocol and set the Output format to http://user:pass@host:port. Copy the line from Preview.
2. Open New Browser in ClonBrowser (top left) and go to the Proxy tab. A name in the Basic tab, such as NZ-01, helps in the list.
3. Set Mode to Custom. Direct means no proxy; Existing Proxy picks one you saved before.
4. Paste the line into Parse and click Parse. ClonBrowser fills Protocol, Host, the port, Username and Password from the line. You can also type the four values yourself.
5. Check Protocol against the port. http for port 8080, socks5 for port 1080. Name is optional: NZ profile 01 is easier to find later.
6. Click Check network. ClonBrowser tests the proxy and shows the IP it detects and its location. The country has to match the -country- in the username. IP Probe Channel is the service that looks the IP up; ipapi is what ClonBrowser's own screens show.
7. Click Create Browser, then launch it. In the Fingerprint tab, Timezone and Geolocation on Follow IP take the proxy's country.

ClonBrowser's Help Center suggests one more check after saving: launch the browser and open an IP lookup site. The IP it shows must be the one from the proxy.

One sticky session per browser

A browser environment 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 browser 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 has to change once it is saved.

# browser 1: New Zealand, one session for a working day
http://USER-country-nz-sid-p01-ttl-480m:[email protected]:8080

# browser 2: same plan, its own session (never reuse p01)
http://USER-country-nz-sid-p02-ttl-480m:[email protected]:8080

# browser 3: Australia, open all day
http://USER-country-au-sid-p03-ttl-1440m:[email protected]:8080

• A different session ID in every browser. Two browsers on the same line share one IP, which is exactly what ClonBrowser 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 Follow IP gives the browser a time zone you did not plan.

With Session set to Sticky, the generator makes as many lines as the Quantity field says, ten by default, each with its own session ID; Copy all or Download takes them out in the same format, ready for Batch Add Proxy.

ISP proxies in ClonBrowser

An ISP plan gives fixed IPs that stay the same for months, the right choice for accounts that should always log in from one address. In the plan's page they are under Assigned IPs, one per line as IP:Port:Username:Password, on port 50100.

1. Save the IP in ClonBrowser. Open Proxy in the left menu and click New. The New Http Proxy window opens.
2. Protocol http. It matches HTTP / HTTPS in the QuanticData panel.
3. Name it, for example ISP 01, then type the IP in Host, 50100 in the port, and the username and password from the same line. ExpiryTime is optional: a date you can set to see when the plan ends.
4. Check network, then Save. The IP ClonBrowser detects is the IP in Host: an ISP proxy does not rotate.
5. Bind it to one browser with Existing Proxy, as shown further down. One ISP IP per browser.

Mobile proxies in ClonBrowser

Mobile lines work like Residential Premium, with -type-mobile in the username and the host mobile.quantumproxies.io, HTTP on 8080 or SOCKS5 on 1080. In the generator choose the gateway (Global, USA, EU or Asia), the country and a sticky session, then generate one line per browser. With several browsers to fill, Batch Add Proxy saves all the lines at once:

1. On the Proxy screen, click the arrow next to New and choose Batch Add Proxy.
2. Proxy Protocol http: it applies to lines without a protocol.
3. Paste the lines into Proxy Information, one per row. Add #nz-mobile-01, #nz-mobile-02 at the end to name them.
4. Click Parse: every line becomes a row under Identified proxy information. PING tests them.
5. Click Confirm. The proxies are saved, not yet bound: bind each one to its browser.

http://USER-country-nz-type-mobile-sid-m01-ttl-60m:PASS@mobile.quantumproxies.io:8080#nz-mobile-01
http://USER-country-nz-type-mobile-sid-m02-ttl-60m:PASS@mobile.quantumproxies.io:8080#nz-mobile-02
http://USER-country-nz-type-mobile-sid-m03-ttl-60m:PASS@mobile.quantumproxies.io:8080#nz-mobile-03

Mobile plans also offer IP whitelist authentication: add your IP in the plan's page and use the host:port list it gives, with Username and Password left empty in ClonBrowser.

Which proxy type for which browser

Proxy type	In ClonBrowser	Good for
Residential Premium	One sticky line per browser through Parse; country, region, city or ISP in the username; username and password only	Most browsers: home IPs in the country you choose
ISP	Fixed IPs from Assigned IPs as IP:Port:Username:Password on port 50100; saved with New, one IP per browser	Long-lived accounts that should keep the same address for months
Mobile	One sticky line per browser with -type-mobile in the username; Global, USA, EU or Asia gateway; HTTP 8080 or SOCKS5 1080; IP whitelist available	Phone-first platforms and accounts tied to mobile networks: see mobile proxies for antidetect browsers

For a wider view of why each browser needs its own address, see residential proxies for antidetect browsers. The plans themselves are on the pages for QuanticData residential proxies, ISP proxies and QuanticData mobile proxies.

Bind a saved proxy to one browser

Proxies saved with New or Batch Add Proxy sit on the Proxy screen until you bind them. ClonBrowser binds them from the browser list:

1. In the browser list, hover the proxy cell of the browser and click Set Proxy, the edit icon next to it.
2. Choose Existing Proxy and tick one proxy in the list. The name and host:port of each one tell them apart.
3. Save. Change a proxy with the browser closed: ClonBrowser advises against switching it while the browser runs.
4. Repeat for the next browser with the next proxy. ClonBrowser allows one proxy on several browsers but advises against it, and two browsers on one sticky line share one IP.

A new IP on Residential Premium or Mobile

The IP is tied to the session ID in the username, so a new session ID, for example -sid-p02 instead of -sid-p01, is a new IP. Generate the new line, open the browser's proxy with the browser closed and paste it into Parse. The old line keeps working until its lifetime ends. ISP proxies are static addresses by design: one IP per browser, for months.

ClonBrowser proxy not working: errors and fixes

ClonBrowser's troubleshooting guide puts the causes of a failed proxy connection in four areas, to check in this order: the proxy configuration, your local network, the proxy itself outside ClonBrowser, and software on the computer that blocks it.

What you see	Usual cause	Fix
Check network fails on a new proxy	The protocol does not match the port: http on 1080 or socks5 on 8080	http with 8080, socks5 with 1080, or a socks5:// line on port 1080 through Parse
The same failure, with the right protocol	The username was cut, a value is missing, or a space came with the paste	Copy the line again from the generator's Preview and parse it whole
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
Every proxy fails, even good ones	The local network: a system proxy or a network tool in the way	Global Settings, Local Settings: Network Connection on No Proxy, then Test Local Network and Test System Network
Wrong country or time zone	No -country- in the username, or Worldwide chosen in the generator	Generate the line with a country; keep Timezone and Geolocation on Follow IP
The IP changes in the middle of a session	The session lifetime ended, or two browsers share one session ID	A longer -ttl- and a different -sid- in every browser
Some proxies in a batch fail	A line in the wrong layout, the wrong protocol, or an expired proxy	Fix those lines and parse again; check them with PING before Confirm

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 ClonBrowser's fields or on the computer:

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

If curl works and ClonBrowser still fails, the last area in its guide applies: a firewall, an antivirus or a security tool blocking ClonBrowser. Add ClonBrowser to its allowed list, or test from another network.

HTTP or SOCKS5 in ClonBrowser

Both work for browsing, and every QuanticData network offers both. HTTP on port 8080 is the simpler choice and the one to start with. SOCKS5 on port 1080 passes any kind of connection, not only web pages; the details are on the page for SOCKS5 proxies. What breaks a browser is never the choice itself, only a protocol that does not match its port.

Before you run accounts

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