After installing a client, importing your subscription, and granting permissions, check that your Android VPN connection is actually working. A key icon in the status bar only means the VPN is on; it doesn’t confirm that the app you want is using the selected route. For your first setup, get connected on the same network first, then check routing and what happens when the screen is locked.

Install a VPN client: Check the download source first

To use VPN5200, check the download page in your dashboard for Android client options. If you choose a compatible client from the setup guide, make sure it supports the subscription format provided in your dashboard; the word “VPN” in an app’s name isn’t enough. The client establishes the connection, while the subscription provides the route configuration. Installing the app alone does not import any routes.

If you need to install an APK downloaded to your device, Android may ask you to allow your browser or file manager to install apps. Grant this permission only after verifying the source, then turn it off once installation is complete. If you’re unsure where the APK came from or Android reports a signature conflict, don’t disable security checks just to proceed. Verify the download source and check whether an app with the same name is already installed. If your device is managed by your organization and installation is restricted, contact your administrator.

Import a subscription: Know the difference between updating settings and connecting

  1. Sign in to your user dashboard and get the subscription link for your chosen client. Copy the entire link—not the dashboard page URL—and don’t remove any parameters at the end.
  2. In the client, look for an option such as “Subscription,” “Configuration,” or “Import from URL,” then paste the link and save it. If the app offers a refresh or update option, use it and wait for the route list to load. Names vary by client.
  3. Choose a route from the imported configuration, note its name, and connect. Refreshing a subscription only fetches the configuration again. Seeing a route in the list doesn’t mean your traffic is using it.

If the list is empty, first make sure your device can open the dashboard, then check that you copied the full link and that the client supports its format. If an old configuration is still there, check the update result rather than assuming the update worked because the old routes remain visible. If the update succeeded but a route won’t connect, troubleshoot the connection instead of repeatedly importing the subscription.

Grant system permission: Check which app is requesting VPN access

The first time you start the VPN in a client, Android usually displays a system connection request. Make sure it comes from the client you just opened, then allow the connection. If you deny the request, return to the client and try connecting again. After granting permission, check the client status and Android’s VPN settings to confirm that the active connection belongs to that app. Whether a key icon appears in the status bar depends on your Android interface.

Only one VPN can usually control the system connection at a time within the same user profile. Ad blockers and firewall apps that use the VPN interface can also conflict. If another app’s “Always-on VPN” is enabled on your personal device, turn it off temporarily for testing if doing so won’t disrupt its purpose. For a work-managed VPN or work profile, contact your administrator; don’t remove management settings to troubleshoot.

Verify the connection: Check both your IP address and access

Disconnect the VPN and use the same browser on your current network to visit a trusted public IP lookup page. Note the address shown. Connect to the route you just selected, reload the same page in the same browser, then try the website or app you normally use. Keep Wi-Fi and mobile data unchanged while comparing results; otherwise, an address change may be caused by switching networks rather than by the VPN.

If the client supports global routing, you can briefly use it on a personal device for comparison, then restore your usual routing rules. Split tunneling uses apps or rules to decide which connections go through the VPN, so the lookup page and the app you’re testing may take different routes. A browser IP that hasn’t changed doesn’t prove that no apps are using the VPN; a changed browser IP doesn’t prove that the app’s traffic is routed through it either.

Common results after connecting and what to do next
What you see Next step
The client says it’s connected, but the lookup page shows the same IP address Reload the lookup page and check whether your browser or the lookup domain is set to bypass the VPN in your routing rules.
Your browser IP changed, but the app you need won’t open Check whether the app is included in VPN routing. After changing the setting, reopen the app and, if needed, compare with the VPN disconnected on the same network.
No test websites open after connecting Disconnect and confirm your regular internet connection works, then try another route. If it still fails, check whether the client reports a connection or DNS resolution error.
It works with the screen on, but the app won’t connect after you unlock your phone Keep the network unchanged and check the client’s background status, battery optimization, and system power-saving settings.

An IP address comparison only covers the connection used by the lookup page at that moment. It doesn’t prove that DNS requests or IPv6 traffic follow the same route. To troubleshoot DNS leaks, check the client’s DNS routing separately and compare results before and after connecting with the same browser secure DNS settings. Seeing the name of a resolver doesn’t tell you whether requests went through the tunnel or connected directly.

Disconnects when locked: Adjust battery settings if needed

Leave the VPN connected, lock the screen, then unlock it. Don’t open the client manually first, as that may reconnect it. Make a new request in the app you were testing, then check the client’s status or connection history. If the connection drops every time the screen is locked but works while it’s on, check background restrictions first. If it drops only when switching between Wi-Fi and mobile data, test that separately rather than combining it with the screen-lock test.

Search your system settings for “Battery optimization” or “Background activity,” then find the client that actually establishes the VPN connection. Depending on your device, the setting may be called “Unrestricted,” “Not optimized,” or “Allow background activity.” Change settings for that app only, then repeat the screen-lock test on the same network. Loosening background restrictions may use more battery. If it doesn’t help, restore the original setting and check the route and underlying network instead.