CONNECT / SESSION SETUP
Can't connect: check your network, then your route
Pinpoint where the connection attempt gets stuck
Getting stuck at “Preparing,” being asked to grant system permission, and seeing a handshake timeout are different symptoms with different checks. If the client is still preparing, it hasn't tried a route yet: check that your subscription has loaded and that the list contains selectable options. If the system asks to create a VPN configuration or allow a network extension, grant permission using an account authorized to do so. Treat a connection timeout as a route issue only after the client has started trying the selected route. Don't lump an inaccessible account page, an empty list, and a failed handshake together as “the node is down”—that can send you down the wrong path.
Pause the client and check that the network your device is connected to actually works. A lit Wi-Fi icon only confirms a wireless connection; it doesn't mean internet access is available. In a browser, try a site you can normally access on that network. Hotel, campus, and guest networks may require you to sign in through a captive portal first. Complete that step before testing the connection. If ordinary pages won't load either, check that your device has valid network settings or contact the network administrator. Reimporting your subscription won't fix an underlying network problem.
Tell system permissions, configuration conflicts, and route differences apart
Once the underlying network is working, check system network settings for another VPN or standalone proxy handling traffic on the same device. Pause only configurations you manage and are allowed to pause; don't change settings managed by your employer or school. On Windows, check whether the system proxy still points to a stopped app after the client exits. On macOS, check whether the network extension is allowed to start. For macOS permissions and compatibility checks, see macOS Client Compatibility and Network Extension Guide. Note the original settings before making changes, then restore any unrelated settings after testing.
Keep the device and network fixed, then try a different route currently available in the client and wait for the connection attempt to finish. If the alternative route connects, switch back and check whether the original problem recurs. If both time out, keep one route fixed and test on another network you're allowed to use. If only one network fails, check its authentication status or access policy. If only one route fails, note the labels of the failed and working routes. If you can't establish a session on either network, check your user panel and local subscription status before considering a support ticket. This helps avoid mistaking an account issue for a network issue.
Record the full error before changing settings. Distinguish “system permission not granted,” “no routes available,” and “timed out after connecting” rather than leaving out the stage where the client stopped.
Don't bypass certificate or time warnings
If an error says a certificate is expired, not yet valid, or failed verification, first check the device's date, time, and time zone, and make sure time synchronization is working. If the error persists, note where the warning appears: on the user panel website, during a subscription update, or while the client is establishing a session. These stages may use different connections. Don't disable certificate checks or install root certificates from untrusted sources. If the issue appears only on a managed network, ask its administrator whether there are known access restrictions. If it also happens off that network, save the error for support to review.
If ordinary internet access works, the client has permission, the panel shows an active status, and multiple routes still fail across different networks, submit a support ticket instead of repeatedly reinstalling. Include the device platform, OS and client versions, test time and time zone, network type, route labels, and the exact error. Note which checks passed. If another device connects, include it as a comparison—but don't assume the first device needs reinstalling. The difference may already narrow the issue down to system settings or client startup.
WEB / REQUEST PATH
Connected, but websites won't load: check where requests go
Check how much is affected before changing global settings
A connected status usually means the session is established. It doesn't mean every browser request uses that session or that the destination has returned a page successfully. In the same browser, try a regular site you can normally access, an international site that works, and the failing page. Note which ones load and whether the failure happens on the first visit or after signing in. If all pages fail, check the system proxy, network access, or DNS. If only one destination fails, check its access requirements, account status, and the routing result for its domain.
Read the error on the page, not just the blank screen. “Server not found” usually points to name resolution. “Connection timed out” means the request may not have reached its destination, but that message alone doesn't identify where it failed. An account or region notice naming the site means at least one part of the service responded. Don't proceed past a security certificate warning or switch to an unencrypted connection to make it disappear. On a managed device, share the warning and circumstances with the administrator. If the same site fails on only one route, note the difference for support.
Compare the actual exit route with the page request
Open IP Lookup in the same browser and compare the visible exit address before and after connecting. First check whether the lookup page's request falls within the routing rules you want to test. Its result shows the route used for that lookup only; it doesn't prove that a destination domain, desktop app, or other domain on the same page uses the same exit. If routing rules match only certain domains, an unchanged lookup result may be expected. Conversely, even if the result changes, an earlier matching rule may send the destination domain another way. Use any local rule-match details available in the client to help assess this.
If the homepage loads but sign-in, images, or video fail, note exactly which action triggers the problem instead of describing everything as “the website won't load.” A site may use different domains for its APIs, sign-in, and static assets. Try a clean browser window or another browser to rule out extensions and cached data affecting that site. Keep in mind that a signed-out window can show whether a page responds, but it can't be compared directly with a signed-in window's account permissions. If you inspect network requests, note only the relevant domains, error types, and steps that triggered them. Don't include full requests, query parameters, or request headers in a support ticket.
An IP lookup compares routes; it doesn't prove that every destination site is reachable. If an error page gives a specific account or region notice, use that as your guide.
Check what recovers before deciding who should handle the issue
Keep the browser and destination URL the same, switch only the route, and make sure both tests use the same session conditions. If the site treats a changed exit address as a new sign-in environment, it may ask you to verify again; that isn't evidence of poor route quality. If only one route times out, keep the comparison details. If the same server-side notice appears on different networks and routes, check the destination service's status and support documentation first. For services such as ChatGPT and Claude, see AI Tools Guide for service-specific access scenarios. A successful sign-in doesn't guarantee that API calls will work too.
If ordinary websites work, the target site repeatedly fails under the same conditions, and you've ruled out browser extensions and local configuration differences, submit a ticket to 8LVPN. Include the failing domain, the action that failed, the exact notice, routing mode, route label, and whether other sites work. If the browser and client seem to show conflicting routes, describe each observation separately and name what you tested. If the destination service explicitly reports an account, authorization, or service-availability issue, contact that service's support first.
SPEED / TRANSFER PERFORMANCE
Slow speeds and peak-hour slowdowns: run comparable tests
Separate slow first response, slow downloads, and persistent buffering
A page that takes a long time to show content, a download that starts quickly but becomes unstable, and a video that repeatedly buffers can have different causes. A slow first response may involve name resolution, connection setup, or server processing. For sustained download speeds, compare the same destination within the same time window. Buffering may relate to transfer instability, video quality, or the player's buffering strategy. A client probe describes only the route and time it tested, not the end-to-end performance of the target app. Don't compare content from different sources or at different quality levels.
Pause cloud sync, system downloads, and background transfers you control. Keep the device, network, and test target the same. If other devices at home are transferring data, note that too; the connection can be busy even when this device is idle. Comparing a wired connection or a device near the wireless access point can help identify interference. If local services on the same network are affected too, address the wireless connection, access point, or upstream network first, then check international routes. Otherwise, an improvement after switching routes may simply reflect a change over time rather than a route difference.
Compare in this order: original route, alternative route, original route again
Around the same time, test the original route with the same target, try another available route, then switch back to the original and repeat. Compare like with like: for example, start a transfer from the same download source and note whether it repeatedly stalls, or play the same video at the same quality and record when buffering starts. Cached pages and prebuffered video can make a second attempt appear faster, so note whether content had already loaded. If testing with real work, don't transfer confidential material for troubleshooting; use a publicly accessible sample that reliably reproduces the issue.
For route options, see Global Routes to compare regions and types such as IEPL dedicated lines, relays, and direct connections. Use the routes currently available in the client as the final reference. A route type describes only part of the transmission path or access method; it doesn't rank every route by reliability for every destination. Switching regions may also cause a service to assign a different content server. If one route is faster, note its region, type, and target instead of generalizing the result to other sites. A route label alone can't tell you whether it's suitable for every real-time activity.
Check whether the problem happens at a consistent time
For peak-hour issues, record when they occur along with your comparison results. On the same network and device, test the same destination during the slowdown and at a normal time. If possible, test another permitted network while the slowdown is happening. If only the original network slows down broadly at a regular time, check for shared traffic or upstream congestion on that network. If ordinary sites work, several international destinations are slow, and an alternative route performs normally, send the details to 8LVPN. If only one video platform or download source is slow, consider its current load and content delivery route too.
When comparing routes, focus on whether the same task completes and whether it repeatedly stalls. Instantaneous readings from different test conditions don't show what caused a speed change.
For everyday use, you can temporarily lower video quality, pause background transfers, or switch to a route that performed better in a comparison, then retest the original route later. For gaming, distinguish input response from dropped frames: local rendering stutter may have nothing to do with the network, while delayed or rolled-back online actions are more likely to warrant a connection check. For how the two types of products differ, see Game Accelerators vs. VPNs. When contacting support, include the time and time zone, network, original and alternative routes, and whether the issue affects initial response, sustained transfer, or video playback. Don't send just one isolated speed-test screenshot.
SESSION / DISCONNECTIONS
Frequent disconnects and background drops: identify the trigger
Check whether the connection actually dropped or the app stopped responding
When the issue occurs, check the client status first, then try another page you know works. If the client clearly shows disconnected, reconnecting, or has exited, start with the session and system service. If the client remains connected but one app says it's offline, check whether that app's connection has expired. Long-lived connections may not survive a network change. Even if the client recovers afterward, the app may not restore its previous session automatically. Note when the issue occurred and record the system network, client, and target app status separately instead of treating them as one.
Test potential triggers one at a time: first use the app in the foreground without moving the device; then separately test waking it after locking the screen, switching between Wi-Fi and mobile data, and making a new request after the connection has been idle. Don't lock the screen, leave Wi-Fi range, and enable battery saver all at once—you won't know which caused the problem. Changing networks alters the device's route, so a brief pause may occur while the connection is reestablished. What matters is whether it recovers automatically once the network is stable, whether you have to reconnect manually each time, and whether other sites load before it recovers.
Check background and network policies by platform
On Android, check the system's battery, background activity, and background data settings for the client. Menu names vary by system and manufacturer, so look for the options actually shown in your settings. Change only options related to this client that you're allowed to modify. First confirm that the app is being restricted, then retest that setting specifically. Don't loosen background permissions for every app just to diagnose the issue. If changing a system setting stops disconnects when the screen is locked, note which setting helped and whether the problem occurs only in battery-saving mode.
On iOS, first compare the system VPN status with what the client shows, then test waking the device from sleep and switching networks separately. The system component that maintains a connection isn't identical to the client interface, and an app disappearing from the app switcher doesn't prove the session has dropped. On a managed device, don't remove organization-installed network settings for testing. On desktop, check whether network access returns after waking from sleep and whether the required system network component has restarted. Test closing the window, quitting the client, and system sleep as separate actions.
Use a timeline to confirm how the connection recovers
A sequence of events is more useful than an isolated error. For example: “Sites worked before locking the screen”; “after unlocking, ordinary sites loaded, the client still showed reconnecting, and the target app said it was offline”; then note which step fixed it—reconnecting or reopening the app. A successful manual reconnect doesn't prove the route issue is resolved; retest under the same trigger to see whether it happens again. If only restarting the client restores service, save relevant error details first so you don't lose the state needed for diagnosis. A brief diagnostic summary is enough; you don't need to collect the entire device event log.
Whether apps continue to use the network during a disconnection depends on device and client settings. Pause tasks that rely on a fixed exit route and resume them once the route is restored.
If foreground use works and the issue happens only in the background, include the OS and client versions, the screen-lock or network-switch action, battery settings, and how the connection recovered. If disconnects also recur without locking the screen or switching networks, compare another route on the same network and test whether another network behaves the same way. If an organization policy forces sessions to stop or restricts background access, contact the device or network administrator. If the issue persists in an ordinary personal setup—repeated disconnections, failed session recovery, or the client exiting—submit a ticket and say whether it happens only on one device.
PROFILE / SUBSCRIPTION CONFIGURATION
Subscription update failed: distinguish download, parsing, and activation
Check the current status in the user panel
A subscription update means the client is fetching configuration. It isn't the same as connecting to a route or signing in to the panel. Open the User Panel Overview and check that you're signed in to the account you're troubleshooting, along with its current plan or data status. If you've just renewed or upgraded, trust the panel's status rather than assuming the new configuration is active because the old list is still in the client. Monthly subscription data resets on the activation date each month; data packs remain available until used and never expire. If you're unsure about available data or billing, see Plans, Pricing, and Data Rules instead of repeatedly importing the subscription.
Subscriptions are available only through the user panel. If you copied an old address before or moved a configuration from another device, return to the entry point for your current account and check it again. Don't share the address with a public subscription converter, paste it into a search box, or send it to support; subscription addresses are sensitive. Before taking a screenshot, check the address bar, content near the share button, and any error message that might show the address. If you think it was exposed, stop sharing it and describe what happened in a support ticket to ask about available options.
Troubleshoot based on the stage where the error occurs
If the client reports a download failure or request timeout, first check whether the current network can reach the user panel. The client's update request may use a different network path. Opening the panel in a browser doesn't guarantee that the client can fetch the configuration. Compare with another permitted network and check that the system clock is accurate. Don't disable certificate verification. If the client reports an authorization error, return to the current account's entry point and check its status. Note the error text; don't try random changes to parameters in the subscription address.
If parsing fails after the download, the content may be incompatible with the client, or the network's captive portal may have returned a sign-in page instead of the configuration. First make sure network authentication is complete, then check the guide for the import method for your platform. If the client lets you keep multiple configurations, leave the old one in place and create a clearly named test configuration from the panel. Don't mix new content into an old configuration you've edited manually. Find platform clients in the User Panel Downloads. You must still sign in to the panel to get your subscription.
After updating, verify which configuration is active
“Update successful” may only mean the configuration was downloaded and added to the list; it doesn't necessarily mean the client has switched to it. Return to the configuration selector and identify the active entry, then check whether the route list changed. If you have multiple entries with the same name, give them different local names first. Then test the connection once and note whether routes that were missing or unavailable can now be selected. If another device has a normal list but this one doesn't, check that both use the same account and the correct configuration, then compare how each client imported and updated it.
Keep the working configuration until you've verified that the replacement updates and connects successfully. Only then remove old entries you no longer use.
If the panel status is normal, you've confirmed the current entry point, and the same update stage still fails on another network, submit a support ticket. Say whether you were updating an existing entry or importing for the first time, whether the error occurred during download or parsing, whether you kept a working configuration, and what happened on other devices. If the error line includes an address, share only the error type. Crop screenshots to show just enough of the interface and status. Don't attach the full configuration file; it may contain subscription credentials, custom rules, and other information unrelated to the issue.
APP / ROUTING SCOPE
One app won't use the proxy: check the routing rules that apply
A working browser doesn't mean an app uses the same route
A web app and desktop app for the same service may use different domains, transport methods, or proxy settings. A browser working through the system proxy doesn't prove that a background process, embedded page, or command-line tool reads those settings too. First identify whether the failure affects sign-in, static assets, API requests, or an ongoing transfer after a connection is established. If the app reports an account permission, request rate, or service-scope issue, follow the service's guidance instead of assuming a routing rule failed to match.
Check the active configuration and routing mode. If the client shows local connection details or rule matches, check the failing action specifically: does the app's connection appear, which rule matched, and which route was assigned? If no relevant record appears, the request may be outside what the client can handle, or the app may not have made a new request at that moment. Save your work, quit and reopen the app, then try again so it doesn't keep using a connection made before the configuration changed. Background processes are especially likely to retain an old session, so refreshing a window alone may not tell you much.
Compare traffic handling and rule-matching conditions
Whether the system proxy applies to an app depends on whether the app reads that setting. Device-wide traffic handling depends on the client and system permissions; it doesn't guarantee that every connection can be captured in every environment. Follow enterprise policies and app-specific proxy settings rather than overriding administrator settings. If the client lets you switch traffic-handling modes temporarily, note the original setting and change only that one option in a permitted personal test environment. Repeat the same action to check for a difference, then restore the original mode to avoid unnecessarily changing other apps' routes.
If the app's request reaches the client but takes the wrong route, check whether it's using the expected domain, whether an earlier rule matched first, and where unmatched requests go by default. Sign-in and content APIs may use different domains. Adjust a narrowly scoped rule only if you understand how the client's matching works and have confirmed that the destination should be covered. After the change, test the target action and check whether previously working sites are affected. If you see no change in the match, remove the temporary rule rather than piling on broader conditions.
Record the timeout stage for API requests separately
Troubleshoot API calls separately from web interactions. If a tool reports a connection timeout, check which network settings it uses and whether requests from the same terminal use the same settings as the graphical app. If it returns a specific API error, distinguish authentication, permission, and rate-limit messages. A request that was sent but waits too long while reading the response is not the same as a failure to establish a connection. See the OpenAI API Routing Guide. Use a short request you are authorized to make, and never paste a real key into a command screenshot, chat, or support ticket.
Switching traffic-handling modes is for diagnosis, not a permanent default fix. If a supported app setting or a narrowly scoped rule solves the problem, don't broaden the changes.
If the same app works on another route, include the route, failed action, and comparison in your ticket. If the client sees the app's requests only in one traffic-handling mode, include the platform, app version, and relevant settings. Be specific: “no connection record,” “wrong rule matched,” or “correct rule matched but the destination returned an error.” Share only relevant, redacted domains and an error summary—not request headers, authorization fields, or business data. If the app doesn't support the traffic-handling mode you expected, check its official documentation rather than describing a compatibility limitation as a route failure.
DNS / NAME RESOLUTION
DNS issues: distinguish resolution errors from connection failures
First check whether the error occurs during name resolution
DNS translates a domain name into an address an app can try to connect to. A typo in the domain, an unresponsive resolver, and a domain that resolves but then times out during connection point to different checks. First verify the domain itself without a path or query parameters. Then, on the same network, test one domain that works and one that fails, noting whether the client is enabled. Once an address is returned, the next failure may be in transport or at the server. And a response alone doesn't guarantee that the app got the address it expected.
On Windows, run nslookup in a terminal. On macOS or Linux with the relevant tool installed, use dig. The commands below use a public example domain to test the command itself and apply only where the corresponding tool is available. For an authorized test target, enter just the domain name, not the full webpage address.
nslookup example.com
dig example.com
Start by checking whether the query returned an answer. A clear “domain does not exist” response is different from no response after waiting. A successful response with no record of a particular type doesn't mean the entire domain is nonexistent. To check record types, run dig example.com A and dig example.com AAAA to inspect each address family separately. Different networks or resolvers may return different answers without indicating a fault; a service may return different addresses based on the request source or distribution policy. The error type and test conditions are more useful than checking whether an address matches someone else's screenshot.
Distinguish system, browser, and client DNS paths
A terminal command checks the resolver used by that command; it doesn't mean your browser, client, or app uses the same one. Some browsers have their own secure DNS settings. The system may select different resolvers by network interface or management policy, and managed networks may use a dedicated resolver for internal domains. If the command returns a result but the browser still says the server can't be found, compare another browser or a clean browsing session. If the browser works but the command gets no response, note the settings difference between them instead of copying one configuration to the other prematurely.
If the issue occurs only after connecting the client, first check whether DNS settings or routing mode changed when you connected. If a test page has an old session open, close it and reopen it before repeating the same query. Browser and system caches may also update at different times after a settings change. Don't start by clearing all network settings or permanently switching to a public resolver. In particular, resolve internal organization domains only through an organization-approved service; don't test them with public lookup sites. If the issue affects only a managed network, ask its administrator to check the DNS policy first.
An IP lookup shows the exit route for that request; it doesn't prove where DNS queries went. Different browser and terminal results alone aren't enough to conclude that there's a DNS leak.
Use the comparison results to choose your next step
If one public domain fails while other public domains and familiar sites work, check whether the domain is still valid and whether the error occurs only with a particular client configuration. If several domains fail to resolve, check whether the network and system resolver are reachable. If both the system and browser return reasonable results but the destination still won't connect, go back to the website or app troubleshooting sections instead of repeatedly flushing DNS. If enabling the same configuration triggers the issue every time and disconnecting restores normal behavior, include the failing domain, lookup method, error type, before-and-after differences, and route in your ticket. Don't include internal domains, complete network settings, or screenshots with sensitive information.
SUPPORT / MULTIPLE DEVICES & TICKETS
Device limit messages and support tickets: identify the source and compare
First find out which screen showed the “limit” message
8LVPN has no limit on the number of devices online at once. If you see a message such as “device limit exceeded” or “can't add device,” note whether it appeared in the 8LVPN user panel, system VPN settings, the client, or the destination app. A destination service's sign-in session rules aren't the same as 8LVPN's device policy. A system error creating a VPN configuration doesn't mean your account has an online device limit. When taking a screenshot, include the screen title and exact message so support can identify its source. Don't sign out every other device just to compare or bulk-delete system configurations that already work.
If the same account works on one device but fails on another, compare the networks, active configurations, and system permissions first—not the number of devices. Try the same action on both devices on one working network, then use another network if needed to narrow down the cause. Confirm that both configurations actually belong to the same account, especially on shared computers or devices with older imported configurations. If only one platform is affected, note its specific steps, such as a permission prompt, active process, or error from the app itself.
Choose where to start based on the source of the message
| Message source | Check first | Contact or escalate when |
|---|---|---|
| User panel | Account and plan status | Submit a ticket if the panel status doesn't match the rules |
| System network settings | Permissions, managed configurations, traffic-handling conflicts | Contact the device administrator for organization-managed settings |
| Client | Configuration source, error stage, behavior on another network | Submit a ticket for repeatable failures with comparison results |
| Target app | Account notices and access requirements from the app | Contact the destination service about account restrictions |
If the issue occurs only on a particular guest network and ordinary pages won't load either, its administrator is usually best placed to fix the access problem. If the target site has returned its own account notice, check with that service first. On the other hand, if the panel status is normal but the current configuration produces the same subscription error on different networks, or a route repeatedly fails in an original–alternative–original test, submit a User Panel Support Ticket. If the panel itself won't load, compare networks and certificate warnings. If you can access it from a working device, submit the ticket there and explain which other device is affected.
Provide a timeline others can reproduce
Keep the ticket title concise: platform + symptom + scope, such as “macOS connected, but one site's sign-in page times out.” Start with the time and time zone, device platform, OS and client versions, network type, and route label. Then list the steps in order, from the initial state to the error. Include the exact error and the expected result alongside comparison results, such as “same device works after switching routes; fails again when switched back” or “all routes fail, but ordinary sites load.” If you can't reliably reproduce the issue, say that it happens intermittently. Don't describe steps you haven't observed as confirmed.
Share only diagnostic details relevant to the issue: for a speed problem, include the time window, same test target, and transfer behavior; for a background disconnect, describe the trigger and recovery; for DNS, include the lookup method and error type. If you changed a setting, say what changed, what the retest showed, and whether you restored the original setting. This lets support continue from the checks you've already done without asking you to repeat them. If you have new comparison results after submitting a ticket, add them to the original ticket to keep the timeline together.
Never include passwords, subscription addresses, keys, or full configurations in a support ticket. Redact errors, screenshots, and diagnostic excerpts first, and show only the part of the window relevant to the issue.
Once the issue is resolved, keep a brief note of what stayed the same, what change helped, and what remains uncertain. In particular, distinguish “switching temporarily worked around the issue” from “the issue no longer happens after reverting the change.” You can continue using an alternative route or network in the first case, but keep the original conditions on record. In the second, you can retest from the same conditions if the issue returns. If you need to go through installation and import from the beginning, return to the Quick Start Guide; there's no need to treat the full troubleshooting process as an installation flow.