How to set up a proxy in MuLogin: add it, check it, fix it

To add a proxy in MuLogin, open Add browser, scroll to Proxy settings, choose HTTP or SOCKS5 to match the port, fill IP address, Port, Login user and Login password (or paste one host:port:user:pass line), click Check the network and save. Give every profile its own sticky session. Below: each step, Residential Premium, ISP and mobile lines, and a fix for each failure.

MuLogin is an antidetect browser for Windows: every browser profile gets its own fingerprint, cookies and, once you add one, its own proxy. MuLogin has no proxy service of its own, so the proxy decides which IP address and country the sites see. MuLogin's documentation puts the rule plainly: one browser profile, one unique IP. The field and button names below are the ones in MuLogin's own documentation and in the current client, and the values come from the QuanticData endpoint generator.

What you need before you start

• MuLogin installed, with an account. It runs on Windows only. New accounts can ask MuLogin's support for a 3-day trial with up to 5 browser profiles.
• A proxy plan. Residential Premium, ISP or mobile: all of them work in MuLogin. 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 (for ISP plans: under Assigned IPs).

The fields and paste formats MuLogin reads

The proxy lives in the profile window, Add browser for a new profile or Edit browser for a saved one, on the Basic Configuration tab under Proxy settings. The dropdown starts on noproxy (Direct connection mode) and offers HTTP, SOCKS4, SOCKS5 and HTTPS. Below it come four fields:

• IP address: the proxy host. It takes a host name as well as an IP.
• Port: 8080 for HTTP or 1080 for SOCKS5 on QuanticData Residential Premium and mobile.
• Login user: the whole username, targeting and session included.
• Login password: the password.

Next to Check the network sit two small icons. The green one pastes a whole line into the four fields; the red bin clears them. MuLogin's documentation lists two paste formats:

# IP:Port:Username:Password, with the type chosen in the dropdown first
residentialpremium.quantumproxies.io:8080:USER-country-no-sid-p01-ttl-60m:PASS

# Proxy type://IP:Port:Username:Password, the type travels with the line
HTTP://residentialpremium.quantumproxies.io:8080:USER-country-no-sid-p01-ttl-60m:PASS
SOCKS5://residentialpremium.quantumproxies.io:1080:USER-country-no-sid-p01-ttl-60m:PASS

The first one is exactly what the QuanticData generator gives with the output format host:port:user:pass, so no editing is needed. Note that MuLogin's format is all colons: user:pass@host is not one of its layouts. The login is the whole username, with everything after the first dash: -country-no picks the exit country (Norway here), -sid-p01 names the session and -ttl-60m keeps it for 60 minutes. A login 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: Residential Premium in a MuLogin 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 profile window. In MuLogin go to Browser Manage, Browser List, and click Add browser (or the green pencil in the Operation column for a saved profile). Stay on Basic Configuration and scroll to Proxy settings.
3. Pick the type that matches the port. HTTP for port 8080, SOCKS5 for port 1080.
4. Paste the line. Click the green paste icon: IP address, Port, Login user and Login password fill in. Typing the four values works the same way.
5. Check that Login user is whole. It must read USER-country-no-sid-p01-ttl-60m, not just USER.
6. Click Check the network. When the proxy answers, a green line appears under Proxy settings: the exit IP and Country / Region with region, country and city. MuLogin's documentation calls this detailed IP information: it means the test passed.
7. Save. The profile keeps this proxy every time it opens.

Two settings on the same tab finish the job. Keep WebRTC on the replacement mode with Automatically detect IP ticked, so WebRTC reports the proxy's address, which is what MuLogin's documentation recommends in normal use. Turn on Start to set time zone based on IP and tick Set language based on IP, so the time zone and language follow the proxy's country instead of your computer's.

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 profile's proxy never has to change once it is saved.

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

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

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

• A different session ID in every profile. Two profiles on the same line share one IP, which is exactly what MuLogin 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 login. Without -country- the exit can be anywhere, and the profile's time zone and language 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.

ISP proxies in MuLogin

An ISP plan gives fixed addresses, each one the same IP for as long as the plan runs. They suit profiles that log in to the same accounts for months. In the dashboard the plan's page lists them under Proxy endpoints, Assigned IPs: choose the Protocol (HTTP / HTTPS or SOCKS5), keep the Output format on IP:Port:Username:Password, then Copy selected or Export .txt.

That output format is the very layout MuLogin's paste icon reads, so each line goes in as it is: choose HTTP (or SOCKS5 if you chose SOCKS5 in the dashboard), click the green paste icon, check and save. The port is the one listed next to the IP, 50100 in the example. Two rules matter more here than anywhere else: one IP per profile, never shared, and the profile's country taken from that IP, because an ISP address does not move.

Mobile proxies in MuLogin

A mobile line goes in like a Residential Premium one: one sticky line per profile, HTTP on 8080 or SOCKS5 on 1080, with -type-mobile in the login. In the mobile Endpoint generator choose the gateway (Global, USA, EU or Asia), the country, Sticky and the protocol. Mobile plans also offer IP whitelist authentication, where the plan recognises your IP and no login is sent; with a username and password the line works from any network.

# mobile, Norway, sticky for 60 minutes
mobile.quantumproxies.io:8080:USER-country-no-type-mobile-sid-p02-ttl-60m:PASS

For a profile that is already saved there is a shorter way than Edit browser: in the Browser List, the first green icon under Open in the Quick operation column opens Proxy server settings, a small window with the same four fields. Paste proxy information fills them from the line, Test proxy information checks it and Complete saves it.

MuLogin also simulates Android and iOS browsers: create the profile with Android or iOS as the operating system and pair it with a mobile line, so the device and the network tell the same story. A new mobile IP is a new session ID in the login, -sid-p03 instead of -sid-p02; the old line keeps working until its lifetime ends. More on the networks themselves on mobile proxies for antidetect browsers.

Which proxy type for which profile

Proxy type	In MuLogin	Good for
Residential Premium	One sticky line per profile; country, region, city or ISP in the login; username and password only	Most profiles: home IPs in the country you choose
ISP	Fixed IPs from Assigned IPs as IP:Port:Username:Password, pasted as they are; 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 login; Global, USA, EU or Asia gateway; HTTP 8080 or SOCKS5 1080; IP whitelist available	Android and iOS profiles, phone-first platforms

For 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.

Proxies for many profiles at once

1. Make the lines. In the generator, set Session to Sticky and the Quantity you need, generate, then Copy all or Download. For ISP, select the IPs under Assigned IPs and Export .txt.
2. Create the profiles. Batch add in the Browser List creates many profiles in one go; MuLogin's documentation notes that the proxy then has to be set for each profile.
3. Fill the proxies through Excel. Select the profiles, open the menu with the three dots and choose Export cookies to Excel. Put one proxy per profile in the proxy columns of that file and save it, then click Batch import cookies and pick the file. When MuLogin asks "Do you want to import and overwrite the proxy server settings this time?", choose Complete to import the proxies together with the cookies; No imports the cookies only.

For scripts, MuLogin's local REST API on port 30725 has a Test Proxy call that takes the type, server, port, username and password, so a list can be checked before it reaches the profiles.

Keep some hosts off the proxy

MuLogin can send chosen hosts around the proxy. In the profile window open the Other Configuration tab and, in Customize startup browser parameters, write --proxy-bypass-list= followed by the hosts, separated by commas. Everything else keeps going through the proxy.

A bypassed host sees your own IP, not the proxy's. Keep the list to local addresses such as localhost and 127.0.0.1, for tools that run on your own computer, and never put a site you log in to on it.

MuLogin proxy not working: no IP information after the check

When Check the network does not bring the green IP line, the test did not pass: MuLogin's documentation treats the profile as ready to open only once the IP information appears. Its list of causes: the settings do not match the proxy, the proxy is slow or no longer valid, the account has no traffic or balance left, or your own network cannot reach the proxy. With QuanticData these are the cases behind them, in the order to check.

What you see	Usual cause	Fix
No IP information after Check the network	The type does not match the port: HTTP on 1080 or SOCKS5 on 8080	HTTP with 8080, SOCKS5 with 1080, or a type prefix in the pasted line
The same, with the right type	Login user cut at a dash, a colon missing, or a space came with the paste	Clear the fields with the bin icon and paste the line again from the generator's Preview
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, time zone or language	No -country- in the login, or the profile's time zone and language set by hand	Generate the line with a country; turn on Start to set time zone based on IP and Set language based on IP
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
The test passes, pages do not load	Your network blocks the proxy port, or the site refuses that address	Run the test below from the same computer; for one refusing site, a new session ID or a mobile or ISP line

One test outside MuLogin settles most cases in a minute. MuLogin runs on Windows, and Windows 10 and 11 include curl: in PowerShell type curl.exe, because plain curl there is another command.

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

If it returns an address in the right country, the proxy works and the problem is in the profile's fields. If it fails on your network but works from another one, a firewall or your provider is blocking the connection to the proxy port, which is the network cause in MuLogin's list.

HTTP or SOCKS5 in MuLogin

Both work for browsing, and every QuanticData network offers both. HTTP on port 8080 is the simpler choice and the one to start with; HTTPS sites still load encrypted end to end through it. SOCKS5 on port 1080 passes any kind of connection, not only web pages; the details are on the page for SOCKS5 proxies. The HTTPS and SOCKS4 entries in MuLogin's dropdown are for proxies that need them; QuanticData lines use HTTP or SOCKS5. What breaks a profile is never the choice itself, only a type that does not match its port. The same setup in another antidetect browser is in our guide to setting up a proxy in Dolphin Anty.

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.