How to add a proxy in MoreLogin

MoreLogin gives you two routes to a proxy: a form with separate boxes for one, and a bulk importer that parses up to a hundred pasted lines.

Which you pick matters more than it usually does, because the importer splits on punctuation that a generated password often contains. This covers both routes, the rules the importer enforces, and how to script the whole thing.

What is MoreLogin?

MoreLogin is an anti-detect browser with a cloud Android product attached. Its own description of the unit of work is direct: "One browser profile can be used as a virtual computer device."

On proxies: "think of a Profile as a separate real computer browser. Each computer needs its own proxy configuration."

It is desktop only. "Morelogin is a PC-based software that needs to be installed and used on the computer. It is not compatible with mobile devices."

MoreLogin proxy features

Two batch templates

Quoted from the Add Proxy page, including the vendor's numbering:

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

These invert each other, which is the pattern across every tool in this category.

A stated default, not a guess

"If the proxy type is not specified, it will default to SOCKS5."

Worth contrasting with GoLogin, which selects HTTP or SOCKS "automatically based on availability". MoreLogin does not probe. Omit the protocol and you get SOCKS5, whatever your provider actually offers, which is a quiet way to produce a proxy that will not connect.

Documented parsing rules

The rest of the list, verbatim:

• ""ProxyHost" and "ProxyPort" are required fields."
• "Only HTTP, HTTPS, SSH, and SOCKS5 proxy types are supported."
• "Each line represents one proxy, with a maximum of 100 proxies added at once."
• "Duplicate proxies will be automatically ignored when added."

Note SOCKS4 is absent from that list and SSH is present, which is the reverse of several competitors.

A rotation field, not a suffix

Where GoLogin, AdsPower and Dolphin Anty all put the rotation URL inside the string in square brackets, MoreLogin gives it its own box, and scopes it: their docs say the refresh URL is used only for mobile proxies.

With a warning attached that applies to all of them: "When multiple profiles use the same mobile proxy, refreshing the IP will change the access address for all these profiles."

The character rule

This is the part to read twice.

"The fields in proxy information should not contain "@" or ":" symbols, as this can cause parsing errors. If such data exists, please use the [Add Proxy - Add Individually] feature."

Both templates use the colon as a field separator and the second uses the at sign as well. A password containing either one moves the boundaries, and the importer splits in the wrong place.

The documented workaround is not to escape it. It is to stop using the importer for that proxy and add it through the individual form, where host, port, account and password are separate boxes and no parsing happens.

This is the same failure we measured from the other direction in Dolphin Anty, where a mis-split string surfaces as a complaint that the port is too long. MoreLogin's advantage is that it warns you first.

Adding a proxy

For one: "Proxy Information: Fill in the proxy host, port, account, and password." Four separate fields, no string to get wrong.

For many, paste one per line in either template, up to a hundred.

Automating it

The local API runs on port 40000 and covers all three drivers.

import requests, hashlib, time
from playwright.sync_api import sync_playwright

BASE = "http://127.0.0.1:40000"

# MoreLogin signs requests with an MD5 of id + token + a millisecond timestamp.
ts = str(int(time.time() * 1000))
sign = hashlib.md5((API_ID + API_KEY + ts).encode()).hexdigest()
H = {"X-Api-Id": API_ID, "Authorization": sign, "X-Nonce-Id": ts,
     "Content-Type": "application/json"}

# 1. Create the proxy. Discrete fields, so nothing can mis-parse a password
#    containing "@" or ":" the way the batch importer would.
proxy = requests.post(f"{BASE}/api/proxyInfo/add", headers=H, json={
    "proxyIp": "gate.example.com",
    "proxyPort": 7000,
    "proxyProvider": 2,
    "proxyType": 1,
    "username": "user-session-abc123",
    "password": "secret",
    "proxyName": "gate_{{random}}",
}).json()

# 2. Start a profile and read back the debug port.
r = requests.post(f"{BASE}/api/env/start", headers=H,
                  json={"envId": PROFILE_ID}).json()
debug_port = r["data"]["debugPort"]

# 3. Attach.
with sync_playwright() as pw:
    browser = pw.chromium.connect_over_cdp(f"http://127.0.0.1:{debug_port}")
    page = browser.contexts[0].pages[0]
    page.goto("https://example.com")
    browser.close()

requests.post(f"{BASE}/api/env/close", headers=H, json={"envId": PROFILE_ID})

Read the port rather than trusting it. MoreLogin's own instruction is that the app is authoritative: "The API endpoint for the current version is: http://127.0.0.1:40000. The port number is subject to the address shown in Settings." Their two headless examples use different ports again, 51473 and 40008, both set with an --api-port argument:

# macOS
"/Applications/MoreLogin.app/Contents/MacOS/MoreLogin" --headless=true --port=40008
# Windows
start /WAIT MoreLogin.exe --headless=true --port=51473

Three proxy errors have codes and literal text, and all three are about fields you control:

14021  Proxy host cannot be empty, please provide the proxy host information.
14022  Proxy port cannot be empty, please provide the proxy port information.
14024  Proxy does not exist, please provide the proxy information.

The port is bounded as you would expect: "only numbers from 1-65535 are supported". The rate limit is 120 requests per minute per endpoint, and the local API is localhost only.

This follows MoreLogin's documented endpoints and signing scheme rather than a run of ours. Unusually, it is the one tool here where you could check it for nothing, since the free plan includes the Local API.

What the free tier includes

Two permanent profiles, no card. "Free Forever | Profiles 2 | Users 2".

The part worth knowing is what is inside it. MoreLogin's free plan feature list ends with "Local API" and "Browser automation with Selenium or Puppeteer".

Every comparable tool we have read excludes exactly that. GoLogin puts API access on its not-available list. AdsPower grants the API to paid versions only. Incogniton excludes automation from the free tier and from its entry paid tier as well.

If you want to test whether a proxy works under programmatic control before paying anything, this is currently the only one of the group where you can.

Whichever tool you settle on, the proxy behind it is the recurring cost, and per-gigabyte prices vary far more between providers than these applications vary between each other. What each charges, with the date it was read, is on the provider table.

Limitations

A hundred proxies per batch, and the character rule above.

Field lengths are capped: 200 characters for a username, 100 for a password, 600 for a proxy name.

No IP allowlisting. We searched the whole Network Setting collection, the help-centre API docs, the developer guide and both downloadable OpenAPI specifications for whitelist, allowlist, IP authentication and authorised IP. None of those terms appears anywhere. Username and password are the only documented method.

What the documentation does not say

• A single filled-in batch line. The Add Proxy page promises an example twice and both times delivers a screenshot rather than text. The abstract grammar is documented; a real line is not.
• Whether SOCKS4 works at all. It is absent from the supported list, which is not the same as being documented as unsupported.
• What "proxy detection failed" means, despite being one of the top completions on this tool's name. No vendor page carries that string.

The individual form removes the parsing risk but not the provider-side one: the session token belongs in the account field at some providers and the password at others. What each states is on its provider page, dated.

Conclusion

Use the individual form when your credentials contain punctuation, because MoreLogin tells you to and the failure it prevents is silent. Set the protocol explicitly rather than inheriting SOCKS5. And if you are choosing between these tools partly on whether you can script against a free account, this is the one where you can.