Choose an Android VPN client

To use a VPN on Android, start with a client that supports your provider’s configuration. Import it, choose a route, connect, and approve the system prompt. A “Connected” status isn’t enough: make a fresh request in the app you plan to use and confirm it takes the expected route.

First, check whether your provider offers sign-in within an app, a subscription URL, or a configuration file. Follow the client’s prompts for in-app sign-in; for a subscription URL, choose a client that supports its format. Android’s VPN settings can manage connections, but you can’t enter just any subscription URL as a server address. Installing more clients won’t help—use one for your first connection so you can pinpoint issues more easily.

Your configuration and where to import it
What you received Where to import it What to check first
Android client recommended by your provider In-app sign-in or setup wizard Get the installer from your provider’s official source or a trusted app store.
Subscription URL The client’s “Subscription,” “Configuration,” or “Import from URL” option The client accepts the subscription format and supports the protocols used in the configuration.
Local configuration file “Import from file” in a compatible client The file format matches the client; importing a file may not enable automatic updates.

With a third-party client, distinguish between reading a subscription and connecting to a route. The first depends on the configuration format; the second also depends on whether the client supports the route’s protocol. For example, support for Shadowsocks doesn’t imply support for Hysteria2. If your provider has import instructions for specific clients, use the matching option. VPNLabel users can start with the Android quick-start guide.

Import your subscription and grant connection permission

  1. Get your subscription. Sign in to your account panel as instructed by your provider and copy the current subscription URL. Paste the full URL into the client’s subscription field; don’t put it in the server address field for an individual route.
  2. Update and check the list. Save, then tap “Update” or “Sync.” Confirm that selectable routes appear in the current configuration. If you see a configuration name but no routes, check the import message instead of repeatedly tapping Connect.
  3. Choose a route and connect. Select a route, then turn on the client. If the client also offers a local-proxy-only mode, choose the mode that routes traffic through Android VPN for your first test.
  4. Approve the system prompt. The first time you connect, Android usually asks you to approve the VPN connection request. Make sure the requesting app is the client you just installed, then allow it. If another VPN or a local filtering tool that uses the VPN interface is running, check for conflicts first. Don’t disable a configuration managed by your organization.

If no permission prompt appears, the connection may still have started—the app could already be authorized. Check Android’s VPN settings to see which app is connected, then review the client’s status. If you see “Subscription update failed,” first make sure your current network can access the internet, then check that the URL is still valid and the import format is correct. Fetching a subscription and connecting to a route are separate steps: a successful fetch doesn’t guarantee the route will connect, and an older configuration may still work even if its update failed.

Check your exit IP and app routing

While connected to the same Wi-Fi or mobile data network, open IP check in your browser before connecting and note your public exit IP. Connect, then run a fresh check in the same browser and compare the results. Don’t switch networks between tests; changing networks can change your exit IP. The IP address is a more useful comparison than a region label, since IP geolocation databases aren’t always accurate. If your browser has its own proxy enabled, account for that too.

Next, test the app you actually plan to use. If the client has settings to include or exclude apps, check which way the rules work: an allowlist routes only listed apps, while an exclusion list does the opposite. After changing a rule, reconnect as prompted, then make a fresh request in the target app—for example, load content that isn’t cached. To verify the route more closely, check whether the client provides connection logs or rule-match details. An app displaying content doesn’t prove which route it used.

A changed exit IP doesn’t mean DNS queries take the same route. Secure DNS in your browser, Android Private DNS, and the client’s own DNS settings can all affect the result. To check DNS, test it separately on the same network with the same browser settings, then compare it with the expected resolution path. If you see an unfamiliar DNS provider, check your configuration first; a different provider name alone doesn’t prove a DNS leak.

Disconnects after locking the screen: check background restrictions

If the connection works in the foreground but drops after the screen turns off, keep the network unchanged and test once with the screen locked. After unlocking, check whether the client says disconnected, reconnecting, or connected even though requests fail. If the issue only happens when switching between Wi-Fi and mobile data, test that separately; don’t confuse reconnection issues with background restrictions.

Once you’ve confirmed the issue is related to locking the screen, go to Settings → Apps → your client → Battery and look for options such as “Unrestricted,” “Allow background activity,” or “Don’t optimize.” Menu names and locations vary by device. Change the setting for this client only; there’s no need to disable battery saving for the whole device. Relaxing background restrictions may increase battery use. Reconnect on the same network, lock and unlock the screen, then make a fresh request to test again.

Android’s “Always-on VPN” and the battery optimization exemption are separate settings. Always-on VPN tells the system to keep or re-establish a specified VPN connection; it can’t fix an invalid route configuration. “Block connections without VPN” may prevent internet access when the tunnel disconnects and can affect apps that need a direct connection. First confirm that the connection and app routing work as expected, then decide whether to enable it.

First-connection troubleshooting checklist

  • ✅ Subscription updates and routes appear: the configuration has loaded. Now test the route connection.
  • ❌ Connection fails immediately: check system permission and whether another VPN is in use, then confirm your network is working. Test one compatible route at a time; don’t change the protocol and app-routing rules together.
  • ❌ The browser’s exit IP changes, but the target app behaves the same: check whether the app is excluded and whether the rule is set in the wrong direction, then make a fresh request to rule out cached content.
  • ❌ It disconnects only after the screen locks: check background restrictions first. If it disconnects only when switching networks, check whether the client reconnects.

If you still can’t find the cause, note whether the failure happens during import, authorization, connection, or recovery after locking the screen. Record the client version, network type, and exact error message. Redact your subscription URL, token, and account details before sending a report. These details are more useful than reinstalling the app and help avoid wiping a configuration that was working.