Routes & Clients

VPN Troubleshooting Guide

For first-time setup, importing a subscription, and checking your connection, start with the Quick Start Guide. If you have followed the guide but are still seeing connection failures, disconnects, or app issues, use the sections below to find the relevant symptoms. This guide starts with the easiest checks. Change one thing at a time and keep the results for comparison.

Initial Checks

Can't Connect: Network, Permissions & Routes

First, check that you can get online without the client

Note where the client stops: nothing happens when you tap Connect, it stays on “Connecting,” a system permission prompt appears, or the connection is established but websites won't load. For the last case, go to Connected, but no websites load rather than treating it as a failed handshake. For the others, disconnect the client and use your usual network to open a public website you can normally access, then open the user panel. If neither loads, first check whether the device is actually online instead of switching routes. A Wi-Fi icon only shows that the device is connected to an access point; it doesn't mean the access point can reach the internet.

On hotel, campus, or guest Wi-Fi, your browser may be redirected to a captive portal. Make sure the page belongs to the network you're using, then follow its instructions to connect. Never enter your VPNHaiLian account details on a captive portal. If basic access still fails, compare with another network you're authorized to use, keeping the device and client unchanged. If the original network fails but the other works, check the original network's access requirements first. If public websites load but the panel doesn't, note whether it shows a DNS error, certificate error, or timeout. Don't bypass a certificate warning, and don't mistake an inaccessible management panel for a problem with every route.

Check whether the system has authorized the client to manage the connection

Try connecting again and watch for a system prompt. If the client needs to create a VPN configuration, verify that the request came from the app you just opened, then grant permission as prompted. If you previously dismissed the prompt, start the connection again from the client and check in the system's network settings whether its configuration is present. If other VPNs, proxy tools, or network filters are running, note their status. Pause only the items you're authorized to change, then restore them afterward. Work- or school-managed devices may restrict configuration changes; ask the device administrator to check rather than deleting management profiles or changing organization policies.

Also check the system date, time, and time zone. A device that's been offline for a long time, manually adjusted after travel across time zones, or resumed from sleep as a virtual machine may treat a certificate as not yet valid or expired. If an administrator set the time, note the discrepancy and ask them before changing it. On a personal device, check that automatic time synchronization is working. Don't disable certificate checks as a workaround. If correcting the time fixes the connection, test again on the original network to distinguish the effect of the time correction from a network change.

Report one failed route separately from multiple failed routes

If you have a route list, note the region and type of the route that failed, then manually select a different route on the same network. Don't let automatic selection change the region in the background. If only the original route fails, keep a working route as a point of comparison and use one that meets your needs for now. If several fail, repeat the test on another network. If the list is empty or contains only old configurations, go to Subscription updates to check whether the configuration imported successfully. If you didn't see a permission prompt during initial setup, return to the Quick Start Guide to check the order of import and connection steps.

In your support ticket, include the operating system, client source, time and time zone of the failure, exact error, whether the panel opens, and the results of testing another network and route on the same device. If just one route failed, name it; there's no need to reinstall the client repeatedly to reproduce the issue.

Traffic Path

Connected, but Websites Won't Load

Check connection status separately from actual access

When the client says Connected, the connection process has reached that state, but that doesn't prove every app's traffic is using the route. In the same browser, try a familiar public website and the site that failed, and note whether everything fails or only one address. Some browsers may show cached content, so check that a new request was actually made—for example, open a public page on the same site that you haven't visited before. Also distinguish a browser-generated error from one returned by the website: the former may mean a connection couldn't be established; the latter means the request reached a service that returned a response.

Next, open My IP on this site and compare the results with the client disconnected and connected. First check whether this page matches your current routing rules. If it normally uses a direct connection, identical results don't show that the VPN is inactive. If the lookup fails or the browser reuses a cached result, the comparison is inconclusive. Use the client's visible connection logs alongside the result; they're more useful than an exit-location label alone. A location label is the lookup service's estimate for the exit address, not your device's location. Use test results for troubleshooting, and avoid posting your full exit address publicly.

Use the browser error to guide checks; change one setting at a time

What happens to websites after connecting
SymptomCheck firstRecord for comparison
Domain can't be resolvedWhether the browser and system use different DNS settingsThe error for the same domain before and after connecting
Connection timed outWhether the site is reachable and the issue recurs on a similar routeWhether other public sites load normally
Certificate warningThe address, system time, captive portal, or managed inspection policyThe warning type; never share certificate private keys or account details
The site returned an access-denied messageApp account permissions, the site's message, and its service requirementsThe exact error page and when it appeared

If only one browser fails, try the same public page in another browser. Check whether the affected browser uses a proxy extension, separate Secure DNS setting, or work profile. Don't disable all security features and extensions before identifying the cause; test only settings that could affect the request, and change only what you're allowed to. If several browsers fail but the panel still opens, check whether the panel uses a direct connection. Its loading only confirms that this particular access path works. If the page shows a region or account restriction, follow the site's instructions; switching routes repeatedly may not help.

Check for proxy settings that remain after disconnecting the VPN

Some desktop apps use the system proxy; others have their own manual proxy settings. If websites still fail after you quit the client and the system proxy still points to a local address, the browser may be sending requests to a local listening port that's no longer running. Check whether the client enabled the setting temporarily or whether a work profile requires it. On a personal device, disconnect and quit the client normally, then check that the proxy has returned to its previous value. Don't copy proxy addresses or ports from another device, and don't reset all network settings; you could lose useful information about the original problem.

If only some page components fail to load, record what happens to the main page and the failed components separately. The page may load while images, login windows, or video fail because component requests can use different domains; app routing may not match the main domain. Don't upload a full network log exported from browser developer tools; it may contain login details. In your support ticket, name the public site, identify the failed component, note whether switching routes or browsers helped, and say whether it worked again after disconnecting on the same network. If the issue affects multiple apps, include the system proxy status and the DNS comparison.

Route Comparison

Slow Speeds and Peak-Hour Slowdowns

Pinpoint which part of the task is slow

A page that takes a long time to start loading, a consistently slow file download, and a call with audio that repeatedly stutters are different problems. Waiting before a page starts may be due to DNS lookup, connection setup, or server response. Large-file transfers depend more on the network path and the other end's capacity, while real-time calls also need data to arrive consistently. Even a promising response-time reading in the route list can't replace testing the task itself. Choose a repeatable, low-impact task with public content, note when it starts to slow down, and avoid using unrelated test results to infer how a particular app performs.

Check local conditions on the original network first. Pause cloud sync, large file transfers, or system updates you started, wait for background transfers to stop, then repeat the same test. If a wireless device is far from the access point, compare from the same room. If wired access is available, use it to help distinguish Wi-Fi fluctuations from upstream network issues. Don't change from Wi-Fi to mobile data, switch devices, and change the destination all at once. If you can only test at a business or on a shared network, leave your connection settings alone and don't adjust shared equipment. Avoid repeatedly testing with large files; it can use extra bandwidth or data.

Compare routes in the same region, and time periods on the same route

See the Nodes page for an overview of direct, relay, and IEPL dedicated routes, then compare routes you can test in your client. A direct route has no extra relay entry point; a relay forwards traffic from an entry point to a subsequent route. IEPL differs in how the link is arranged, but it isn't necessarily faster for every destination. Keep the destination and region fixed when comparing route types; if the region changes during testing, note it. Different exit addresses may be assigned to different content servers, so playback or download results can't automatically be attributed to the route type.

To investigate peak-hour slowdowns, establish a baseline during the day when things work. Record your local network, route, task, and time, then repeat under the same conditions in the evening and compare with another route in a similar region. If direct access to regular sites and several routes are all slow on the same network, first check whether the local connection or shared network is busy. If one route repeatedly has trouble at similar times while another completes the same task, switch to the route you've verified and send support both sets of results. For real-time collaboration, consistently completing the task is more useful than one fast page load.

Check whether the issue is a plan allowance or a network path

Check your subscription status and remaining data in the user panel, then check the client's last update time. Plan allowance and connection quality are different things: having data remaining doesn't guarantee a working network, and one slow app doesn't prove a plan limit is in effect. Monthly subscription data resets each month on the activation date; data packs never expire and remain available until used. For plan allowances, see Plans & Pricing; don't upgrade just because of one slowdown. If only long requests from Cursor or another coding tool stall midway, see Route Selection Tips for AI Coding Tools and note whether the first response is slow or the connection drops after it starts.

In your support ticket, describe a repeatable task, the exact step that stalls, your local time zone, comparison times, and route type. If switching routes fixes it, name the working route too. If only one service is slow, say how other public services perform.

Connection Stability

Frequent Disconnects and Mobile Background Dropouts

Match disconnect times to what the device was doing

Check the client logs for what happened before and after the disconnect, then recall whether the screen stayed on, the device had just locked or woken, or you moved from Wi-Fi to mobile coverage. A disconnect during continuous foreground use and one that happens every time the network changes may have different causes. Keep the device in one place on a single network you're authorized to use, and repeat a task that often gets interrupted. If the disconnect stops when the network stays the same, test the network switch separately. The original transfer may need to reconnect after a switch; even if the client reconnects, a call or download may not resume where it stopped.

If the device often disconnects where signal strength fluctuates, check whether Wi-Fi is still connected when the issue occurs and whether other apps can connect directly at the same time. If the problem happens after a desktop wakes from sleep, first make sure it has reconnected to the network, then connect the client normally instead of rapidly toggling it as soon as the device wakes. Also check for a second VPN configuration or another tool that automatically takes over the network. If switching routes on the same network doesn't help and disconnects still coincide with the same device action, investigate the device or its connection process rather than treating every reconnect as a route change.

Mobile devices: Identify which app is being paused

On Android, keep the client in the foreground for one test, then lock the screen and repeat the same steps. If the issue only happens in the background, check the client's battery optimization, background activity, and background network permissions. Menus vary by device; adjust only the necessary app using options you can actually see, rather than disabling power-saving features globally. Also check whether the VPN connection really disconnects or whether the app you're using stops sending and receiving data in the background. If the system still shows the VPN as connected after you wake the device and other apps work, check the target app's background permissions first. See the Android VPN Setup Guide for configuration steps, but follow the interface on your device.

On iOS, compare the system VPN status with the client status. Record what changes when you switch to the background, lock the screen, and reopen the app. If you previously force-quit the client, run a separate test without doing so; an app preview in the app switcher doesn't prove that the tunnel is still active. If the device is managed, ask the administrator to check the VPN configuration and policies rather than deleting the configuration yourself. On both Android and iOS, test Wi-Fi and mobile data separately in the same location to see whether disconnects happen only on one type of connection. If one connection is stable but switching between them causes interruptions, report those as separate behaviors.

Automatic reconnection and interrupted work

If the client offers automatic reconnection or on-demand connection, note the original setting, try it if appropriate, and check whether the connection returns after the network recovers. Automatic reconnection only tries to restore the route; it can't resume a call, file transfer, or remote session. Save your work before testing and use a public webpage to check the connection rather than repeatedly switching routes during an important meeting. If the client consistently shows Connected but your work session times out after being idle, compare the app's session behavior under the same conditions with another app. The issue may be with the app session rather than the device's connection as a whole.

Submit a support ticket if disconnects continue in the foreground, on a fixed network, and across different routes, or if a background issue reliably recurs with the same steps. Include the operating system, power-saving settings, connection type, time, sequence of actions, and redacted disconnect and reconnect logs.

Configuration Delivery

Subscription Update Failures and Empty Server Lists

Check the panel, subscription request, and configuration import separately

A subscription update isn't another name for connecting. The update requests configuration from the subscription endpoint, then the client processes it and refreshes its local node list. Connecting to a route happens afterward. So if the client shows an update in progress, a download failure, or an unsupported format, existing routes may still work, but the local list may not be current. Keep the old configuration and note when it last updated successfully; don't clear the list right away. Then sign in to the Account Overview, make sure you're in the right account, check your plan status and remaining data, and retrieve the import link for your current client from the panel.

If you import by copying and pasting, check for spaces or line breaks at either end and make sure you copied the full link. When transferring between devices, use the method provided in the panel rather than sending the subscription link through a public clipboard service or group chat. The subscription URL is a credential; anyone who sees the full link may be able to use it. Don't include the full URL, a QR code containing credentials, or a raw configuration export in a support ticket. Check whether the client printed the full request URL in its logs before describing the error. If you think the link was shared, ask through the panel or a support ticket how to update the entry and handle the old configuration.

Choose the next step based on where the update fails

If the update times out, first check whether the panel opens in a browser, then see whether the client's subscription request depends on a route that has stopped working. A successful browser sign-in doesn't mean the client uses the same access path. Note how the update request connects, then reproduce it on your personal network and another network you're authorized to use without changing the configuration. If the client says access was denied, the link expired, or authentication is required, retrieve a fresh link from the panel and check your account status. Don't guess at permissions by refreshing repeatedly or adding URL parameters. For certificate warnings, check the time and network authentication; don't bypass certificate checks.

If the error occurs while parsing or importing, check that the client came from the download page in the panel and that the configuration type is supported by the app you're using. A successful browser download doesn't mean the client can read the content; the response may actually be a login prompt or network authentication page. Don't upload the file to a public online converter or paste a full export into a temporary sharing service. Keep the old configuration and follow the import steps in the Quick Start Guide. Once import succeeds, check that the new entries show selectable regions and routes.

Verify the update, not just the success message

The client may store configurations from multiple sources. After a successful update, check that the active entry is the one you just updated, then check whether the update time, route list, and selected route have changed. If the list contains entries but appears empty after filtering, clear the client's filters first; don't delete the subscription by mistake. If a route disappears after an update, note its name and connect using a route that remains in the list. Don't edit the old configuration manually to keep connecting to an unknown address. If the same account updates successfully on another device, keep that comparison and focus on the failing device's import method, client source, and network.

If the correct account can't retrieve the subscription on different networks or devices, or the panel status repeatedly conflicts with a client permission error, include the update time, operating system, failure stage, and panel status in a support ticket. Provide account identification in the panel only as needed. If payment proof is required, share only the relevant details in the ticket and hide unrelated transactions. If the old configuration still works, mention that too so support knows the issue is with refreshing it, not the initial connection.

App Routing

Only One App Isn't Using the VPN

A working browser doesn't mean every app uses the same path

First identify what fails in the target app: the sign-in page won't open, content won't load after sign-in, only syncing fails, or an external check says the app isn't using the expected exit. Record what happens in the desktop app, browser version, and other apps you know work. Browser access confirms that the browser's path works, but a desktop app may use its own proxy settings, system network interface, or separate background process. A sign-in window may open in the system browser; signing in successfully doesn't mean data requests use the same path after you return to the app. Use the exact error to distinguish a connection failure from a business permission denial.

Check whether the client is using rule-based routing, a system proxy, or device-tunnel mode. Interface names can vary by version, so use the modes actually available in your client. A system proxy doesn't require every app to use it, and whether a device tunnel covers a particular request depends on the client configuration and local policies. If the client shows request logs, reproduce a public request that contains no private information, then check whether its domain or app appears at that time and which route rule matched. If there's no log entry, it only means the current view didn't capture the request; that alone doesn't prove the app bypassed the tunnel.

Check app settings and connection reuse

If a desktop app has its own proxy settings, check whether it's set to follow the system or still has a manually entered proxy address. In manual mode, use only the address and protocol shown by your current client. Don't copy someone else's port or expose a local proxy listener to devices that don't need it. Work browsers, command-line tools, and editor extensions may each use different settings; a running process may also keep settings it read at launch. Save your work, restart the target app, and repeat the same action rather than only disconnecting and reconnecting the client. Change one thing at a time to identify what's choosing the route.

If the client supports app inclusion or exclusion rules, check how the allow and exclude lists interact, and whether a separate sign-in component or helper process makes the failed request. Multiple related processes don't mean you should add every program to a rule. Start with a narrow, reversible change. Keep existing policies for sensitive apps such as internal services, device management, and payments; don't use them as test cases. If you briefly switch to a broader mode for comparison, first confirm that device policies allow it and close sensitive apps not involved in the test. Restore the original mode afterward, and treat the comparison as diagnostic evidence, not a permanent fix.

Distinguish network routing from app permissions and service policies

An app may connect to separate services for authentication, updates, and downloads, so testing only its home page isn't enough. If an error occurs while syncing content, note the type of operation and check whether the app mentions account, region, or organization permissions. If the request definitely uses the selected route but the service still returns an explicit access restriction, check that service's terms or contact its support team. Don't add unknown rules or disable certificate checks. If only links opened inside the app fail, check whether they use an embedded browser or the system browser; each may have different proxy or DNS settings.

In your support ticket, include the client's current mode, target app, failed action, browser comparison, and whether switching routes or restarting the app changed the behavior. If you need to attach app logs, include only the lines around the error and remove access tokens, project paths, and internal domains. If your organization manages the relevant settings, note which options you can't change so support can help without altering device policies.

Domain Resolution

DNS Issues: Failed, Incorrect or Slow Lookups

Separate DNS resolution problems from connection problems

DNS resolves a domain name to an address used to connect. A browser saying it can't find a domain may mean the DNS request failed; if resolution succeeds but the connection times out, investigate the route to that address or the destination service. First check the spelling, then compare with a public domain you can normally access. Don't use the returned address instead of the original domain: one address may host multiple sites, and secure connections need to verify the certificate against the domain name. Accessing a site by address can fail even when the site works normally, so that alone doesn't prove the DNS result is wrong.

If you have access to a command line, run the query below before and after connecting, and compare the results locally. The command uses the device's current default lookup path; the output often shows the responding server and returned addresses. If the command isn't available, skip this step rather than downloading an untrusted lookup tool. Use a public example domain, not an internal company domain, for comparisons across networks. If the query returns an address but the browser still reports a domain error, compare the browser's and system's DNS behavior instead of switching routes at random.

nslookup example.com

Look for differences in results and settings

DNS output only tells you about the lookup step
ResultWhat it meansHow to check again
Query timed outThe client didn't receive a DNS response in timeOn the same network, compare before and after connecting and note whether the default DNS server changed
Domain doesn't existThe DNS service reports that the queried name doesn't existCheck the spelling, then compare with the result for another public domain
Address returnedThe query received a response; this doesn't mean the website is reachableCompare the target app's error with access to a public website

If the command-line query succeeds but the browser doesn't, check whether the browser uses its own Secure DNS setting or is restricted by an organization policy. Also check whether the client handles system DNS queries. Different tools may use different caches and resolution paths, and returned addresses can vary by region and service routing. Don't assume different addresses mean a leak or tampering. If you've manually set a DNS resolver on a personal device, record its current value. If you're authorized, temporarily restore the network's original setting and query the same domain again. Don't copy DNS addresses from unknown sources or replace internal DNS on a managed device.

Cache, local network names, and fallback

After switching networks, an old DNS result may remain in the app or system cache, causing occasional issues with only some domains. Close and reopen the target app, then try the same public domain again. If the system has a built-in way to clear its DNS cache, you can use it after recording the original results. Don't reset the browser, system network, and router all at once; that makes the results hard to compare. Printers, file shares, and company services on a local network may use names resolvable only on a specific network. If public domains work but internal names don't, reconnect to the relevant network and ask its administrator rather than sending internal lookups to a public DNS service.

When checking which resolver handled a request, distinguish where the lookup went from where the webpage's traffic exited. A difference between the web exit and DNS service doesn't necessarily indicate a problem; browser-specific resolution, system policies, and routing rules can all cause it. If the client is expected to handle DNS but repeated queries for the same public domain on the same device and network give conflicting results, submit both sets of results from before and after connecting. Note whether the app has its own Secure DNS setting and whether the system is managed. Share only the necessary lookup logs, and hide internal resolver addresses and private domain names.

Account and Alert Source

“Device limit exceeded” message

Identify which layer is showing the message

VPNHaiLian allows unlimited simultaneous devices. If you see “Device limit exceeded” or a similar message, note whether it appears in the user panel, the client's connection screen, system network settings, or an open third-party app. The message alone doesn't establish that VPNHaiLian has a device limit, nor does it rule out an incorrect alert. Record what you were doing beforehand, such as signing in, importing a subscription, connecting the VPN, or starting video playback. If the system says an old VPN configuration is in use, focus on switching configurations on this device rather than how many people are online at home.

If the message appears only in a video, collaboration, or other app, while the same device can still access other public services, check that app's device management, sign-in status, or concurrent-use policy first. Those alerts are separate from your VPN subscription. Don't rush to sign family members out of their devices or change your VPN plan. Check which service account was in use and whether you were signing in or playing content. Some apps may reuse an old sign-in session when multiple people share a page or device. Before signing out, make sure your work is saved and you can sign back in.

Compare devices before removing any configurations

If the client shows the alert, note the affected device's operating system, client source, current configuration, and update time. Open the Account Overview to check your account and subscription status, then compare the working and affected devices on the same network, using the same route and task. If only a new device is affected, check whether it imported the wrong configuration, is still using an old account entry, or hasn't completed system authorization. If both devices show the alert, note where each one displays it; the same wording doesn't prove it comes from the same layer. Don't delete a working device's configuration before you've recorded the comparison.

If a personal device has both work and personal VPN configurations enabled, check which one the system selected and who manages each configuration. Conflicting configurations on one device aren't an account's simultaneous-device count. Disconnect an old connection you are authorized to manage through the app, then select the correct configuration. Don't remove organization-required profiles or clear all system network settings. If your account still works but the panel itself shows an unexpected alert, save a screenshot and ask through the Support Ticket Panel; there's no need to change plans as a test.

Wrap up with a reproducible report

Structure your support ticket as “Where it happened, steps taken, actual result, comparison result.” Say whether the alert came from the system, client, panel, or a third-party app. List the steps that led to it and the point where it appeared. Quote the exact error and include the time and time zone. For comparison, say whether another device worked and whether it used the same network and route. If you reimported a subscription or updated the client, describe the change alongside its result. Screenshots should show only the alert and necessary parts of the interface; hide passwords, subscription links, QR codes, and unrelated account details.

You can describe plan status, payments or refunds, and network problems separately in a support ticket to avoid reporting a billing issue as a route failure. To check current plan allowances, see Plans & Pricing. VPNHaiLian offers a 14-day no-questions-asked refund; see the Terms of Service for details. For common questions about accounts, connections, speeds, or billing, visit the Support Center. If you haven't completed the initial import, return to the Quick Start Guide to finish connecting and verifying your setup, then follow the relevant section of this guide.

Start Free