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

To add a proxy in MoreLogin, open Advanced create and under Proxy choose New proxy. Set the type that matches the port, put the host and port in Proxy server, the whole username in Proxy account and the password, click proxy detection and confirm. Give every profile its own sticky session. Below: each field, bulk setup and a fix for each error.

MoreLogin keeps every browser profile apart: its own cookies, its own fingerprint and, once you add one, its own proxy. The proxy decides which IP address and which country the sites see. Unlike tools that take the proxy as one pasted line, MoreLogin's profile window asks for it field by field, so the usual mistakes are a type that does not match the port and a username cut on the way. The field names below are the ones in MoreLogin's own help center and current client; the values come from the QuanticData endpoint generator.

What you need before you start

• MoreLogin installed, with an account. Browser profiles and cloud phone profiles both take a proxy; the bulk tools are covered further down.
• A proxy plan. Residential Premium, ISP or mobile: all three work in MoreLogin. 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, under Connection details.

The MoreLogin proxy fields, one by one

MoreLogin field	What goes in	QuanticData value
Proxy Option	New proxy for a proxy typed here, Use existing proxy for one saved before	New proxy
Proxy type	The protocol of the port you use; MoreLogin lists HTTP, HTTPS, Socks5 and SSH	HTTP for port 8080, Socks5 for port 1080
IP query channel	The database MoreLogin uses to show the proxy's location: IP2Location, MaxMind, DB-IP or IP-API	Leave IP2Location; switch only if the location shown looks wrong
Proxy server	Host in the first part, port after the colon	residentialpremium.quantumproxies.io and 8080
Proxy account	The username	The whole string, for example USER-country-es-sid-p01-ttl-60m
Proxy password	The password	The plan's password
Refresh URL	A link that changes the IP of some mobile proxies	Leave it empty: a new session ID in the username gives a new IP

The username carries the targeting: -country-es picks the exit country, -sid-p01 names the session and -ttl-60m keeps it for 60 minutes. Copy it whole into Proxy account. 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.

Step by step: add a proxy to a MoreLogin profile

1. Generate the proxy. In the QuanticData dashboard open My proxies, then your plan. In the Endpoint generator choose the Country (Spain in this example, plus 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, and choose the Protocol.
2. Open Connection details. It shows the same proxy as four values with a copy button each: Host, Port, Username (with current targeting) and Password. These are the four MoreLogin fields.
3. Open the profile's proxy settings in MoreLogin. For a new profile: Profiles, + New profile, Browser profile, Advanced create, then the Proxy section. For an existing one: Edit Proxy in the Proxy column of the profiles list.
4. Choose New proxy under Proxy Option.
5. Pick the Proxy type that matches the port: HTTP for 8080, Socks5 for 1080.
6. Fill Proxy server, Proxy account and Proxy password with Host and Port, Username and Password from Connection details.
7. Leave Refresh URL empty. QuanticData lines change IP through the session ID, not through a link.
8. Click proxy detection. MoreLogin answers "Pass detection!" with the export IP and the location. The country has to match the -country- in the username.
9. Click Confirm, then Start the profile in the profiles list. By default MoreLogin opens its detection page when a profile starts, a second chance to see the IP and location.

If the location MoreLogin shows is a neighbouring city or region, the proxy is still fine: the IP query channels are different databases and can disagree slightly. MoreLogin's own advice is to switch the IP query channel when the result does not match. Recent MoreLogin versions also add IPv4 and IPv6 options to the proxy section; QuanticData gateways answered on IPv4 in our check.

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 suits scraping and breaks 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 nothing has to change in MoreLogin once the profile is saved.

# profile 1: Spain, one session for a working day
Proxy server   residentialpremium.quantumproxies.io : 8080
Proxy account  USER-country-es-sid-p01-ttl-480m

# profile 2: same plan, its own session (never reuse p01)
Proxy account  USER-country-es-sid-p02-ttl-480m

# profile 3: Germany, open all day
Proxy account  USER-country-de-sid-p03-ttl-1440m

• A different session ID in every profile. Two profiles on the same username share one IP, which is what an antidetect browser is there to avoid. MoreLogin's own help center makes the same point about mobile proxies: refresh one that several profiles share and all of them change address at once.
• 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 read that as a new login location.
• The country in the username. Without -country- the exit can be anywhere, and the profile no longer matches the country it was set up for.

Adding many proxies at once: Batch add

MoreLogin keeps a proxy library on its Proxy screen, under Self-owned proxy. Add proxy, then Batch add, takes a list, one proxy per line, up to 100 at a time, in either of two layouts:

ProxyType://ProxyHost:ProxyPort:ProxyAccount:ProxyPassword
ProxyType://ProxyAccount:ProxyPassword@ProxyHost:ProxyPort

The second layout is exactly what the QuanticData generator gives with Output format set to http://user:pass@host:port:

http://USER-country-es-sid-p01-ttl-60m:PASS@residentialpremium.quantumproxies.io:8080
http://USER-country-es-sid-p02-ttl-60m:PASS@residentialpremium.quantumproxies.io:8080
http://USER-country-es-sid-p03-ttl-60m:PASS@residentialpremium.quantumproxies.io:8080

One rule decides whether the batch works: a line with no type in front is read as SOCKS5. A plain host:port:user:pass line on port 8080 therefore goes in as SOCKS5 on an HTTP port and fails the check. Keep http:// in front of lines on 8080, or set the Protocol Type menu next to the box instead of automatic identification; lines on port 1080 work either way.

1. Make the lines. In the generator set Session to Sticky, the Quantity you need (10 by default) and Output format http://user:pass@host:port, then Generate and Copy all or Download.
2. Paste them. In MoreLogin open Proxy, Add proxy, Batch add, and paste the list. MoreLogin splits each line into type, host, port, account and password in the table below; duplicates are skipped.
3. Check them. Click proxy detection: each line gets its result in the Test results column. Then Confirm.
4. Assign them. For one profile: Edit Proxy, then Use existing proxy (Saved Proxies in some versions of the help center). For many: select the profiles in the list and use Modify Proxy in the action bar above it.

MoreLogin's notes add one more rule: the fields must not contain "@" or ":", because those characters split the line. A proxy with either one in its password goes in through Add proxy, Add individually, the same form as in a profile.

Which QuanticData proxy for which MoreLogin profile

Proxy type	In MoreLogin	Good for
Residential Premium	One sticky username per profile; country, region, city or ISP in the username; HTTP 8080 or Socks5 1080; 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; one IP per profile	Long-lived accounts that should keep the same address
Mobile	Host mobile.quantumproxies.io; Global, USA, EU or Asia gateway; HTTP 8080 or Socks5 1080; IP whitelist available	Phone-first platforms and cloud phone profiles
Datacenter	The same four fields	Testing and low-risk profiles where speed matters more than the type of IP

Residential Premium in MoreLogin

Everything above is Residential Premium: one host, port 8080 for HTTP or 1080 for Socks5, and the targeting and the session inside the username. For a new IP on a profile, change the session ID, for example -sid-p01 to -sid-p01b, and save: the Refresh URL field stays empty. For why each profile needs its own address, see residential proxies for antidetect browsers; the plans are on the page for QuanticData residential proxies.

ISP proxies in MoreLogin

An ISP plan gives fixed addresses, listed on the plan's page under Assigned IPs. Choose the protocol and the format IP:Port:Username:Password, then give each profile one IP: the IP and the port go in Proxy server, the username and password in their fields, Proxy type to match the protocol. For Batch add, put http:// or socks5:// in front of each line to match, since a line with no type is read as SOCKS5. ISP addresses are static by design, so there is nothing to refresh. More on the plans: ISP proxies.

Mobile proxies and MoreLogin cloud phones

Mobile plans use the host mobile.quantumproxies.io with a gateway to choose, Global, USA, EU or Asia, and the same two ports: HTTP 8080, Socks5 1080. Set Session to Sticky in the generator and copy the values from Connection details, exactly as above. A new IP is a new session ID; leave Refresh URL empty here too.

MoreLogin's cloud phones, its Android profiles, take a proxy in their own Network setup section: New proxy or Use existing proxy, the same fields, and Network detection as the check. MoreLogin's cloud phone guide asks for a usable SOCKS5 proxy to start the phone, so use Socks5 on port 1080 there. Mobile plans also offer IP whitelist authentication, where your IP is registered and no login is sent. For the wider picture see mobile proxies for antidetect browsers and the plans for mobile proxies.

MoreLogin proxy detection failed: errors and fixes

A proxy that does not pass the check shows Detect Failed in the Proxy status column of the Proxy screen; in the profiles list, Bulk detection marks it in magenta instead of green; in the profile window, proxy detection does not return "Pass detection!". These are the causes behind it, in the order to check.

What you see	Usual cause	Fix
Detect Failed on lines added with Batch add	The lines had no type, so MoreLogin read them as SOCKS5 on an HTTP port	Keep http:// in front of lines on 8080, or set Protocol Type
Detect Failed on a proxy typed in a profile	The type does not match the port: HTTP on 1080 or Socks5 on 8080	HTTP with 8080, Socks5 with 1080
The same error, with the right type	The username was cut, a space came with the paste, or the password is wrong	Copy Username and Password again from Connection details
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 in the location	No -country- in the username, or Worldwide chosen in the generator	Generate the username with a country
Right country, slightly different city	The IP query channel's database places the IP differently	Switch the IP query channel; the proxy itself is fine
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

After a fix, click Edit on the proxy, save, and run batch detection proxy on the selected lines to see the new status. One test outside MoreLogin 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-es-sid-test-ttl-10m:PASS" https://ipinfo.io/json

If the 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 MoreLogin

Both work for browsing, and every QuanticData network offers both. HTTP on port 8080 is the simpler choice for browser profiles: HTTPS sites still load through it, because the browser tunnels them. Socks5 on port 1080 passes any kind of connection, not only web pages, and it is the type MoreLogin assumes when a Batch add line has no prefix and the one its cloud phone guide asks for; 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. Using several antidetect browsers? See the same setup 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.