Swap one line for a new IP
Edit the token of that line (shop1 to shop1b) and check the template again.
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1b-time-1000-country-usPick a proxy by the job it has to do
Everyday residential
Location-aware browsing
Advanced identity
Priority pools and ASN control
What teams run on Ludax
Collect
Gather public data at volume
Verify
Confirm what each market sees
Understand
Turn signals into decisions
Popular proxy locations, each with its own guide
Resources
Multilogin keeps your profiles apart inside the browser; the network has to keep them apart too. With Ludax every profile gets its own home IP for the whole session, and one template can hand out 25 of them. Choose Custom, paste, check.
Moving a team over? We help on Telegram, every day. To try it first: 1 GB of Residential, $0.99. Steps from Multilogin X’s own documentation; Ludax values checked against the gateways — November 2026
KEY FACTS
IP:port:login:password; the host can be a name: gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD.gw.ludaxproxy.com:7777, SOCKS5 gw.ludaxproxy.com:7575; Residential Premium gw.ludaxproxy.com:8080 and gw.ludaxproxy.com:1080.One Markdown file with everything ChatGPT, Claude, Cursor or Copilot needs to write working Ludax code for Multilogin X: the connection format, the gateways in force, sessions, errors and tested examples. Copy it into the chat, or paste this prompt:
Read https://ludaxproxy.com/docs/multilogin.md and set up my Multilogin X profiles with Ludax proxies.
Pick the product, protocol and country, name the profile, and copy a line in Multilogin’s IP:port:login:password form. Your username and password stay in this browser tab and are never sent anywhere.
Paste is one proxy (One proxy). 5 profiles is a Proxy list for a template: five lines, five tokens, five IPs. The profile name becomes the session token.
Get one in a minute with the smallest plan, paste it in the field above, and these become your real values.
Ten seconds that tell you whether the profile is on a home connection in the right country, before an account ever sees it.
Open https://api.ludaxproxy.com/whoami in the profile before it goes near an account. It answers with what a site sees:
{
"ip": "203.0.113.24",
"country": "United States",
"type": "residential",
"tls_profile": "Chrome 154",
"latency_ms": 418
}| Field | Good | If not |
|---|---|---|
type | residential: a home connection, not a data centre. | Anything else: do not log in; check the port and the product prefix. |
country | The country in your password. | Another country: the city or region had no free exit; check the spelling of the codes. |
ip | The same on every reload while the session runs. | It changes: the profile has no -session- token, or shares one with another profile. |
tls_profile | The browser Multilogin X’s handshake looks like. | Expected: Multilogin X runs a real browser engine. |
Six steps. Labels as in Multilogin X’s help center; menus can move a little between versions.
From the generator above, tab Paste.
Profiles → Browser → Create, or edit an existing profile, and open its Proxy section.
Pick Custom. Multilogin would use Multilogin’s own traffic, None your own connection.
HTTP (7777, 8080) or SOCKS5 (7575, 1080), One proxy, then paste the line.
Click Check proxy. “Proxy check passed” means Multilogin reached the exit.
Click Create, then Start, and open https://api.ludaxproxy.com/whoami in the profile.
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-ushttps://api.ludaxproxy.com/whoamiOfficial docs: Multilogin X: Proxy section
One template, many profiles, and still one IP per profile: the token on each line does it.
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-us
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop2-time-1000-country-us
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop3-time-1000-country-us
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop4-time-1000-country-us
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop5-time-1000-country-usTemplates come with Multilogin’s larger plans (Pro 20 and up when this was written); the number of templates follows your plan.
Edit the token of that line (shop1 to shop1b) and check the template again.
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1b-time-1000-country-usOfficial docs: Multilogin X: proxy templates
Multilogin’s Quick profiles are for a look at a site, not for an account.
Click Quick on the dashboard, choose Custom under Proxy and paste a line. For a one-off look a rotating line is fine: every connection may leave from a new IP. For anything with a login, use a normal profile with a session token.
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-country-usRegion and city follow the country: -country-de-state-by-city-munich.
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-de-state-by-city-munichOn Residential Premium, -os-windows (or macos, android, ios) picks the device behind the IP; match it to the profile’s system.
gw.ludaxproxy.com:8080:premi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-us-os-windowsProtocol SOCKS5, port 7575 (Premium 1080).
gw.ludaxproxy.com:7575:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-usPay for what your profiles use, not for a subscription. Your own measurement, multiplied out.
Enter the MB one profile uses in a day.
Every account type uses traffic differently, so we do not guess a number for you. Plans run 30 days from activation; buy the size the estimate gives, and top up if it runs short. Every size and price: pricing.
All gateway answers: status codes.
| You see | Why | Fix |
|---|---|---|
| “Proxy check failed” | Most often the login (407): a typo, resi- on a Premium port or the reverse, or a plan with no data left. | Copy the line again; check the plan. See every 407 cause. |
| The profile will not start, or shows a proxy error | Multilogin’s own advice is to run Check proxy first; with Ludax a failure there is the login or the port. | Fix the line until the check passes. If it passes and the profile still will not start, restart the desktop app. |
| A whole template fails at once | Every line carries the same wrong password: 30 failed logins in 5 minutes block your IP for 10 minutes. | Fix the password in the template, wait 10 minutes, check again. |
| SOCKS5 fails at once | SOCKS5 sent to an HTTP port: the gateway closes the connection. | HTTP: 7777 and 8080. SOCKS5: 7575 and 1080. |
| Two profiles show the same IP | Their lines share one session token. | One token per line (templates). |
Short answers; the full option list is in proxy authentication.
In the profile’s Proxy section choose Custom, not Multilogin, pick HTTP or SOCKS5, and enter the proxy as IP:port:login:password. A host name works: gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD.
Yes. A custom template takes a proxy list of up to 25 lines. Give every line its own Ludax session token and each line is its own sticky residential IP.
With Ludax it is almost always the login: a typo, resi- on a Premium port or the reverse, or a plan with no data left. Copy the line again and check one profile before the rest: 30 failed logins in 5 minutes block your IP for 10 minutes.
HTTP on gw.ludaxproxy.com:7777 or SOCKS5 on gw.ludaxproxy.com:7575; on Residential Premium 8080 and 1080. Both carry the login.
No. With Custom, Multilogin uses only your Ludax proxy for that profile.
No: the smallest plan is the test. 1 GB of Residential costs $0.99, with no subscription, and your username stays the same when you buy more.
Stuck? Send a screenshot of the Proxy section on Telegram and we fix it with you. Every plan and price: pricing.