How to Set Up a Proxy in LDPlayer, Including Multi-Instance
By the ProxyV4 Engineering Team · Updated:
To set up a proxy in LDPlayer, configure it inside each instance's Android system: in the Wi-Fi network's proxy fields, with an ADB global proxy command, or in a proxy helper app. ProxyV4 proxies log in with a username and password, and Android's built-in proxy fields have no login box, so for credential login the helper app (or a desktop tool such as Proxifier) is the route that works. If your PC has a fixed public IP, there is a simpler option: add that IP to the order's IP whitelist and type only the host and port into the Wi-Fi or ADB proxy setting. Each instance can hold its own IP, which keeps test, client and team environments apart.
How LDPlayer proxy setup works
Every LDPlayer instance is a separate Android virtual machine that shares your computer's internet connection. Unless you set a proxy, every instance leaves through your home or office IP. The proxy has to be set inside each instance, or on the Windows side for the LDPlayer process as a whole.
There are four places to put it, and the deciding question is whether your proxy needs a login. The general limits of Android's own proxy settings are covered in the Android proxy setup guide; the table below is the LDPlayer-specific summary. In the Wi-Fi route, the fields sit under the active Wi-Fi network's advanced options (labels vary by version).
| Route | Username and password | What it covers | Per instance? |
|---|---|---|---|
| Wi-Fi proxy fields in Android Settings | No login fields | Apps that honor the system proxy, mainly browsers | Yes |
ADB global proxy (settings put global http_proxy) | No login fields | Same as Wi-Fi: apps that honor the system proxy | Yes |
| Proxy helper app inside the instance | Yes, if the app supports it | Most app traffic, via Android's VPN interface | Yes |
| Proxifier on Windows | Yes | The LDPlayer processes it matches | No, one rule covers instances that share a process |
LDPlayer proxy authentication: use a helper app
ProxyV4 proxies use username and password login by default, delivered as one ip:port:user:pass line. Alternatively, on the order's page in the dashboard you can add up to three public IPv4 addresses under IP Whitelist; connections from those addresses need no login, so the Wi-Fi and ADB fields work with just IP:PORT. LDPlayer connects from your PC, so the address to add is the PC's public IP (check it with the my IP tool); if that IP changes, update the list. The Android Wi-Fi proxy form and the ADB global proxy setting accept only a host and a port. If you put an authenticated proxy there, the proxy answers with 407 Proxy Authentication Required or apps simply show no connection, no matter how carefully the address is typed.
The route that carries a login is a proxy helper app installed inside the instance. These apps create a local VPN through Android's VpnService and forward traffic to your proxy with the credentials you enter. Android shows a connection request the first time the app starts its VPN; accept it, and a key icon appears in the status bar.
Choosing a helper app
Specific apps come and go from the Play Store, and some once-popular ones are no longer maintained, so check what is currently available rather than relying on an old list. Look for an app that explicitly supports username and password for SOCKS5 or HTTP, is still updated, and comes from a developer you trust, because it sees all of the instance's traffic.
If your order is set to both HTTP and SOCKS5 on the same port, either protocol works in the app. SOCKS5 usually captures more app traffic. Whether UDP is carried depends on the app and the proxy; if your game needs UDP, ask ProxyV4 support through a ticket before you order.
Desktop alternative: Proxifier
Proxifier on Windows can send LDPlayer's own processes through an authenticated proxy without touching Android at all. The catch is that its rules match processes, and instances started from the same LDPlayer installation run under the same process names, so one rule gives all of them the same IP. Use it when one IP for the whole emulator is what you want; the Proxifier setup guide covers adding the server and the rule. Proxifier's connection log shows which LDPlayer process actually opens the connections, and that is the name to put in the rule.
LDPlayer ADB proxy commands
ADB is useful when you script many instances or want a quick host-and-port proxy, for example a local relay you run yourself that adds the login upstream. LDPlayer ships an adb.exe in its installation folder. Run adb devices first and use the serial it prints for each running instance, since the numbering depends on how many instances are open.
Set and clear the global proxy
# List running instances and their serials
adb devices
# Point one instance at a host:port proxy (no login possible here)
adb -s emulator-5554 shell settings put global http_proxy IP:PORT
# Read the value back
adb -s emulator-5554 shell settings get global http_proxy
# Remove it again
adb -s emulator-5554 shell settings put global http_proxy :0
adb -s emulator-5554 shell settings delete global http_proxyA wrong value leaves the instance without internet, so keep the clearing commands at hand. Some builds need an instance restart before the cleared value takes effect.
Per instance with ldconsole
Recent LDPlayer versions also include ldconsole.exe, which addresses instances by their index in the multi-instance manager instead of by ADB serial. A command of the form ldconsole.exe adb --index 0 --command "shell settings put global http_proxy IP:PORT" sets the proxy on the first instance. The syntax has changed between versions, so run ldconsole.exe help in your install folder before you build a script around it.
LDPlayer multi-instance proxy: one IP per instance
The LDMultiPlayer manager starts, clones and names instances. For one IP per instance, install the helper app in each instance and give each its own proxy line. When you clone an instance, the clone copies the app and its saved profile, so it starts with the original's proxy; change the line in the clone before you open any app.
Name each instance after its job and its IP, for example qa-jp-01 or client-b-us, and keep a sheet that maps instance name to proxy line. That record is what lets a teammate fix an instance without guessing which address it should use.
Separate IPs keep test, client and team environments apart, and they let you check how an app behaves from a given country. They do not change what a game allows. Follow each game's and platform's rules on multiple accounts; the online games proxy page covers what a game server sees and how to pick a location near it.
Where a ProxyV4 IP fits an LDPlayer setup
ProxyV4 sells private datacenter IPv4 in seven countries (United States, Vietnam, Japan, South Korea, Singapore, United Kingdom, Hong Kong) and static ISP IPs registered to consumer internet providers in the United States and Vietnam. Each IP has one tenant for the whole term, traffic is unmetered, and renewing before expiry keeps the same address, so an instance keeps its IP from one term to the next.
Every proxy supports HTTP(S) and SOCKS5 with username and password, or IP whitelist login from up to three of your own IPv4 addresses. On the order's page in the dashboard you choose HTTP only, SOCKS5 only, or both on the same port; switching can move the proxy to a new port, so copy the line again afterwards.
It does not fit everywhere. If an app accepts only mobile carrier IPs, ProxyV4 has no mobile proxies. If you need a new IP on every request, rotating proxies are on a waitlist and not on sale. If a game's traffic depends on UDP, ask support before ordering rather than assuming it will pass. Check the per-IP rates on the pricing page, order one IP, and test it in a single instance before you scale.
Check the exit IP and fix common failures
Open the browser inside the instance and load the my IP tool. You should see the proxy's address and country, not your own. A browser check confirms the helper app or system proxy is active; for a game that never shows its IP, the login history inside the account is the next best check.
- Authenticated proxy set via ADB: the system proxy has no login fields, so the proxy returns 407 or apps show no connection. Clear the ADB value and use a helper app; the 407 error guide explains the response.
- Browser shows the proxy, the app does not: the app ignores the system proxy. A VpnService-based helper app is the route that captures its traffic.
- Protocol mismatch: a SOCKS5 client pointed at a port set to HTTP only stalls. Match the app's protocol to the order's mode.
- Port changed: after switching the order between HTTP and SOCKS5 modes, copy the full
ip:port:user:passline again. - Instance offline after an ADB test: an old value is still set. Run the clearing commands above and restart the instance.
Step by step
- 1
Copy the proxy line
Copy the ip:port:user:pass line from the order's page and note whether the order is in HTTP, SOCKS5 or both mode.
- 2
Install a helper app in the instance
Inside the LDPlayer instance, install a currently maintained proxy app that supports username and password for HTTP or SOCKS5.
- 3
Enter the proxy and start it
Create a profile in the app with the host, port, username, password and matching protocol, start it, and accept Android's VPN connection request.
- 4
Verify the exit IP
Open the browser in the instance, load the my IP tool and confirm it shows the proxy's address and country.
- 5
Repeat per instance
Give each instance its own line, update clones before opening apps, and record which instance uses which IP.
Frequently asked questions
Can I enter a proxy username and password in LDPlayer's Wi-Fi settings?
Not in the built-in Wi-Fi settings, which have no login box. Either add your PC's public IP to the order's IP Whitelist and enter only host and port there, or keep username and password and use a helper app inside the instance or Proxifier on Windows.
Does the ADB global proxy cover game apps?
Only apps that honor Android's system proxy use it. Many games open their own connections and ignore it, which is why a VPN-based helper app is the more complete route.
Can several LDPlayer instances share one proxy?
Yes, and they will all show the same IP. Use one line per instance when each environment needs its own address.
Will an instance keep the same IP after I renew?
Yes. Renewing a ProxyV4 proxy before it expires keeps the same address, and you can renew all proxies or only a selection.
What if the proxy does not work in LDPlayer?
Check the protocol mode and the line first. A proxy that fails for a technical reason, such as not connecting or showing the wrong location, is covered by the refund policy, credited to your account balance.
One static IP per LDPlayer instance
Private IPv4 and static ISP proxies with HTTP(S) and SOCKS5 with username and password or IP whitelist login, unmetered traffic and the same IP on renewal. Order one IP and test it in an instance first.
Get a private IP