Android Studio Emulator Network Not Working | Fix Fast

You hit Run, your app launches, and then each request times out. The emulator says Wi-Fi is connected, yet the browser can’t load a page. Or your API calls work on a phone but fail on the AVD. It’s frustrating because the failure looks random right away.

This checklist follows the same order I use when the emulator loses data on a real dev box. Start inside the emulator, then move out to ADB, proxy settings, DNS, and host-machine blockers. You’ll get a working AVD, then you can keep coding instead of poking at settings all night.

What Emulator Network Breaks Usually Mean

“No internet” can mean a few different things. The emulator may have an IP but no DNS. It may reach the internet but not your local server. Or your host machine may be forcing a proxy that the emulator can’t use.

The fastest path is to match what you see to the layer that’s failing, then fix that layer once.

Now let’s get practical and knock out the fixes that clear most cases in minutes.

Android Studio Emulator Network Not Working After An Update

Updates can change two moving parts at once: the Emulator app and the Android system image inside your AVD. If the AVD lost internet right after updating Android Studio, the Emulator, or a system image, start with clean boot steps before you touch your app code.

1. Cold Boot The AVD — In Device Manager, open the AVD menu and choose Cold Boot Now to start without a saved snapshot.
2. Wipe AVD Data — If Cold Boot didn’t clear it, use Wipe Data to reset user data and cached network state.
3. Update Emulator And Platform Tools — In SDK Manager, update the Emulator and Android SDK Platform-Tools, then restart Android Studio.
4. Try A Fresh Test AVD — Create a new AVD using a current system image. If the new one works, your old AVD state is the culprit.

If Cold Boot fixes it, the issue was a snapshot bringing back a bad network state. If only a fresh AVD works, migrate to it and delete the broken one.

Fast Fixes That Clear Most Network Issues

These steps are quick, safe, and worth doing in order. After each step, open the emulator browser and try loading a simple site. If the browser loads but your app still fails, jump to the API section later.

• Toggle Airplane Mode — Turn Airplane mode on, wait a few seconds, then turn it off to force a reattach.
• Restart Wi-Fi — Turn Wi-Fi off and back on inside the emulator settings to clear a stuck Wi-Fi state.
• Restart The Emulator — Close the emulator, then start it again from Device Manager so the virtual router stack restarts.
• Restart ADB — Run adb kill-server, then adb start-server, then relaunch the emulator.
• Fix Device Time — Enable automatic date/time. Bad time can break HTTPS and look like a dead connection.

If nothing loads at all, DNS and proxy are the usual next stops. If some sites load and others don’t, proxy rules or certificate checks may be involved.

Two Fast Tests Before You Change Anything Else

Before you change proxy settings or rebuild an AVD, run two quick checks that tell you which layer is failing. They don’t require extra apps, and they separate “no routing” from “DNS or TLS.”

1. Load An IP In The Browser — In the emulator browser, try https://1.1.1.1. If it opens but domains fail, DNS is the issue.
2. Ping A Public IP — Run adb shell ping -c 1 8.8.8.8. A fail points to routing or firewall blocks.
3. Check One HTTPS Site — Load https://developer.android.com. If HTTP works and HTTPS fails, fix device time or proxy interception.

Once you know which test fails, jump to the matching section and skip the rest.

Proxy, VPN, And Firewall Blocks That Stop Traffic

A proxy mismatch is a top reason an emulator shows Wi-Fi but can’t reach the web. Android Studio can use system proxy settings, auto-detect, or a manual proxy, and the emulator can follow those settings. If your network does not need a proxy, disabling it is the cleanest baseline.

Set Proxy In Android Studio

Open Android Studio Settings, then HTTP Proxy. Start with “No proxy” and test the emulator browser. If your network requires a proxy, switch to manual proxy and enter the host and port your network uses, then test again. Android’s emulator networking documentation calls out Android Studio proxy settings as the place to configure this when the emulator runs inside the IDE.

Clear Proxy In Extended Controls

If you run the emulator as a standalone window, you can also clear or set proxy entries from Extended controls. Open the three-dot menu, go to Settings, and make sure proxy fields match your current network.

• Disable VPN As A Test — Disconnect your VPN, reboot the emulator, and test again. Split routing can break DNS or HTTPS inside virtual devices.
• Allow Emulator Through Firewall — On Windows, allow the emulator and ADB on private networks, then reboot the emulator.

If proxy changes fix it, lock that configuration in and stop there. If proxy and firewall checks don’t help, check DNS and URLs next.

DNS, Localhost, And API Testing Gotchas

When the emulator has internet but your app still can’t reach what it needs, the issue is often name resolution or the URL you’re calling. The emulator sits behind a virtual router, so “localhost” means something different.

One more gotcha is captive portals. Hotel, airport, or office guest Wi-Fi may require you to open a login page on the host machine. The emulator often inherits the same network, but it may not show the portal page cleanly. If you’re on guest Wi-Fi and the emulator has no data, open a browser on your computer and confirm you’re fully signed in. Then reboot the emulator. If it still fails, try a phone hotspot to skip captive portal rules.

Use 10.0.2.2 For Host Services

Inside the emulator, localhost points to the emulator itself. To reach a web service running on your computer, use 10.0.2.2, which maps to the host side of the emulator’s network. If your API runs on port 8080, call http://10.0.2.2:8080.

Spot A DNS Failure Fast

If the emulator can open a site by IP but can’t open normal domains, DNS is the failing layer. Fix DNS on the host machine, then restart the emulator so it picks up the new resolver.

• Switch Host DNS Servers — Set your computer’s DNS to a public resolver and retry.
• Flush Host DNS Cache — Flush DNS or restart your network adapter on the host, then boot the emulator again.

Fix App-Side Blocks That Look Like No Internet

Sometimes the network is fine and your app is what’s blocking requests. A common case is a base URL pointing at http://localhost instead of the emulator-safe host. Another is TLS errors that your UI masks as “timeout.”

1. Log The Real URL — Print the URL your client uses and confirm the host and port are correct for the emulator.
2. Watch Logcat For TLS — Look for certificate or handshake errors and fix the trust chain used by the emulator.
3. Try A Plain Curl Test — Run adb shell and use a simple request tool if your image includes one, or open the browser to the same URL to confirm reachability.

If DNS and URLs are correct and web pages still won’t load, go for clean state and a repeatable test AVD.

Reset Deeper State Without Losing A Day

Past this point, random toggles stop paying off. You want clean state, a known-good emulator build, and one test that answers “is the emulator online?” in under a minute.

• Disable Snapshots — Turn off snapshots for the AVD and boot it fresh. A broken snapshot can revive the same network bug.
• Create A New Test AVD — Make a new AVD with default settings and a current image. If it works, your old AVD is the problem.
• Switch Graphics Mode — Try Automatic, Hardware, then Software graphics for a test AVD. Driver quirks can break the emulator in odd ways.

If a brand-new AVD has internet, migrate to a new device profile and move on. If even a new AVD is offline, the blocker is outside the AVD.

Host Machine Checks When Nothing Else Works

At this stage, treat the emulator like any other virtual device. If the host can’t route traffic cleanly, the emulator won’t either. These checks are the ones that most often fix stubborn cases on developer machines.

1. Reboot The Host Machine — A full reboot resets stuck virtual adapters and clears driver glitches that survive app restarts.
2. Reset Network Adapters — Disable and re-enable your active adapter, then restart the emulator.
3. Pause Competing Virtualization — If you use Hyper-V, WSL2, or other VM tools, test with them stopped, then boot the emulator.
4. Try A Different Network — A phone hotspot can confirm whether your router or office Wi-Fi rules are the trigger.

If you find that a VPN or virtual switch is the trigger, write down the working combo so you can repeat it without guesswork.

A Short Checklist You Can Reuse

When android studio emulator network not working pops up again, run this list top to bottom. It keeps you moving and stops you from bouncing between random fixes.

• Cold Boot First — Start fresh without snapshots and see if the AVD comes online.
• Reset ADB — Restart ADB so device routing and port rules are clean.
• Clear Proxy — Set the IDE proxy to none unless your network needs one.
• Verify 10.0.2.2 — Use 10.0.2.2 for host services, not localhost.
• Rebuild If Needed — Create a new AVD once you’ve ruled out host blockers.

If the emulator browser works and your app still fails, the fastest next move is to log the exact request URL and error from your HTTP client, then compare it to what works in the browser. That one side-by-side check can save an hour of guessing.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback