Mobile proxies for Multilogin: setup, checks and fixes

The short answer

Multilogin is the antidetect browser used by agencies and e-commerce teams to run many isolated browser profiles, each with its own fingerprint, cookies and proxy. The proxy is the half of a profile the browser cannot provide, and the rule is one exit per profile that does not change while the profile is open. With QuanticData mobile that is a 4G/5G carrier address shared with real phones, pinned to the profile by a session ID in the username with a lifetime up to 24 hours, in the account’s country, with the carrier selectable where the catalog lists it, at $5 for 1 GB and no port fee. HTTP and SOCKS5 share the credentials. Everything below is that one operation done carefully, plus the fixes for the errors people search for.

Where the proxy goes in Multilogin

In Multilogin the proxy belongs to the profile: create or edit a profile, open its Proxy section, choose a custom proxy rather than the browser’s own, pick HTTP or SOCKS5, and fill the four fields. Recent versions also accept the whole thing pasted as one line, host:port:username:password. The names of the sections move between releases; the four values do not.

Step by step: a QuanticData mobile proxy in a Multilogin profile

1. Get the four values. In the QuanticData dashboard pick a mobile pack ($5 for 1 GB is enough to test) and open the endpoint generator: it shows host, the HTTP and SOCKS5 ports, a username built from your choices, and the password.
2. Build the username for this profile. Country of the account, a session ID that only this profile will ever use, and a lifetime that covers the time the profile stays open: USER-country-us-sid-shop01-ttl-720m. Add -isp-t_mobile_usa or another carrier code from the country page when the profile should look like it lives on one operator.
3. Open the profile’s proxy section. New profile (or edit an existing one), Proxy: choose the custom proxy option, then HTTP or SOCKS5. Do not leave the built-in option selected if you want to control the session yourself.
4. Enter host, port, username, password. Host and port from the dashboard (the port must match the protocol you chose), login = the whole username string including -country- and -sid-, password = the dashboard password.
5. Press the check button. Multilogin prints the exit IP, its country and its time zone. The country must match the account; let the profile take its time zone and language from the proxy, or set them by hand to the same values.
6. Save, launch, and repeat with a new session ID for the next profile. Every profile gets its own -sid-. The host, port and password stay the same across all of them; bandwidth is shared across the plan.

No screenshots on this page on purpose: the fields move between releases and a stale screenshot misleads more than it helps. The four values and the check button are constant.

One sticky session per profile: the username

The configuration travels in the username, so the profile’s proxy settings never change once written. USER and PASS stand for the dashboard credentials.

# profile 1: US exit on T-Mobile, one session for 12 hours
      USER-country-us-isp-t_mobile_usa-sid-p01-ttl-720m
      
      # profile 2: same plan, different session ID (never reuse p01)
      USER-country-us-isp-t_mobile_usa-sid-p02-ttl-720m
      
      # a UK profile, any carrier, open all day
      USER-country-gb-sid-p03-ttl-1440m

Three rules: a distinct -sid- for every profile; a -ttl- equal to the time the profile stays open (up to 1440 minutes on mobile); the country taken from the account, with the profile’s time zone and language matching the exit. Leave the carrier out to rotate across all operators of the country; pin it when a phone-like profile should look local.

Multilogin proxy not working: causes and fixes

For every antidetect browser the searches for its proxy errors outnumber the searches for the product. These are the causes we see, in the order to check them.

A test that settles most cases in a minute, outside the browser: curl -x "$PROXY_HOST" -U "USER-country-us-sid-p01-ttl-10m:PASS" https://ipinfo.io/json. If it returns a US carrier address, the proxy is fine and the problem is in the profile’s fields.

Multilogin’s own proxies versus one you bring

Multilogin sells its own proxies inside the app, and for a first test they are the shortest path. The difference with a proxy you bring is control: with QuanticData the session ID, the lifetime, the country and the carrier are yours to set per profile, and you pay per gigabyte across every profile rather than per seat or per port. A complaint that comes up on forums about built-in pools is the exit changing during a session; a fixed -sid- with a -ttl- as long as the working day is the answer to it. Related searches also ask about "Multilogin proxy traffic" and its pricing: on our side traffic is the pack, from $5 for 1 GB, with nothing renewing.

Countries and carriers for Multilogin profiles

The country comes from the account, never from convenience. These are the five asked for most with antidetect profiles, with the carriers the mobile catalog lets you name; every other country has its own page under mobile proxies.

For a comparison of what each network gives you per country, with measured rows: the US, the UK, Germany, Italy, Spain.

What a Multilogin profile costs to run

Per gigabyte, not per port: a profile that moves 100 MB a day costs about $0.23 a day at the 500 GB rate and $0.50 a day at the 1 GB rate, against $8 to $10 a day for a rented port. Packs are one-off, valid 90 days, and bandwidth is shared across every profile on the plan.

For dozens of low-stakes profiles, residential sticky sessions from $1.00/GB ($0.80 at 1,000 GB) go in the same fields; the residential proxies for antidetect browsers page covers that side. How the mobile price compares with 14 other providers: best mobile proxies, by criteria.

What this page does not promise

A proxy supplies the network half of a profile’s identity. It does not make an account "undetectable", it does not change a platform’s rules on multiple accounts, and an antidetect setup used to break those rules is still against them. QuanticData proxies are for keeping legitimately separate accounts separate and consistent. We measured latency, country match and session stickiness on our network (published in the mobile test); we did not measure, and do not claim, any success rate on any platform through Multilogin.