Skip to main content
[ DOCS / BITBROWSER ]

BitBrowser proxy setup: the four fields, and batch import

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.

  • A home IP per windowits own session token
  • Batch for many windowsone line each
  • Checked before loginwhoami shows the IP type

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

  • In a window choose Proxy Method Custom and a Proxy Type; for Ludax HTTP on gw.ludaxproxy.com:7777 or Socks5 on gw.ludaxproxy.com:7575 (Residential Premium gw.ludaxproxy.com:8080 and gw.ludaxproxy.com:1080).
  • The fields: Host gw.ludaxproxy.com, Port the number after its colon, Username resi-lx_k3m9q2p7xa, Password your plan password plus options.
  • Batch import reads Host:Port:Username:Password, one line per proxy, under Proxy IP → Proxy IP Management → Batch Add Proxy.
  • One session token per window (-session-shop1-time-1000) keeps one IP for up to 1000 minutes.
  • Proxy Detection failing with the right host is almost always the login (407). 30 failed logins in 5 minutes block your IP for 10 minutes.

Using an AI assistant? Give it this guide

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.

[ 01 / YOUR VALUES ]

BitBrowser Host, Port, Username and Password

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.

Product

Real home IPs for everyday scraping. Gateway: gw.ludaxproxy.com:7777

Protocol
IP address
bitbrowser-fields.txt

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.

No username yet?

Get one in a minute with the smallest plan, paste it in the field above, and these become your real values.

Get 1 GB — $0.99
[ 02 / BEFORE YOU LOG IN ]

Check the window’s IP before you log in

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:

whoami (your values will differ)
{
  "ip": "203.0.113.24",
  "country": "United States",
  "type": "residential",
  "tls_profile": "Chrome 154",
  "latency_ms": 418
}
READ IT IN TEN SECONDS
FieldGoodIf not
typeresidential: a home connection, not a data centre.Anything else: do not log in; check the port and the product prefix.
countryThe country in your password.Another country: the city or region had no free exit; check the spelling of the codes.
ipThe same on every reload while the session runs.It changes: the window has no -session- token, or shares one with another window.
tls_profileThe browser BitBrowser’s handshake looks like.Expected: BitBrowser runs a real browser engine.
  • Prepaid, no subscriptionyou pay for GB, plans run 30 days
  • Crypto checkoutBTC, USDT, ETH and more
  • Bodies never storedwhat you send is not kept
[ 03 / ONE WINDOW ]

Add a Ludax proxy to a BitBrowser window

Labels as in BitBrowser’s help center; menus can move a little between versions.

  1. Get your four values

    From the generator above, tab Fields.

  2. Add a window

    Go to Browsers and click Add, or edit a window.

  3. Choose Custom

    Proxy Method: Custom. Direct Mode would use your own connection.

  4. Pick the type and fill the fields

    Proxy Type HTTP (7777, 8080) or Socks5 (7575, 1080), then Host, Port, Username, Password.

  5. Proxy Detection

    Click Proxy Detection. For the IP lookup, BitBrowser offers channels such as IP-API and IP123; any of them reads the exit.

  6. Save and open

    Save the window, open it and visit https://api.ludaxproxy.com/whoami: the IP and country the sites see.

check_ip.txt
https://api.ludaxproxy.com/whoami

Official docs: BitBrowser: Http/Https/Socks5/Ssh

[ 04 / BATCH IMPORT ]

Batch-import Ludax proxies into BitBrowser

For many windows: one line per window, then bind each line to its window.

  1. Left menu Proxy IP, tab Proxy IP Management.
  2. Add Proxy → Batch Add Proxy, type http (or socks5), and paste the lines.
  3. Batch Proxy Testing on one line first, then the rest.
  4. Bind Window ties each proxy to its window.
paste_5_profiles.txt
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-us

Each 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.

paste_residential.txt
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-us
01

A new IP for one window

Edit that proxy (Edit Proxy) and change its token.

paste_new_ip.txt
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1b-time-1000-country-us
02

SOCKS5 lines

Type socks5 in the batch, port 7575 (Premium 1080).

paste_socks5.txt
gw.ludaxproxy.com:7575:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-us

Official docs: BitBrowser: proxy IP management

[ 05 / LOOK LOCAL ]

Make the BitBrowser window match its IP

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.

01

Pin the city

When the 1000 minutes run out the window gets a new IP; with the city fixed it stays local.

paste_city.txt
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-de-state-by-city-munich
02

Premium: a Windows exit for a Windows window

-os-windows (or macos, android, ios) on Residential Premium.

paste_premium_windows.txt
gw.ludaxproxy.com:8080:premi-lx_k3m9q2p7xa:YOUR_PASSWORD-session-shop1-time-1000-country-us-os-windows
03

Windows without an account

Leave the session out for a new home IP on every connection.

paste_rotating.txt
gw.ludaxproxy.com:7777:resi-lx_k3m9q2p7xa:YOUR_PASSWORD-country-us
[ 06 / HOW MUCH ]

Work out the GB for your BitBrowser windows

Pay for what your windows use, not for a subscription. Your own measurement, multiplied out.

Enter the MB one window uses in a day.

  1. Work one window for a normal day through Ludax.
  2. Read how much the plan used in your Ludax dashboard.
  3. Put that number here; the rest is multiplication.

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.

[ 07 / TROUBLESHOOTING ]

BitBrowser Proxy Detection failed: causes and fixes

All gateway answers: status codes.

SYMPTOM, CAUSE, FIX
You seeWhyFix
Proxy Detection failsUsually 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 workThe window still holds an old password (a plan password was reset).Open the window’s settings, update Password, run Proxy Detection.
Every imported proxy failsThe 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 fieldBitBrowser wants them apart.Host gw.ludaxproxy.com, Port the number alone.
Two windows show one IPTheir lines share a token.One token per window (batch import).
[ 08 / FAQ ]

BitBrowser proxy FAQ

Short answers; the full option list is in proxy authentication.

01What do I put in BitBrowser’s Host and Port fields?

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.

02How do I import many proxies into BitBrowser?

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.

03How do I give each BitBrowser window its own IP?

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.

04Which IP query channel should I pick?

Any of BitBrowser’s channels reads the exit. To see exactly what sites see, open https://api.ludaxproxy.com/whoami inside the window.

05Does BitBrowser need the Residential TLS ports?

No. BitBrowser runs a real browser with its own fingerprint; use the standard ports.

06Is there a free trial?

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.

[ START NOW ]

Fill your first BitBrowser window with Ludax

  1. Pick a plan. 1 GB, no subscription.
  2. Copy the four values from the generator above.
  3. Fill the fields and run Proxy Detection.

Stuck? Send a screenshot of the proxy fields on Telegram and we fix it with you. Every plan and price: pricing.