2LVPN Technical Guide

VPN Troubleshooting Guide

If you haven’t installed the app, imported a configuration, and connected for the first time, start with the setup guide. If you’ve used the service before and are now having trouble, find the matching symptom on this page. The goal is not to change every setting, but to identify where the problem starts while keeping a way to restore your original settings.

Note the exact error message, when it occurred, and your time zone before testing. Change only one thing at a time—your network, route, or app—and repeat the same action. Don’t also update the client, change the system proxy, and switch DNS during testing. Otherwise, even if the problem goes away, it will be hard to tell which change helped.

Can’t Connect at All

First, check whether the failure happens before or after connecting

After tapping Connect, check whether the client shows no available routes, stays on Connecting, or briefly shows Connected before dropping. If no routes are available, check your account and subscription first; switching networks won’t replace importing a configuration. If it stays on Connecting, note the current route and network, then wait for the client’s result instead of repeatedly toggling the connection. If the connection succeeds but you then can’t open websites, go to Websites Won’t Load. Noting the order in which errors occur is more useful than simply writing “it doesn’t work.”

Disconnect the client and confirm that your internet connection works. In a browser, open a public page that normally works on this network and refresh it to rule out a cached page. If other devices on the same network can’t open it either, first check whether the Wi-Fi actually has internet access. If a public network displays a sign-in or access page, follow the provider’s instructions and try again. On a work-managed network, ask the administrator about access rules; don’t disable a required proxy or security software yourself. Without a working base connection, trying other routes won’t produce useful results.

Run comparable tests with the same account

Once the base connection is working, check your account and service status in the user panel. Make sure the subscription in the client belongs to the current account, especially if you’ve configured the account on another device, restored a backup, or kept a configuration with the same name. The panel and client don’t show the same data: the panel reflects account status, while the client may still have an older imported configuration. A route name doesn’t mean the configuration is up to date. If the panel shows an issue with your service status, resolve the account issue first. If the panel looks normal but the route list is empty, follow Subscription Update Failed to check the update process.

If your account and route list look normal, try another available route on the same network without changing the client mode. If only one route fails, note which route failed and which one connected, then check its region and type in the route list. If several routes fail, connect the same device to another permitted network and test the original client and route again. If it fails on one network but works on another, the difference is related to the access environment—but that doesn’t establish whether the cause is the router, network policy, or connection path. If another device works on the same network, compare the client settings and system messages on both devices before considering a reinstall.

Check system prompts before deciding whether to submit a ticket

If the system asks you to approve a network configuration when the connection is first set up, verify that the request came from the current client and then approve it in the system dialog. A permission request denied by the system is different from a connection refused by the service. If another network tool is running on your device, quit the one you control and test again; closing its window may not stop its background connection. Don’t remove configurations from a managed device without permission. Resetting the entire network is also a poor first step: it can erase working settings and remove useful comparison conditions.

If the base connection works, the subscription is valid, and the system permits the connection, but available routes still fail across different networks—or the client exits at the same stage every time—describe the issue in a user panel support ticket. Include your device’s operating system, the client version shown in the app, route, time and time zone, where the connection stops, and what happened after switching networks or routes. If the system displays a prompt, copy its exact text; that’s more useful than saying “there’s a permissions issue.” Capture only the relevant part of the screen and hide account details, network identifiers, and notifications.

Connected, but Websites Won’t Load

Determine whether the problem affects the whole device, one browser, or one website

When the client says Connected, it means the client reports that a connection has been established. It doesn’t mean every app is using that connection or that a website will accept the request. Keep the current route and open both a public page that normally works and the page that’s failing. Then try the same pages in another browser on the device. If neither browser can open any pages, check the system’s network path. If only one browser fails, check its proxy settings or extensions. If only one website fails, note the message it returns; don’t assume the entire route is down because of a single site.

When retesting, use the same public page rather than comparing a logged-in page with a website’s homepage. If the homepage loads but a page fails after login, the issue may involve the account session or the site’s policies. If one browser works and another gets stuck loading, an extension may be blocking scripts rather than the site being unreachable. You can try the public page in a private window to compare the effects of extensions and old sessions, but private browsing doesn’t necessarily disable every extension or organization policy. Clear data only for the affected site if it helps narrow down the issue; clearing the entire browser may sign you out of other websites.

Choose your next step based on the error

If the message says the domain can’t be found, go to DNS Issues and check whether name resolution is failing. If the connection times out, compare the same destination on another route first; don’t assume every timeout is a DNS issue. If the destination returns a refusal page, at least one service has responded. Check the scope indicated by the message—such as account region, sign-in status, or access rules—instead of repeatedly rebuilding the system network. If the page loads but videos, images, or uploads fail, note the specific resource or action rather than simply writing “the website won’t load.”

For a certificate or secure connection error, check the system date, time, and time zone first, then confirm the browser address is correct. A public network’s access page can also affect the first connection; disconnect the client and follow the provider’s instructions to complete access. Even if the certificate error appears only with the client enabled, don’t choose to continue or install a certificate from an unverified source. Keep the browser’s exact error text. If the device is managed by your organization, ask the administrator about its certificate or network policies. Don’t enter account or payment details on an error page until you know why the error occurred.

Check proxy mode and keep a way to restore the previous settings

Check whether the current configuration affects only apps that follow the system proxy or whether the client handles more traffic. Options vary by platform and client; refer to the app interface and the setup guide. Check whether the system proxy still points to a local app that has been closed. If the current client set the proxy automatically, use its own disconnect and quit controls to restore the settings, then check whether the browser works again. Change only settings you added yourself and know how to restore. If a kill switch is enabled, continued blocking after disconnecting may be expected behavior—not necessarily a network failure.

A support ticket is appropriate if two browsers and multiple public websites fail while the connection is enabled, recover immediately after disconnecting, and still fail on other available routes. Include the network type, client mode, route, error text, time and time zone, and the results before connecting, after connecting, and after disconnecting. If only one website errors, include its public domain and the steps that fail; don’t include a full URL with session or account parameters. If the issue occurs only in a managed browser, also check with your device administrator about browser policies.

Slow Speeds and Peak-Time Lag

Describe what’s slow before comparing under the same conditions

A slow first page load, a download that slows halfway through, and choppy call audio are different symptoms. A slow initial load may point to domain lookup or connection setup. Slow ongoing downloads are more about throughput, while choppy calls are more sensitive to fluctuating latency and brief packet loss. Choose a repeatable task, such as opening the same public page or playing the same content, and note whether the delay occurs before loading or during use. Don’t compare different sites, files, or video quality settings, and don’t treat the client’s latency figure as a measure of the actual app experience.

On the original network, pause large file syncs, system downloads, or cloud backups on your device, then check whether the problem improves. If possible, test the same device over a wired connection or closer to the Wi-Fi access point, without changing anything else. If common public services are just as slow when disconnected, check the local connection or congestion on the shared network first. However, if a destination is accessible only while connected, the speed of a different service after disconnecting isn’t a valid direct comparison. A better test is to keep the destination the same, change the route or access network one at a time, and note what changed.

Compare routes for your use case, not by a single number

Check the available regions and route types in the route list. Direct routes, relay routes, and IEPL dedicated lines are types of routes, not a fixed ranking of app performance. Direct-route performance depends on the actual access network and path to the destination. A relay changes part of the path but is still affected by local access. A dedicated line doesn’t guarantee a faster response from the destination site. On the same network, test different routes with the same task. Check whether pages load reliably, videos keep buffering, or calls remain clear, then keep the route that works best. If your use case requires a specific region, compare routes within that region first.

If lag tends to occur in the evening, keep one record from a normal period and one from a problem period, using the same device, network, route, and destination where possible. During the problem period, try another route first. If performance clearly improves, note which route worked better at that time. If several routes perform similarly, compare another access network at a similar time. If the other network is stable, investigate the access environment further. If both are slow but only for one destination, the destination service or the path to it may be the cause. Use a fixed video quality when testing buffering, so automatic quality reduction isn’t mistaken for a recovered connection.

Keep data usage separate from network performance

If the client or panel also shows a data usage alert, check the plans page and your personal panel. Monthly subscription data resets each month on the activation date; data add-ons never expire and remain available until used. Don’t use the start of the calendar month to guess your reset date, and don’t assume a change in speed means you’ve used up your allowance. If the panel and client show different information, check the account and when each was last updated. A task getting faster after switching routes doesn’t mean you need a different plan. Compare data allowances only if your actual usage doesn’t meet your needs.

You can submit a support ticket if the same task repeatedly lags at similar times and switching routes or networks produces a clear difference. Include the access method, client mode, public destination domain or app name, time and time zone, and whether background transfers were running. Provide one normal and one affected test. There’s no need to include a full call or playback history; a description such as “started normally, then buffered several times during playback” is enough. If multiple ordinary websites are just as slow when disconnected, report the underlying connection issue to your network provider first.

Frequent Disconnects and Mobile Background Drops

Match disconnect times with what you were doing

First, determine whether the client actually changed to a disconnected state or whether it still shows connected while the app you’re using stops working. Note the last action before the problem: locking the screen, switching apps, the device going to sleep, leaving Wi-Fi coverage, or nothing in particular. When you notice a drop, check the client and system network status before reconnecting; otherwise, you may lose the trigger. If the same action reliably reproduces the issue, investigate system networking or background behavior first. If the device stays awake but still disconnects on the same network and route, test for differences between routes.

For a comparison, keep the device on the same network and route, and test the client once in the foreground and once in the background. Then test locking the screen on its own. When you return, check whether the client is still connected and retest a public page that worked earlier. Don’t change the screen state, network, and power-saving mode all at once; each can produce the same apparent symptom. If the issue occurs only when the network changes, keep the route the same and test switching from Wi-Fi to mobile data separately. An existing session may be interrupted during a network handoff, so check the client’s reconnection behavior separately from whether the app recovers.

Find settings for your platform instead of copying another device’s menus

Background and sleep checks by platform
Platform Check first Comparison test
Android App battery management and background activity restrictions Compare the connection with the screen on and after locking it, on the same network
iOS VPN status in system settings and changes when switching networks Test locking the screen without switching networks, then test a network change separately
Windows / macOS / Linux Power management and network recovery after waking from sleep Compare locking the screen with waking the device from sleep

Android battery management menus vary by device. If you’ve confirmed that background activity is restricted and you have permission, adjust the setting for this client only, then repeat the same test. You don’t need to remove power-saving restrictions for every app. On iOS, first check whether the system still shows the VPN as connected; don’t assume that “it works again when I open the client” means Background App Refresh is disabled. On desktop, distinguish the screen turning off from the system entering sleep. If the base network hasn’t recovered after waking, wait for it to reconnect before deciding whether the client needs to reconnect manually.

Rule out connection conflicts and note how to recover

Check whether another network tool you control automatically takes over the connection at startup, after waking, or when the network changes, or whether the same client has two startup entries. Disable only entries you set up and know how to restore. Don’t let multiple tools repeatedly compete for control of the system, and don’t remove configurations installed by your organization for testing. If you’re saving or uploading work, save your progress before changing settings; network testing shouldn’t risk losing work. If the drop happens only on one Wi-Fi network, check the signal, access point handoffs, and whether a public network session has expired.

If the connection also drops repeatedly while the screen is on and the device stays on the same network, keep the destination the same and try another route, then compare a different access network. A repeatable drop after locking the screen, sleep, or a network change is also worth reporting. Include the platform, client version shown in the app, system power or background settings, time and time zone, whether the connection recovers automatically, and whether you need to reopen the client or simply wait for the network to reconnect. If the client still shows connected but only one app fails to retry, also follow Connection Issues in One App to test the app session separately from a dropped tunnel.

Subscription Update Failed

First, distinguish account, retrieval, and import problems

Can’t find an active subscription in the user panel, can’t download the configuration in the client, and can’t parse a successfully downloaded configuration are problems at different stages. First sign in to the user panel and check the current account and service status, then check what the client reports during the update. If the panel itself won’t open, use the steps in Websites Won’t Load to test basic access. Don’t judge subscription status from an old client cache. If you can access the panel but the account status isn’t what you expected, check that you’re signed in to the account used to activate the service. A remembered configuration name alone doesn’t tell you which account it belongs to.

If only the update fails but the old configuration still connects, don’t delete it first. Note the last successful update time, the error message, and the current configuration options so that “update failed, but still works” doesn’t become “no configuration to connect with.” If the client has multiple configurations, make sure you’re using the update entry for the current account, not an archived one with a similar name. Don’t test by replacing your subscription with someone else’s. Even if it connects, that won’t explain why your own account or configuration failed, and it will make later troubleshooting harder.

Retrieve it again from the panel; don’t paste it into third-party tools

Retrieve the subscription for your current client from the user panel and follow the setup guide to choose an import method. Make sure you’re importing it as a subscription configuration, not opening it as an ordinary web address, a single route, or a local archive. When copying it, check for extra spaces, line breaks, or other text. Don’t try to fill in missing characters, or paste the link into a search box, online parser, or chat. If the client lets you keep the original configuration and create a new one, and lets you choose which one to use, update and test the new configuration before deciding whether to remove the old one.

If the client reports a timeout, note whether it was connected during the update. Retest on a working base network only when doing so won’t interrupt an active task. The path used for an update may differ from the one used for everyday browsing, so being able to browse doesn’t prove the client can retrieve the configuration. If the update works on another network, check whether the original network requires an access confirmation or has a connection issue. For an authentication or access-denied message, check the panel status and retrieve the subscription again. If the client says the content can’t be parsed, confirm the import format, then report the device and error. Don’t edit configuration fields yourself.

Verify the update instead of treating the success message as proof

After the client says the update is complete, check whether the configuration’s displayed update time changed, whether the route list is available, and whether the newly updated configuration is selected. Pay close attention if the list contains similarly named entries. Select an available route and test a public page you can reliably access. If the configuration updated but won’t connect, follow Can’t Connect at All to diagnose it separately: retrieving a configuration and establishing a route connection are different checks. If the error occurs only during automatic updates, note whether the client was in the background, whether the device had just woken, and whether a manual update works.

A support ticket is appropriate if the panel status is normal, you’ve retrieved the subscription again using the guide, and the same error persists on a working network. Include the platform, client version shown in the app, import method, stage of failure, time and time zone for the last successful update and the current failure, and the results of manual updating and testing on another network. Crop screenshots to hide subscription details, QR codes, and account information. Don’t paste log lines containing credentials or full URLs. If you think the subscription link has been exposed, stop sharing it and check the panel for a reset option, or ask support how to proceed.

One App Can’t Connect Through the Proxy

Confirm that the issue affects just one app

If a browser works on the same device but a desktop app doesn’t, first open the app’s public service page in a browser. Then note whether the app gets stuck at startup, sign-in, syncing, or data transfer. A working web page doesn’t prove that the app’s sign-in or media endpoints are working, but it provides a useful basic access comparison. If the app has a web version, sign in with the same account and compare the same feature; comparing only the homepage isn’t enough. If both versions fail at the same step, check the service status, account messages, or app permissions before changing global network settings.

Then compare behavior before and after connecting. Save any unsent work, fully quit the app, reopen it, and repeat the same action to avoid reusing an old session from the previous network. Browser extensions usually affect only the browser, and not every desktop app follows the system proxy. If the app has its own proxy setting, note the original value and check whether it follows the system, uses its own proxy, or explicitly connects directly. Change it only if you understand what it does and are allowed to do so. Don’t enter a proxy address from an unverified source.

Check whether the app is covered by the current configuration

If the client supports per-app or rule-based traffic handling, check whether the target app is excluded, whether the expected configuration is enabled, and the order in which its rules are applied. Matching by domain doesn’t necessarily handle an entire app the same way: sign-in, messaging, files, and media may use different domains. Use the information available in the client to check how the domain for the failing feature is handled. Don’t broaden proxy coverage for every app permanently just to fix one feature, or overwrite several existing rules at once.

If the client offers different traffic-handling modes, compare them one at a time on a device and network you control, following the setup guide. Restore any changes you don’t need after testing. If a mode isn’t available, check for a system permission issue or conflict with another network tool rather than disabling security controls. Follow your administrator’s requirements for work apps, managed devices, and organization-managed networks. If the app displays a region, account, or device restriction, treat that as an app policy issue, not a proxy forwarding failure. Switching routes doesn’t change your account eligibility.

Retest each feature and note what still works

Games, calls, and meeting apps may use different transport methods from web requests. If messages work but voice doesn’t, or sign-in works but a session drops, at least some features are working; narrow the issue down to the failing step. Keep the same network and route while testing sign-in, messaging, and the affected feature separately, then change only the route and test again. If the issue occurs only after switching networks, fully quit and reopen the app once, and note whether that helps. Don’t change routes while also changing the app account, permissions, or region settings.

If multiple apps fail, go back to Websites Won’t Load or DNS Issues to check what they share. You can submit a support ticket if only one app fails while connected, the issue persists on other available routes, or the client’s handling information doesn’t match the selected mode. Include the app name, platform, client mode, affected feature, time and time zone, browser comparison results, and steps to reproduce the issue. If you keep logs, include only relevant entries; don’t share chat content, private file names, or session credentials. If the app reports the same account error on different networks, contact the app provider’s support team instead.

DNS Issues and Domain Resolution

First check whether the domain really failed to resolve

DNS resolves a domain name to the address needed to reach it. If the browser says “server not found” or shows a similar message, check the spelling first. Then use the same browser to open another common public domain and try the affected domain in another browser. If just one domain fails, the cause may be a typo, a domain record, or the service itself. If several domains fail together, check the shared resolution path first. If the page opens but shows an error after sign-in, or reports a certificate problem, don’t change DNS based on that message alone.

On the same device, compare the same public domain while disconnected and connected, and note whether it fails in both states. If it also fails while disconnected, check the base network and system settings first. If it fails only while connected, note the route, client mode, and affected app, then try another available route. If only the browser is affected, check whether it uses its own secure DNS setting or has a resolution method set by an administrator. Browsers, systems, and clients may use different resolution paths, so success in one place doesn’t mean another app got the same result.

Look up a public domain and understand what the result tells you

If nslookup is available on your system, you can run the query below in Windows Command Prompt or a macOS or Linux terminal where the command is installed. It queries a public example domain only, requires no administrator privileges, and doesn’t change any settings. Note the results while disconnected and connected, then replace the example domain with the affected public domain for comparison. Enter only the domain name, without a protocol, page path, or query parameters. If you don’t have this command, compare results in a browser and the system network settings instead. There’s no need to install unfamiliar software for troubleshooting.

nslookup example.com

If the query returns an address, that means the resolution path used for that request returned a result; it doesn’t prove the browser or another app can connect to the destination. If it returns a non-existent domain, check the domain and query environment first. A timeout means the query didn’t get a response in time, not that the domain doesn’t exist. Different addresses from two queries aren’t necessarily a problem; public sites may return different addresses based on network location. Don’t paste a resolved address into the browser as a substitute for certificate and domain checks. A basic command output alone can’t prove whether DNS went through the client or determine whether there was a leak.

Restore your original settings, then check which layer is in use

If the issue started right after you changed a setting, restore the last change and test again. Check whether the system gets DNS settings automatically, whether the browser has its own DNS configuration, and whether the client handles DNS in the current mode. Don’t clear the cache, change servers, disable secure DNS in the browser, and switch routes all at once. If an administrator set the original policy, leave it in place and ask them about it. On a device you manage, restore the last known working settings, then quit and reopen the affected app to avoid using an old cache or connection. Only follow system documentation to clear a cache if you’ve found evidence that the cache is involved.

If several public domains repeatedly fail to resolve while connected but work when disconnected, and the same happens on different available routes, send support results for a public example domain, the network type, system platform, client mode, time and time zone, and whether the browser and terminal results match. Don’t share full output if it includes internal domains or private addresses. If the base network has the same issue, report it to the network administrator or provider first. If only one public domain is affected, keep the domain and error text and check whether the site has posted any information.

Device Limit Alert

First identify which interface displayed the alert

2LVPN doesn’t limit the number of devices connected at the same time and supports Windows / macOS / iOS / Android / Linux. If you see a “device limit exceeded” alert, note where it appears: the client’s connection screen, a system permission prompt, the 2LVPN user panel, or the app you’re trying to access. A target website’s playback device rules, conflicts between network tools in the operating system, and your subscription status are separate issues. 2LVPN’s simultaneous device policy doesn’t mean those alerts will all disappear. Don’t switch plans just because a message mentions devices.

If the alert comes from the target app, check whether it appears during sign-in, playback, or management of trusted devices. Try the app with an account on a device that worked previously, and open another ordinary public page to confirm that the client connection still works. If only the target app rejects an action, follow that app’s account or device guidance. Don’t clear other devices’ configurations just to dismiss the alert, and don’t mistake the app’s error for a 2LVPN connection limit. If the messages look similar, include the interface title and exact error text in your screenshot to make the source clear.

Cross-check a working device against the affected one

If the alert comes from the client or panel, first check the account, subscription status, and configuration source in the panel. After a device migration, backup restore, or account switch, the client may still have an old configuration. Use a working device as a reference without changing its setup. On the affected device, check and refresh the configuration by following Subscription Update Failed, then test the same available route and public page. If the devices aren’t on the same network, note the difference; don’t attribute the entire issue to the device limit when one has been working for a long time and the other has just changed networks.

If the affected device shows the same alert when it connects on its own, the number of devices connected at the same time doesn’t explain what you’re seeing. Check whether the client is running multiple configurations or whether another network service is connected in the system. To compare using other devices with the affected device on its own, choose a time that won’t disrupt your work and briefly test after disconnecting normally. Don’t sign out of every account or clear all devices. Even if the issue temporarily goes away, note the sequence of events; what looks like a device-count change may coincide with a configuration refresh, network switch, or old session ending.

If you suspect an account issue, protect your access first

If you find a configuration you don’t recognize or think credentials were accidentally posted publicly, don’t share the suspicious link with anyone for testing. Check your account status in the user panel first. If you think your password was exposed, use the account’s security settings. If a subscription link was exposed, separately check whether it can be reset or ask support; changing your sign-in password doesn’t prove the subscription link is invalid. Before taking action, check whether existing devices will need to import the configuration again, and confirm recovery on each one to avoid interrupting working connections.

If the panel or client continues to show an alert that conflicts with the unlimited device policy—especially when the subscription is valid and the issue also occurs with a single device tested on its own—submit a user panel support ticket. Include the platform, client version shown in the app, time and time zone, where the alert appeared and its exact text, whether the configuration was updated, and comparison results from working and affected devices. Don’t submit a complete device list or any sign-in credentials. If you’re not sure which product the alert came from, check the FAQ or VPN FAQ for Beginners first. Account status, data usage, and using multiple devices are separate things to check.