Setting up a VPN on Android involves more than seeing “Connected.” This guide walks through installing a client, importing a subscription, granting system permission, and verifying that the connection works. Start with the default settings, check that your apps use the intended route, then troubleshoot disconnects after locking the screen and DNS settings.
In this article, “VPN connection” refers to Android routing traffic through a VPN interface. A client’s use of this interface does not mean the subscription uses any particular transport protocol. Check the service dashboard and client documentation for supported protocols, configuration formats, and client names.
Prepare your client and subscription details
Before you begin, make sure your device can access the network. If a public Wi-Fi network requires you to sign in through a captive portal, complete that step before connecting to an international route. Updating your subscription or switching servers repeatedly usually won’t help if the underlying network is unavailable.
VPNRE users can get a client from the user dashboard. For installation instructions, see the Guides. If you download a general-purpose client from its official project site, make sure it supports the subscription format provided in your dashboard. Don’t assume compatibility based on a similar app name, and never enter your account credentials in an app from an unknown source.
Shadowsocks, VMess, Trojan, and VLESS are names for different protocols or configuration types, not universal import formats. A client that recognizes one type of node may not be able to read every service’s subscription. If the service offers different subscription links for different clients, use the one that matches your app and don’t alter its URL parameters.
- ✅ Confirm that your internet connection works, and note its status before connecting.
- ✅ Make sure the download source, client, and subscription format are compatible.
- ✅ Get the subscription link from your dashboard; don’t use the dashboard login URL.
- ✅ Keep your account details safe. VPNRE requires no email address; create an account with a username and password.
Subscription links often contain credentials used to retrieve your configuration, so treat them as sensitive information. Don’t share them in public forums, online conversion tools, or screenshots. If a link has been exposed, check whether your dashboard lets you reset it, then update the link saved in your client.
Install an Android client
After downloading the installation file, follow the system prompts to install it. If Android asks you to allow your browser or file manager to install apps, grant permission temporarily only to the source you’re using. You can revoke it after installation. This is separate from the VPN connection permission you’ll need later, and there’s no need to leave app installation enabled to stay connected.
If you see “Can’t install app,” first check that the file downloaded completely, that the app supports your Android version, and that you don’t already have an app with the same name but a different signature. Don’t overwrite an old version from an unknown source. Before uninstalling and reinstalling, make sure you can restore your subscription link and any important settings; uninstalling may erase local configuration.
System menu names vary across Android manufacturers. Options such as “App info,” “Battery,” and “Background activity” may be in different places; treat the names in this guide as categories. Don’t enable unrelated permissions just to find an exact match. A standard network connection setup shouldn’t require device administrator access unrelated to its function.
Import your subscription and update the configuration
Installing the client only prepares the tool. A subscription link retrieves servers and related settings; it doesn’t establish a connection. After copying the link, add it to the client as a remote configuration or subscription and refresh it. Once the available servers appear, you can connect.
- Copy the right link. Find the subscription link for your client in the service dashboard and use the copy button to avoid missing characters.
- Add a remote configuration. In the client, look for “Configuration,” “Subscription,” or a similar option, then choose import by URL. Name it whatever you like, but keep the link intact.
- Update the subscription. Wait for the download and parsing to finish. Make sure the app shows a server list, not just an empty configuration name.
- Enable the configuration. Some clients let you save multiple configurations. After importing, select the one you want to use.
- Choose a server and mode. For your first connection, keep the service’s default routing rules and select one server manually. Avoid changing several settings at once.
If parsing fails, first check that you selected the right client, the link is complete, and the subscription is still valid. If the download fails, also check whether your current network can reach the subscription URL. These are different issues: a successful download followed by a parsing error usually points to format compatibility; if no content was retrieved, check access and credentials first.
Don’t send your subscription to an unfamiliar website for format conversion. If conversion is necessary, use a method explicitly provided or approved by the service. There’s no need to refresh repeatedly after a successful import; updates retrieve configuration changes and aren’t a universal fix for connection problems.
Grant connection permission and configure routing
When you tap Connect, Android usually displays a system VPN connection request to let the app route network traffic. Make sure the request comes from the client you just installed, then allow it. This permission lets the app use Android’s network interface; it doesn’t confirm that the route works, so you’ll still need to test access.
Android generally allows only one active VPN service per user or profile. Some ad blockers, corporate network tools, and firewalls use the same interface and may displace your VPN client. If the connection stops immediately after you tap Connect, check whether another app is using the interface. Don’t run multiple network-routing tools at the same time.
Rule-based mode typically routes traffic directly or through an international route based on domains, addresses, or other conditions. Global mode usually sends traffic handled by the client through the selected exit, but app exclusions, local network exceptions, and configuration rules may still apply. Global mode can help isolate a routing-rule issue, but it doesn’t guarantee that every app uses the same exit.
Some clients also support per-app routing. Check whether the list means “only these apps use the VPN” or “these apps don’t use it.” If your browser works but a collaboration app doesn’t, check whether that app is excluded. After changing the setting, reopen the app so it doesn’t keep using an existing connection.
Android’s “Always-on VPN” and “Block connections without VPN” options aren’t required for a basic connection. The latter may block internet access if the client stops or its configuration fails. First make sure the connection works, then enable these options only if they suit your needs—and note where to turn them off.
Battery settings and background activity
If the connection works while the app is open but drops after you lock the screen, Android’s background restrictions may be the cause—not an expired subscription. Open the client’s app info and check its battery settings. Make sure background activity is allowed and that the app isn’t in a restricted or deep-sleep list. Depending on the device, the option may be called “Unrestricted,” “Allow background activity,” or something similar.
Allow background activity for the client if needed; you don’t have to disable battery saving across your whole device. Some manufacturers also offer autostart controls or the option to lock an app in the recent-apps view. These may help keep it running, but not every device needs them. Start with settings that directly affect the client, then lock the screen and reopen the app to see if anything changes.
A connection may also need to be re-established when you switch from Wi-Fi to mobile data. If the issue only occurs after switching networks, disconnect and reconnect, then check the client’s status and error messages. Don’t assume every background disconnect is caused by battery restrictions; an unreachable server, incorrect configuration, or conflict with another VPN app can cause the same symptoms.
Verify your exit, apps, and DNS
Check your exit location and whether your apps work as separate steps. Before and after connecting, open the IP lookup page in the same browser and compare the displayed exit address and region. Geolocation databases can disagree, so don’t rely on the location label alone. In rule-based mode, the lookup page may use a direct connection; an unchanged exit address doesn’t necessarily mean the client isn’t working.
Next, open the international websites or collaboration apps you actually need and test page loading, sign-in, and key features. A page loading doesn’t guarantee that uploads or persistent connections work. Likewise, a service login failure may be due to your account, regional policies, or the service’s own security checks—not just the route.
| What you see | Possible cause | Next step |
|---|---|---|
| Shows connected, but the target page won’t load | Unreachable server, unmatched routing rule, or DNS resolution issue | Check the active configuration and connection logs, then test another server |
| Browser works, but a specific app doesn’t | Per-app routing, an existing connection, or an app-specific restriction | Check the app list and reopen the target app |
| Works in the foreground, but disconnects when the screen is locked | Background activity is restricted or the network has changed | Check battery settings and see what happens after reconnecting |
| Exit address changes, but DNS test results seem questionable | DNS resolution takes a different route from traffic, or the test results are being misinterpreted | Check the client’s DNS settings, Android Private DNS, and the browser’s Secure DNS |
A DNS leak test checks whether domain lookups follow the intended route. Android Private DNS, your browser’s Secure DNS, and the client’s DNS settings may all affect resolution. A resolver in another region doesn’t automatically mean there’s a leak, and a changed exit address alone doesn’t prove that DNS requests follow the expected route.
Before troubleshooting, note your current settings and check the client documentation to understand its DNS policy. If your browser uses encrypted DNS independently, its test results may not reflect what other apps use. The resolver provider shown by a test site may also differ from the server your device connects to directly. Review the client logs and configuration before making changes; switching DNS settings blindly can create new problems.
When it’s working: Verification is complete when the client stays connected, your target apps work as expected, and the exit and DNS routes match your selected rules. The key icon in Android’s status bar only shows that the VPN interface is active; it doesn’t prove that the international route or routing settings are correct.
Troubleshoot connection issues in this order
Keep the issue reproducible while troubleshooting, and change just one thing at a time. Check your underlying network first, then the subscription update, active configuration, and system permissions. Next, review your server selection, per-app routing, and DNS, and finally check background restrictions. This makes it easier to tell which change helped, rather than having the issue disappear temporarily with no clear explanation.
Labels such as IEPL, transit, and direct in server names describe how a route is set up, not which protocol the client uses. An IEPL circuit typically uses dedicated Ethernet transport; a transit route forwards traffic through an additional gateway; and a direct route usually connects to a server outside mainland China. The label alone doesn’t confirm that the route works, nor does it fix an incorrect subscription format or missing system permission.
When reporting an issue, include your device’s OS and client versions, the error message, your network type, and whether behavior differs between foreground use and a locked screen. Redact subscription links, account credentials, and other sensitive information from logs and screenshots. For general questions, see the Help Center. For account or subscription issues, open a support ticket in the user dashboard.
Once you’ve verified the connection, compare monthly subscriptions and data plans based on your actual usage. Confirm that the device is configured correctly and the apps you need work before deciding how much data to get. VPNRE supports unlimited devices and uses bank-grade encryption. The refund policy offers a 7-day money-back guarantee; see the plans page and dashboard for current plan details.