Setting Up HTTP Proxy on Android Emulator: The Easy Way (2025 Guide)

Debugging network requests from an Android Emulator is surprisingly difficult. Should you change the settings in the Extended Controls? Or inside the Android Wi-Fi menu? Or pass a flag to the command line?

In this guide, we'll cover the two most reliable methods to route emulator traffic through a proxy tool like Debuggo or Charles.

Method 1: Extended Controls (Easiest)

This is the recommended method for most users. It sets the proxy globally for the emulator instance.

1. Launch your emulator from Android Studio.
2. Click the three dots (...) in the emulator toolbar to open Extended Controls.
3. Go to the Settings tab on the left sidebar.
4. Select the Proxy tab at the top.
5. Uncheck "Use Android Studio HTTP proxy settings".
6. Select Manual proxy configuration.
7. Enter your proxy details:
   • Host name: chaos-proxy.debuggo.app
   • Port number: 11997
   • Auth: Enter your username and password. (Don't have credentials? Get them for free here)
8. Click Apply. You should see "Success" at the bottom.
   ▶▼View Screenshot

   

Method 2: Command Line (For CI/CD)

If you are starting the emulator from a script or pipeline, you can pass the proxy as an argument.

Crucial Step: Installing the Certificate

Even with the proxy set, you won't see HTTPS traffic (it will fail with SSL errors) until you install the CA certificate.

1. Open Chrome inside the Emulator.
2. Go to http://mitm.it (or download the PEM file from your Debuggo dashboard).
3. Download the certificate.
4. Go to Android Settings → Security → Encryption & Credentials → Install a certificate → CA certificate.
5. Select the downloaded file and confirm.

▶▼View Installation Screenshots (Step-by-Step)

1. Search Encryption

2. Encryption & Credentials

3. Install a certificate

4. CA certificate

5. Confirm

Why use a Cloud Proxy for Emulators?

Using `localhost` (10.0.2.2) is often flaky. By using a cloud proxy like Debuggo, your emulator connects to the internet just like a real device would on a 4G network. Plus, you can simulate 500 Errors and High Latency to see if your app crashes.