How do you set up a VPN on Android? Follow this order: install a compatible app, import your subscription, choose a route, allow the system to establish a VPN connection, then check background activity and access. Android’s VPN settings manage connection permissions; they don’t provide international routes. Opening that settings page alone won’t configure a VPN.
This guide follows the steps for first-time setup. Menu names vary by device manufacturer, so look for features such as app battery management, VPN, and background activity rather than relying on the exact location of a button. Use only apps from verified sources and your own subscription.
Understand the app, subscription, and system permissions
The app reads the configuration, applies routing rules, and connects to a remote server. The subscription link retrieves route configurations maintained by the service provider. Android’s VPN permission lets the app route selected traffic through the system’s virtual network interface. Each has a separate role; if any part is missing, the app may open without your network behaving as expected.
Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are protocol names that may appear in a configuration; they aren’t interchangeable subscription formats. Whether an app supports a protocol also depends on its core and version. Use the app and import method specified in your service panel, and don’t assume compatibility based on the app’s name alone.
| Component | What it does | What to check |
|---|---|---|
| App | Reads the configuration and connects | Download source, protocol support, and device architecture compatibility |
| Subscription link | Retrieves routes and related configuration | Is the link complete and in the right format for the app? Did the update succeed? |
| VPN permission | Allows the app to create a system tunnel | Did the permission prompt come from the app you’re using? |
| Routing and background settings | Directs traffic and keeps the app running | Are the rules correct? Is the process restricted when the screen is locked? |
Install the app and verify its source
For VPNWood, start at the client downloads in the service panel and follow the Android instructions there. Available download and subscription import methods are shown in the panel. Don’t pick a similarly named installer from search ads, forwarded group messages, or unknown mirror sites.
If you download an APK in a browser, Android may ask you to allow that browser to install apps. Grant permission only after verifying the file’s source, and revoke it after installation if you like. This is separate from VPN access, and you don’t need to disable the system’s overall security checks to install the app.
If you see an “App not installed” error, first check that the download completed, the installer matches your Android version and processor architecture, and there isn’t already an app with the same name but a different signature. Don’t uninstall an existing app right away: first check whether you can restore its configuration and save any settings you need. If Android or the installer warns that the file may be risky, stop and verify it instead of repeatedly dismissing the warning.
Import your subscription and confirm the configuration is up to date
After installation, return to the service panel to get the subscription for your app. Subscription links often contain a token that identifies your account, so treat them as sensitive credentials. Don’t post the full link in public forums, screenshots, or unknown subscription-conversion sites. If you need help, hide the link and QR code.
- Use the right import option. If the panel offers an “Import to app” option, confirm that it opens the app you just installed, then approve the import. If it doesn’t open the app, copy the link and add it manually.
- Add the remote configuration. In the app, look for “Subscription,” “Configuration,” or “Import from URL,” then paste the complete link. Don’t use the panel sign-in address or an ordinary webpage URL as a subscription link.
- Update and activate it. Download or update the configuration, then confirm that routes or policy groups appear. Some apps also require you to select the imported configuration as the active one.
- Choose a working route. Follow the panel’s instructions to select a region and policy group. Stick with one route while testing so you don’t keep changing your exit during troubleshooting.
A failed update doesn’t necessarily mean the route is unavailable. Check whether the error indicates an unsupported format, authentication failure, or request timeout. For a format error, use the matching subscription import option. For an authentication error, check the subscription status and link in the panel. For a timeout, check your underlying network first. If the subscription can only be updated after connecting, follow the panel’s instructions; don’t modify the link parameters yourself.
Grant VPN access and choose a routing mode
When you tap Connect, Android usually shows a system prompt to establish a VPN connection. Check the app name and make sure it’s the app you just opened, then allow the connection. This permission allows the app to handle network traffic routed through the tunnel, so don’t grant it to apps from unknown sources.
On most devices, only one app at a time can use the system VPN tunnel in the same user or work profile. Ad blockers, firewalls, and work network apps may use it too. If a new connection drops immediately, check for a conflict before assuming your subscription has expired.
Choosing between rule-based and global mode
For your first setup, start with a rules configuration maintained by your service provider. Rule-based mode directs traffic through the proxy or a direct connection according to criteria such as domain, address, or app; the details depend on the app and configuration. Global mode usually routes traffic handled by the app through the selected exit, but that doesn’t mean every app and system service on your device will use the tunnel.
If your app supports per-app routing, check that the app you’re testing isn’t excluded. If you only enable a local proxy port without turning on VPN or TUN routing, apps that aren’t configured to use the proxy may still connect directly. To troubleshoot one app, compare rule-based and global modes temporarily. Once you’ve identified the cause, restore the routing settings that suit your everyday use.
Android’s “Always-on VPN” and “Block connections without VPN” are optional system policies, not requirements for your first connection. The latter can cut off network access if the tunnel can’t connect. Enable it only if you need that blocking policy and understand how the app handles per-app routing.
Allow background activity and check the connection with the screen locked
Battery optimization or manufacturer-specific background restrictions are common causes of Android VPN disconnects. A VPN icon that remains visible doesn’t prove that the app process and tunnel are still working. If the connection works with the screen on but fails when it’s locked, focus on background settings rather than repeatedly changing subscriptions.
- ✅ Open the app’s battery settings and allow background activity. If there’s an “Unrestricted” or similar option, select it if needed.
- ✅ If Android has a separate auto-start setting, allow the startup behavior the app requires. Locking the app in recent tasks can help, but it doesn’t replace battery settings.
- ✅ If the app uses a foreground service, keep its status notification visible and follow any system prompts for the relevant permissions.
- ✅ Check what happens after locking the screen, switching Wi-Fi networks, and switching to mobile data. Note the exact circumstances when the connection drops.
- ❌ Don’t grant access to contacts, accessibility features, or device management just to keep the connection active; these permissions aren’t related to network functionality.
Allowing background activity won’t fix every disconnection. Switching networks changes the underlying connection, so the app may need to establish the tunnel again; UDP connections can also be affected by local network policies. If the problem occurs only on a particular network, compare another network with the same configuration before deciding whether to try a compatible route recommended by the panel.
Verify the connection and tell DNS issues from route problems
Check what actually works, not just the connection button. First confirm that an ordinary webpage opens, then visit the international site you need. Next, check whether the target request matches the expected policy in the app’s logs or connection list. Before sharing logs, hide subscription URLs, account details, and other sensitive information.
An IP address lookup only shows where that particular request exited. In rule-based mode, the lookup site may be configured for a direct connection, so it can’t prove the exit used by other apps. Location databases may also be out of date. Check the policy records for the request you care about, rather than relying only on the region shown on a webpage.
Webpages won’t load? Identify where the error occurs
A DNS resolution failure, connection timeout, and website access restriction are different issues. DNS translates domain names into addresses. If the DNS path doesn’t match the routing rules, resolution may fail or return an unsuitable address. Android Private DNS, the app’s built-in DNS, and a browser’s secure DNS may all be involved; their priority depends on the system and app implementation.
A DNS leak generally means that a DNS request expected to use a protected route went through an unexpected one. With direct-connection rules, some DNS requests may be routed directly by design; that isn’t automatically a fault. First determine which requests should use the tunnel, then check the app’s documentation and DNS records. Avoid changing several DNS settings at once.
How to confirm the connection: The app has established a tunnel, the target app matches the expected routing rule, the page loads successfully, and behavior after locking the screen or switching networks is as expected. The VPN icon, IP lookup, and route tests are each only one piece of evidence; none replaces the others.
Troubleshoot common issues by symptom
Connected, but no webpages will load
Disconnect the app first and check that your underlying network works; public Wi-Fi may require you to complete a web login first. Then check that the configuration is active, the policy group has a working route selected, and Android isn’t still set to block connections without a VPN. Once basic access is restored, troubleshoot routing rules or DNS separately instead of changing several settings at once.
The browser works, but one app doesn’t
Check per-app routing, the domain rules used by that app, and whether you need to fully close and reopen it. Some services also determine access based on account region, permissions, payment details, or platform rules. A network connection can improve the route, but it can’t guarantee eligibility for a service. Don’t mistake an account restriction for a route problem.
Only certain routes or networks fail
Keep the app and configuration unchanged while comparing other routes and underlying networks to narrow down the cause. Note the error type, selected region, network, and whether the issue is reproducible. Then look for relevant steps in the Help Center. An app’s connection test alone can’t confirm that a service will work, and results from different kinds of tests aren’t directly comparable.
Final checks before you use your VPN
Your Android setup should now be complete: an app from a verified source, a compatible subscription format, valid system permissions, routing rules that fit your needs, and background settings tested against real usage. If something goes wrong later, check these in order; it’s usually more helpful than repeatedly uninstalling and reinstalling the app.
VPNWood doesn’t require an email address; you can create an account with a username and password. Before choosing a subscription, check the data allowance and billing terms on the plans page. The refund policy offers a 60-day money-back guarantee. Correct network setup and choosing the right plan are separate questions: verify the connection first, then choose based on your actual usage.