Setting up proxy for Android emulators (Nox, BlueStacks)

Setting Up Proxies for Android Emulators (Nox, BlueStacks)

Introduction

Android emulators (Nox, BlueStacks, LDPlayer) are used for multi-accounting in mobile applications. Each emulator requires a unique proxy to simulate separate devices.

Basic Setup

Nox Player

1. Open Nox settings (gear icon)
2. Go to "Network" → "Settings"
3. In Android Wi-Fi settings:
   - Press and hold the Wi-Fi network
   - "Modify network" → Show advanced options
   - Proxy: Manual
   - Proxy hostname: proxy_ip
   - Proxy port: port
4. Or via ADB: adb shell settings put global http_proxy proxy_ip:port

BlueStacks

1. Android settings in BlueStacks
2. Wi-Fi → Modify network → Manual proxy
3. Or via ADB commands

LDPlayer

Similarly, via Android Wi-Fi settings or ADB.

For each emulator instance, configure its own proxy for multi-accounting.

Advanced Configuration

Environment Variables

Most tools support standard environment variables for proxies:
- HTTP_PROXY / http_proxy — proxy for HTTP requests
- HTTPS_PROXY / https_proxy — proxy for HTTPS requests
- NO_PROXY / no_proxy — list of exceptions (addresses that bypass the proxy)
- ALL_PROXY / all_proxy — proxy for all protocols

SSL and Self-Signed Certificates

Corporate proxies often use their own SSL certificates. To work through them, you need to:
1. Obtain the proxy's CA certificate from the administrator
2. Add it to the system certificate store
3. Or disable SSL verification (for testing only)

Authentication

Two main authentication methods are supported:

By username and password — standard HTTP Basic authentication. Credentials are sent with each request. URL format: http://user:pass@proxy_ip:port

By IP address (whitelist) — your IP is added to a whitelist. No credentials need to be sent.

Verification

After setup, verify:
1. Perform a test request through the proxy
2. Ensure that the IP has changed
3. Check the connection speed
4. Ensure there are no DNS leaks

Troubleshooting

Proxy Not Connecting

• Check the correctness of the address and port
• Ensure that the firewall is not blocking the connection
• Check the proxy's availability from your network

SSL Errors

• For corporate proxies, add the CA certificate
• For testing, temporarily disable SSL verification
• Update SSL libraries to the latest version

Authentication Errors

• Check the username and password
• Ensure the correct credentials format
• Try encoding special characters in the password (URL encoding)

Best Practices

1. Use environment variables — for flexibility and security
2. Do not hardcode credentials — use environment variables or configuration files
3. Configure exclusions — do not proxy localhost and internal addresses
4. Document settings — in the project README or team wiki
5. Test after changes — any configuration change requires verification

Conclusion

Correct proxy setup ensures stable tool operation and connection security. Follow the recommendations in this guide and always verify functionality after configuration.