A new IP for one window
Edit that proxy (Edit Proxy) and change its token.
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
A BitBrowser window is only as separate as its IP. Give every window its own home IP, kept for the whole session, so your accounts never meet on one connection. Four fields per window, or one batch for all of them.
Many windows to move? We help on Telegram, every day. To try it: 1 GB for $0.99. Steps from BitBrowser’s own documentation; Ludax values checked against the gateways — November 2026
KEY FACTS
gw.ludaxproxy.com:7777 or Socks5 on gw.ludaxproxy.com:7575 (Residential Premium gw.ludaxproxy.com:8080 and gw.ludaxproxy.com:1080).gw.ludaxproxy.com, Port the number after its colon, Username resi-lx_k3m9q2p7xa, Password your plan password plus options.Host:Port:Username:Password, one line per proxy, under Proxy IP → Proxy IP Management → Batch Add Proxy.-session-shop1-time-1000) keeps one IP for up to 1000 minutes.One Markdown file with everything ChatGPT, Claude, Cursor or Copilot needs to write working Ludax code for BitBrowser: 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/bitbrowser.md and set up my BitBrowser windows with Ludax proxies.
Pick the product, protocol and country, name the window, and copy each value into its field. Your username and password stay in this browser tab and are never sent anywhere.
Fields gives the four values under BitBrowser’s names. Paste and 5 profiles are in the batch format, Host:Port:Username:Password. The window 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 window is on a home connection in the right country, before an account ever sees it.
Open https://api.ludaxproxy.com/whoami in the window 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 window has no -session- token, or shares one with another window. |
tls_profile | The browser BitBrowser’s handshake looks like. | Expected: BitBrowser runs a real browser engine. |
Labels as in BitBrowser’s help center; menus can move a little between versions.
From the generator above, tab Fields.
Go to Browsers and click Add, or edit a window.
Proxy Method: Custom. Direct Mode would use your own connection.
Proxy Type HTTP (7777, 8080) or Socks5 (7575, 1080), then Host, Port, Username, Password.
Click Proxy Detection. For the IP lookup, BitBrowser offers channels such as IP-API and IP123; any of them reads the exit.
Save the window, open it and visit https://api.ludaxproxy.com/whoami: the IP and country the sites see.
https://api.ludaxproxy.com/whoamiOfficial docs: BitBrowser: Http/Https/Socks5/Ssh
For many windows: one line per window, then bind each line to its window.
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-usEach line has its own token, so each window its own IP. Test before you test them all: 30 failed logins in 5 minutes block your IP for 10 minutes.
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-usEdit that proxy (Edit Proxy) and change its token.
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1b-time-1000-country-usType socks5 in the batch, port 7575 (Premium 1080).
gw.ludaxproxy.com:7575:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-usOfficial docs: BitBrowser: proxy IP management
BitBrowser builds the window’s fingerprint with the proxy in mind; check that it did.
In Browser Fingerprint Settings check that the time zone, language and geolocation follow the proxy IP rather than your own computer. BitBrowser’s documentation does not list these settings by name, so look at what the window shows after Proxy Detection.
When the 1000 minutes run out the window gets a new IP; with the city fixed it stays local.
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-de-state-by-city-munich-os-windows (or macos, android, ios) on Residential Premium.
gw.ludaxproxy.com:8080:premi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-us-os-windowsLeave the session out for a new home IP on every connection.
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-country-usPay for what your windows use, not for a subscription. Your own measurement, multiplied out.
Enter the MB one window 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 Detection fails | Usually the login (407): a typo, resi- on a Premium port or the reverse, or a plan with no data left. | Copy the values again; check the plan. See every 407 cause. |
| Fails on a window that used to work | The window still holds an old password (a plan password was reset). | Open the window’s settings, update Password, run Proxy Detection. |
| Every imported proxy fails | The batch carried a wrong password: 30 failed logins in 5 minutes block your IP for 10 minutes. | Fix the lines, wait 10 minutes, test one first. |
| Port and host in one field | BitBrowser wants them apart. | Host gw.ludaxproxy.com, Port the number alone. |
| Two windows show one IP | Their lines share a token. | One token per window (batch import). |
Short answers; the full option list is in proxy authentication.
Host: gw.ludaxproxy.com. Port: 7777 for HTTP or 7575 for SOCKS5 (Residential Premium 8080 and 1080). Username: resi-lx_k3m9q2p7xa (premi- on Premium). Password: your plan password plus options.
Proxy IP, Proxy IP Management, Add Proxy, Batch Add Proxy, and paste Host:Port:Username:Password lines. Then Bind Window ties each proxy to a window.
Give each line its own session token in the password: -session-shop1-time-1000, -session-shop2-time-1000 and so on. The same token keeps the same IP for up to 1000 minutes.
Any of BitBrowser’s channels reads the exit. To see exactly what sites see, open https://api.ludaxproxy.com/whoami inside the window.
No. BitBrowser runs a real browser with its own fingerprint; use the standard ports.
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.