How to set up a proxy in XLogin: add it, test it, fix the errors

To add a proxy in XLogin, open the profile's Setting proxy server, turn on Enable proxy server, pick HTTP Proxy for port 8080 or Socks 5 Proxy for 1080, click Paste proxy info with the line copied, then Test Proxy and Save. Give every profile its own sticky session. Below: each step, Residential Premium, ISP and mobile lines, bulk import and a fix for each error.

XLogin keeps every browser profile apart: its own cookies, its own fingerprint and its own proxy. XLogin has no proxy network of its own, so the IP address and the country the sites see come from the proxy you set in each profile. The field names below are the ones in XLogin's Help Center and in the current client, and the values come from the QuanticData endpoint generator. One test from this guide is real: a Colombia line checked on 23 October 2026 came out in Bogotá with the America/Bogota time zone.

What you need before you start

• XLogin on Windows, with an account. The client runs on Windows only (Windows 7 to 11 and Windows Server 2016), on a PC, a virtual machine or a VPS. New users can ask XLogin's support for a three-day trial with up to five browser profiles.
• A proxy plan. Residential Premium, ISP or mobile: all of them work in XLogin. The table further down says which one fits which profile.
• 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 formats XLogin accepts

The Proxy settings window has four fields, IP address, Port, Username and Password, and a Paste proxy info button that fills them from the clipboard. XLogin's documentation lists two layouts for it:

• IP:Port:Username:Password: what the generator gives with the output format host:port:user:pass. A host name works in the IP address field, not only an IP.
• Username:Password@IP:Port: the same proxy, the generator's user:pass@host:port.
• No login: with IP whitelist authentication, Username and Password stay empty; IP address and Port are the only required fields.

The type is not part of the pasted line: it is the Proxy type list above the fields. XLogin supports HTTP, HTTPS, SOCKS4, SOCKS5 and IPv6 proxies. The same QuanticData proxy in both layouts:

# IP:Port:Username:Password, Proxy type HTTP Proxy
residentialpremium.quantumproxies.io:8080:USER-country-co-sid-p01-ttl-60m:PASS

# Username:Password@IP:Port, Proxy type Socks 5 Proxy (its own port)
USER-country-co-sid-p01-ttl-60m:PASS@residentialpremium.quantumproxies.io:1080

The username is the whole string, with everything after the first dash: -country-co 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 profile then leaves from a random country on a new IP at every request.

Step by step: add a proxy to an XLogin 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. Copy the line from Preview.
2. Open the Proxy settings window in XLogin. In a new profile (New browser profile), click Setting proxy server under Basic setup. For an existing profile, right-click it in Browser profile and choose Edit Proxy configuration.
3. Turn on Enable proxy server.
4. Pick the Proxy type that matches the port. HTTP Proxy for port 8080, Socks 5 Proxy for port 1080.
5. Click Paste proxy info. XLogin fills IP address, Port, Username and Password from the line you copied. Check that the username arrived whole, with no space at the end.
6. Click Test Proxy. The Test IP URL list next to it picks the checking service, ip234 by default. A Tips window shows the IP, country, city, region, time zone, latitude, longitude and zip of the exit; the country has to match the -country- in the username.
7. Confirm, then Save. Back in the profile, Save profile.

The test checks the proxy from your computer, the same way the profile will use it. If the Tips window shows the right country, the profile will leave from that country; if it shows an error, nothing else in the profile will fix it, so the section on errors below comes first.

One sticky session per profile

An antidetect profile is meant to look like one person on one connection, and XLogin's own documentation says the same: one browser profile, one unique IP. 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 has to change once it is saved in the profile.

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

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

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

Three rules cover almost every case:

• A different session ID in every profile. Two profiles on the same line share one IP, which is exactly 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.

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, and Copy all or Download takes them out in the same format. One line per profile. For a new IP on Residential Premium or mobile, put a new session ID in the username, -sid-p02 instead of -sid-p01: XLogin has no change-IP field, and none is needed.

Residential Premium, ISP and mobile proxies in XLogin

Proxy type	In XLogin	Good for
Residential Premium	One sticky line per profile; HTTP Proxy on 8080 or Socks 5 Proxy on 1080; country, region, city or ISP in the username; username and password only	Most profiles: home IPs in the country you choose
ISP	Fixed IPs listed under Assigned IPs as IP:Port:Username:Password, port 50100 for HTTP, 50101 for SOCKS5; one IP per profile	Long-lived accounts that should keep the same address for months
Mobile	One sticky line per profile 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

Residential Premium

The step-by-step above uses a Residential Premium line: residentialpremium.quantumproxies.io, port 8080 with HTTP Proxy or 1080 with Socks 5 Proxy, and the targeting and the session in the username. Region and city targeting go in the same username when the profile needs a specific city; the generator writes them for you.

ISP proxies

In the dashboard, Proxy endpoints, Assigned IPs lists one fixed IP per line. Keep Protocol on HTTP / HTTPS and Output format on IP:Port:Username:Password, then copy one line per profile: the port is 50100. In XLogin, right-click the profile, Edit Proxy configuration, choose HTTP Proxy, click Paste proxy info and Test Proxy: the IP in the Tips window is the IP of the line. For Socks 5 Proxy, switch Protocol to SOCKS5 in the panel first: the port in the list changes to 50101. That IP does not change, so keep one ISP IP for each profile and leave it there.

Mobile proxies

Mobile lines work like Residential Premium, with -type-mobile in the username and their own host, mobile.quantumproxies.io. Choose the gateway (Global, USA, EU or Asia) and the protocol in the generator, then match the Proxy type in XLogin: Socks 5 Proxy for 1080, HTTP Proxy for 8080. Mobile plans also offer IP whitelist authentication: add your computer's IP in the dashboard, use the host:port list it gives and leave Username and Password empty in XLogin. For phone-first platforms, see mobile proxies for antidetect browsers.

For a wider view of why each profile 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.

Adding proxies to many profiles at once

XLogin imports proxies from a TXT file, one line per selected profile, with the type in front of each line:

HTTP:residentialpremium.quantumproxies.io:8080:USER-country-co-sid-p01-ttl-60m:PASS
HTTP:residentialpremium.quantumproxies.io:8080:USER-country-co-sid-p02-ttl-60m:PASS
SOCKS5:mobile.quantumproxies.io:1080:USER-country-co-type-mobile-sid-p03-ttl-60m:PASS

1. Make the lines. In the generator, set Session to Sticky and the quantity you need, generate, then Download. Add HTTP: (or SOCKS5: for port 1080) at the start of every line, for example with a find and replace in a text editor.
2. Select the profiles. In Browser profile, select them the way you select rows in a spreadsheet, with Ctrl or Shift.
3. Import. Right-click and choose Batch import proxy to the selected profile, then pick the TXT file.
4. Check. Batch export proxy of the selected profile writes the current proxies back to a TXT file, a quick way to confirm that every profile got its own line.

XLogin's spreadsheet route does the same with cookies: Export selected cookie to excel gives a template with a proxy column, and Batch import cookies asks whether to import and override the proxy settings this time.

Sites that skip the proxy: the bypass list

XLogin passes launch parameters to the profile's Chromium, and one of them is a bypass list: hosts that connect directly from your own IP instead of through the proxy. Its documentation suggests it to keep browser update downloads off proxy traffic.

1. One profile: New browser profile (or Edit profile), Other configurations, Custom launch browser parameters.
2. Write one parameter with the hosts separated by commas, and * as a wildcard: --proxy-bypass-list=*.gvt1.com,update.googleapis.com. Other parameters go in the same box, separated by a space.
3. Save profile. Every host not in the list still goes through the proxy.
4. All new profiles: My account, Preferences, Custom launch browser parameters. Existing profiles in bulk: select them, right-click, Batch edit selected Profile, Navigator Settings, Edit.

Two things to keep in mind. Never put a site you log into on the list: that site would see your own IP next to the profile's fingerprint. And localhost or 127.0.0.1 do not need to be listed: Chromium has sent local addresses around a manually set proxy since version 72, and XLogin's current kernels are far newer.

Time zone, language and WebRTC follow the proxy

A proxy in Colombia with a browser on New York time is easy to spot. In the profile's Basic configuration, keep Enable setting time zone based on IP on, tick Lang based on IP next to Accept-Language, and leave WebRTC on replacement mode with Auto detect IP, so that WebRTC reports the proxy's address and not your own. With these on, the time zone, the language and the WebRTC address all come from the proxy's IP.

XLogin proxy not working: errors and fixes

XLogin reports a failing proxy in three places: the Tips window after Test Proxy, a window when a profile cannot start, and a Windows notification. Its documentation lists the causes, from traffic left on the proxy account to a network that cannot reach the proxy. These are the cases behind them, in the order to check.

What you see	Usual cause	Fix
Failed to test the proxy server.	The type does not match the port: HTTP Proxy on 1080 or Socks 5 Proxy on 8080	HTTP Proxy with 8080, Socks 5 Proxy with 1080
The same message, with the right type	The username was cut or a space came with the paste	Copy the line again from the generator's Preview and use Paste proxy info
Your Proxy IP failed to connect, pls check your proxy IP.	The proxy did not answer when the profile started: most often a plan that expired or ran out of traffic	Check the plan in My proxies: status, remaining traffic, expiry date; then the two rows above
Proxy network is blocked, please check your proxy software.	Your network, a firewall or a VPN blocks the connection to the proxy port	Allow outgoing connections to port 8080 or 1080, or try another network
The browser asks for a username and password	Wrong credentials, or an IP whitelist line used from an IP that is not on the list	Paste the line again; on a whitelist line, add your current IP in the dashboard
Test passes, pages show "This site can't be reached", "Connection time-out" or "Bad gateway"	A local VPN or firewall in between, or the session ended	Try without the local VPN; a longer -ttl-, or a new session ID for a fresh IP
Wrong country, or IP and DNS in different places on a checker site	No -country- in the username; a DNS mismatch alone is the checker's database, as XLogin's documentation notes	Generate the line with a country; trust the Tips window over checker sites

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-co-sid-test-ttl-10m:PASS" https://ipinfo.io/json

XLogin's local API runs the same test as the Test Proxy button, which helps when profiles are created by a script: a GET request to http://127.0.0.1:35000/api/v1/proxy/test with proxytype, proxyserver, proxyport, proxyusername and proxypassword returns the IP and location of the exit, or "Failed to test the proxy server."

HTTP or SOCKS5 in XLogin

Both work for browsing, and every QuanticData network offers both. HTTP Proxy on port 8080 is the simpler choice and the one to start with. Socks 5 Proxy on port 1080 passes any kind of connection, not only web pages; 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.

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.