VPN won't connect
Break “can't connect” down into observable symptoms: the button does nothing, the system denies permission, the client stays on “Connecting,” or it reports a successful connection and immediately returns to “Disconnected.” These point to different stages. Before testing, note your current network, selected route, connection mode, and the exact error message. If the error disappears quickly, check the client's diagnostics for a recent entry. Don't repeatedly click Connect just to capture the message; multiple retries can mix up the results.
Check that your device can access the internet
- Disconnect GangVPN and open a regular website you can normally reach on your current network. A Wi-Fi icon alone doesn't mean you're online. Public networks may require you to accept their terms in a browser first. An old page may load from cache, so try a page that hasn't been cached to confirm.
- If regular internet access isn't working, reconnect to the network or, where allowed, try another type of connection. Then test the same route again. If basic websites behave differently before and after switching networks, focus on the network connection first. Don't change both the route and the network in the same test.
- If regular internet access works, check that your device's date, time, and time zone are correct. A clock that's out of sync can cause certificate checks to fail. Sync the system clock and try again. If a certificate warning still appears, don't choose “Continue”; just note which screen showed it.
Tell system permission issues apart from route handshakes
If a system permission prompt appears when you tap Connect, make sure it came from the client you just opened, then follow the system instructions. If you denied permission earlier, check whether the relevant configuration appears in your system network settings, then follow the platform installation and import steps to complete authorization. On a work- or school-managed device, an administrator may have locked down the configuration. Check your organization's network and device policies first; don't remove management profiles or disable security software to troubleshoot. If the system says another connection is already in use, quit any similar client you installed or check its on-demand connection settings, then test GangVPN on its own.
If the client starts connecting but stays on “Connecting” or times out, keep the network and connection mode unchanged and try another visible route for comparison. If the alternate route connects, retry the original to confirm the difference is reproducible. You can check the regional coverage on global servers, but use the options shown in your client as the source of truth. If all routes fail, keep one route selected and change only the network. If switching networks fixes it, focus on the original network. If both routes and networks fail, check the account, subscription, and device configuration; there's no need to test every available route.
Check whether the connection failed or the subscription has no usable configuration
An empty route list, an outdated subscription, or the wrong configuration may mean the client hasn't retrieved usable connection details. Open the account overview in the user dashboard and check the account and plan status, then confirm which subscription is selected in the client. If the dashboard shows your plan is active but the routes still don't appear after an update, go to Subscription updates. Don't clear all configurations and try again. Conversely, if routes are listed and other routes connect, keep the current subscription instead of reimporting it because one route failed.
Connected, but websites won't load
A “Connected” status only means the system or client completed a connection step. It doesn't guarantee that your browser reached the destination over the expected route. First identify the error: domain not found, timeout, certificate warning, or a page that loads but refuses the request. The last case usually means the request reached the site, so it doesn't by itself indicate a DNS problem. Note whether the error occurs when opening the home page, being redirected to sign in, or loading page resources. That makes later comparisons more useful.
Check whether it's all websites, one site, or the browser
Keep the same route. Open a regular website you can normally access, then try the affected site. Next, try the same site in another browser or a clean browser session. If regular websites fail in both browsers, check the system proxy, connection mode, and DNS. If only one browser fails, check its secure DNS, proxy extensions, and site data. Private browsing doesn't automatically disable extensions in every browser, so check whether extensions are allowed to run there before testing.
If only the target site fails, check whether other pages on that site or its sign-in page work. A page may load its main content from one domain while sign-in, images, and scripts come from others. So opening the home page doesn't mean the whole site is working. If the error only occurs after submitting a form or being redirected, note the step and any domain that can be shared publicly. Don't copy a full URL containing sign-in parameters. If the page shows a region, account permission, or rate-limit notice, follow the site's rules; don't treat a refusal message as a connection timeout and retry repeatedly.
Use system DNS queries to narrow down DNS issues
DNS resolves domain names to addresses. A command-line lookup can check whether the default resolver responds, but it can't replace a browser test: browsers may use their own encrypted DNS, and the client may handle domain names differently depending on its connection mode. In Windows Command Prompt, run nslookup. On macOS or Linux systems with dig, you can query the public example domain below. To troubleshoot a real issue, replace only the domain name—don't include a protocol, path, or query parameters. You only need to read the output; administrator privileges aren't required.
nslookup example.com
dig example.com
| Symptom | Next step |
|---|---|
| Several common domains all time out | Compare results before and after connecting, and check whether the default resolver is reachable. |
| Only the target domain returns “not found” | Check the spelling, subdomain, and network scope. Internal domains may only be available on a specific network. |
| The command returns an address, but the browser reports a DNS error | Check the browser's secure DNS settings, proxy extensions, and exact error message. |
Restore the original settings, then compare
Note your original system and browser DNS settings first. If you recently changed DNS manually, restore the network's original configuration and test again. If the issue started after installing a browser extension, disable only that extension, if permitted; don't change both system DNS and client rules at once. Different DNS results before and after connecting aren't necessarily a problem—services may route requests by region. Don't treat opening a site by IP address as an equivalent test: sites that rely on domains, certificates, and virtual hosts may not work that way.
If lookups work while disconnected but several public domains time out after connecting on the same network—and the issue persists on another route—include the lookup command, type of result, and client mode in a support ticket. If lookups work but only one app is inaccessible, see Troubleshooting a single app. You don't need to share your home network's resolver address. Don't send internal domains or screenshots containing session parameters.
Slow speeds and peak-hour slowdowns
First describe what's slow: pages take a long time to start loading, downloads never reach their usual speed, video quality keeps dropping, or calls cut out occasionally. Slow page startup may involve DNS, connection setup, or the server's response. Slow sustained downloads are more likely to depend on route throughput or limits at the destination. Calls and video are especially sensitive to latency changes. Don't use one download speed to predict call or video quality, or rank two routes using results from different sites.
Keep speed records you can compare
- Use the same device, network, and test destination. Pause background downloads, photo backups, and large file syncs that you can control. Note whether other devices are transferring data during the test. If your target normally isn't accessible on a regular connection, choose a public test destination that works both connected and disconnected as a baseline.
- Around the same time, record performance on your regular connection, then connect to your usual route and repeat the same test. Finally, change only the route. Use the same source and file for download tests. For video, use the same content and note whether automatic quality is enabled. Watch for caching: reopening a page you've just loaded isn't a good way to compare first-visit speed.
- Keep one set of results from a typical time and another from when slowdowns occur, noting the local time and time zone. Rather than capturing a one-off peak, record whether buffering is constant, intermittent, or happens only at playback start or after seeking. For a complete testing method, see VPN speed tests: tools and comparison tips.
Use comparisons to find the bottleneck
If things are slow both with and without the VPN, first check whether devices at home are uploading, downloading large files, or on video calls. Move closer to the access point or try a wired connection if available. If that improves your baseline connection, focus on local network access. If the baseline is stable and only one route is slow—but changing only the route fixes it—use the better-performing route for now and note the original route and when the issue occurred.
If routes in multiple regions are slow to the same destination but work normally with other destinations, investigate the destination site, its content delivery network, or the app itself. For video, automatic quality reduction is the player's response to available throughput, but stuttering can also be caused by device decoding. Keep the video the same and check whether other destinations stutter on the same device, then compare playback on another device. If only one device drops frames while playback progress continues, check its load and playback settings. For more on picture quality, see Streaming quality and bandwidth troubleshooting.
Look for patterns during peak hours, not one-off results
If the same route works during the day but repeatedly slows down in the evening, the cause may be your network, the path between networks, or a busy destination site. Keep a baseline test of your regular connection in the evening too, and compare more than one destination. If only your home Wi-Fi slows down and the same route works on another permitted network, focus on local access. If the baseline is fine but the same route repeatedly takes a long time to reach several destinations, include those shared symptoms in your ticket. Don't present a momentary speed-test result as a bandwidth guarantee.
Frequent disconnects and background drops
First work out whether the client actually disconnected or only the current task failed. If the client still shows connected during a slowdown and other regular websites load, the issue is more likely limited to the app, session, or destination. If the client and system connection status both change, note whether the connection recovers automatically, requires a manual reconnect, or still appears connected but stops transferring data. What happened just before the disconnect is often a better clue than repeatedly switching settings.
Match disconnects to screen status and network changes
On the same network and route, check what happens while using the app in the foreground, after switching to another app, and after locking and unlocking the device. Don't change power settings or force-quit processes at the same time. If you only notice a disconnect after unlocking, that doesn't prove it disconnected while the screen was locked. Check system records and note whether the actual interruption time is known. If no background task was transferring data, the delay before the app screen recovers may just be the app reestablishing its session.
Next, check for changes in network access. Moving to another room may switch Wi-Fi access points, and a device may switch between Wi-Fi and cellular data. Either can cause existing connections to renegotiate. Test brief interruptions during a switch separately from repeated drops while stationary. Retest in one place with a stable signal, then check what happens when the network changes. If it disconnects while stationary, keep the app in the foreground and the network unchanged, and compare another route.
Check whether the system is suspending the connection on your platform
| Platform | Where to check |
|---|---|
| Android | Battery use, background data, and system VPN settings under app details; names vary by system. |
| iOS | System VPN status, network changes, low-power mode, and any on-demand connection settings shown in the configuration. |
| Windows / macOS / Linux | System sleep and wake, Wi-Fi connection status, and whether another network client is running at the same time. |
On Android, if disconnects only happen after the screen locks, check whether the client is restricted from running in the background, if the device owner allows it. Adjust that app alone and test again, keeping an eye on battery use. Don't remove power-saving restrictions for every app. On iOS, the system VPN status and app background refresh are separate. Check the system status and configuration first; enabling background refresh isn't a universal fix. If a desktop disconnects after sleep, compare how it recovers on wake rather than leaving the entire device awake indefinitely just to keep the connection alive.
Decide whether you need to rebuild the configuration
Check whether another on-demand connection is enabled or the network configuration was changed manually. Note the current settings, then pause conflicting personal configurations on a device you own and test whether GangVPN works reliably on its own. Don't delete every configuration first: that erases useful differences, and some managed configurations can't be restored by importing a subscription. If disconnects began after a subscription update, note the route names and modes before and after, then test another route in the current configuration. If disconnects continue after switching, don't try to fix things with outdated configurations from unknown sources.
Contact support if multiple available routes disconnect while you're on a stable network and using the app in the foreground, or if the regular internet connection doesn't recover after reconnecting. Include whether the device had just woken up, whether the system connection status changed, and whether automatic reconnection worked. If only one app disconnects while other network requests work, note when the app fails and follow App-specific comparison tests.
Subscription update failed
Updating a subscription and connecting to a route are separate steps. A route that still works doesn't mean the client can fetch new configuration; a successful download doesn't guarantee that any particular route will connect. First determine whether the subscription can't be retrieved, was retrieved but can't be imported, or shows a successful update but no new routes to select. Note the update time shown in the client, the exact error, and the screen where it appeared. Don't delete the old configuration or paste the subscription URL into an external site to test it.
Check the account and subscription source
- Sign in to the user dashboard and confirm it's the same account used in the client. Check the plan and data status. Monthly plan data resets each month on the activation date; data packs never expire and remain available until used. Billing types work differently, so check the relevant status for each. Don't confuse depleted data with a configuration parsing error.
- Get the import option for your client from the current user dashboard. If you've switched accounts, changed the import source, or saved an old URL, don't assume it's still valid based on the subscription name alone. Check your platform using the client links in the dashboard, then verify the target configuration using the import steps.
- After starting a manual update, check the current configuration's update time or see whether the route list changed. Some clients can store multiple configurations, so a successful refresh may have updated one that isn't enabled. Make sure you're testing the subscription you just updated, then try connecting through one of its routes. Keep any configuration that still works until you've finished testing.
Follow the step where the error occurs
If the error is a network timeout, first check whether the same device can open the dashboard, whether its system clock is correct, and whether the failure only occurs on one network. The client's update request may take a different path from your browser, so being able to sign in to the dashboard only confirms that the account page is reachable. If permitted, try updating the same configuration with the same client on another network. If it fails on both and the client stays at the retrieval stage, save the exact error. Don't look for mirrors or conversion tools from unknown sources.
For an authentication or permission error, first rule out switching accounts, importing an old subscription, or copying an incomplete URL. If you get the same error after retrieving the configuration from the dashboard again, ask support to check it. If the format isn't recognized, make sure the import method matches the subscription type required by the client. Don't try to force an import by manually changing route addresses, encryption settings, or file extensions. If the actual error is a write failure, check whether the client can save local configurations, especially if the device warned about storage space or system permissions recently changed.
Finish by testing a route, not just the success message
Make sure the updated configuration is enabled, then test a regular website and the target app. If only the original route was failing before the update and a newly available route now connects, keep the results for future comparison. If import succeeds and routes appear but connections still fail, return to the connection troubleshooting section. If the plan status doesn't match what you expect, compare the plan pricing and data rules first, then note both the dashboard status and the client's message in your ticket.
Only one app can't connect
A service working in your browser doesn't mean its desktop app uses the same route. Apps may use the system proxy, keep their own proxy settings, or use different domains or transport methods from the website. First clarify whether the app won't open at all, opens but can't sign in, or only fails when uploading, making calls, or syncing. Use the browser as a comparison, but don't assume that loading the website's home page means app sign-in and data transfer are working too.
Check how the app actually connects
- Keep the route unchanged and check whether other apps and regular websites work. If your browser has network extensions installed, note whether they're involved in the test. Otherwise, the difference between a working browser and a failing app may simply be that the browser uses its own connection path.
- Check whether the affected app has its own network or proxy settings. If you manually entered an old address or port, check whether it still points to the current local configuration. If you're unsure, note the original settings and follow the app's instructions to restore an appropriate default. After changing settings, quit and reopen the app normally so it doesn't reuse an existing session.
- Check that the client's connection mode and rules match what you're trying to do. If the client offers another mode to compare, briefly switch modes on the same route in an environment where that's allowed. Note whether the app changes, then restore the original mode. Don't switch routes, change DNS, or enable another proxy at the same time, or you won't know which change made a difference.
Distinguish routing rules, reused sessions, and service restrictions
Split routing typically sends requests down different paths based on conditions such as domains, addresses, or apps; the details depend on the client. One app may contact several service domains, so a home page working doesn't mean sign-in or sync requests are using the expected route. If the client shows request logs, briefly reproduce the issue and check the relevant domains and paths. There's no need to enable detailed logging indefinitely. If changing modes fixes the app, switch back to the original mode and check whether the issue returns. Then inspect the rules related to that request; don't send all device traffic down one route indefinitely.
Some apps reuse an existing session after a network change or wait for an idle connection before reconnecting. After switching modes, end the app's existing network task, then close and reopen it normally. For developer tools, identify whether the request comes from the editor, terminal, or a task inside a container; they may use different proxy settings. If the problem only occurs in a development environment, note the publicly shareable request stage and error category. Don't include environment variables, project configuration, or request headers. See AI tool access guidance for differences between web and desktop tools.
Use the response to decide who to contact
If the app returns a message about account permissions, unavailable resources, or reauthentication, the request reached a service capable of responding. Check the destination service's account and usage policies; changing routes can't replace site authorization. If the same action also fails on a regular connection, don't report two different errors as one VPN issue. If other apps work but this app consistently fails in one connection mode, give GangVPN support the mode, failure stage, publicly shareable domain in the client log, and retest results.
Issues across multiple devices
GangVPN has no device limit for simultaneous connections. If you see a message such as “device limit exceeded” or “this device stopped working after signing in on another,” first check where it came from: the user dashboard, GangVPN client, system network settings, or the third-party app you're using. Third-party apps may manage their own account sessions, playback devices, or sign-in state, and your system may limit which network configurations can be active at once. Those restrictions are separate from GangVPN's plan rules for devices.
Run a basic check on each device first
Use a working device as a reference. On the same network, check that both devices can open regular websites. Then sign in to the user dashboard on each and confirm the expected account is in use. Check that the selected subscription in each client belongs to that account. Similar account names, an old configuration, or changed credentials can make it look as if both devices use the same subscription when they actually have different configurations. Reimport from the dashboard only on the device that needs updating. Don't share subscription links through chat apps.
Connect the first device and verify it with a public website. Then connect the second and test the same destination. Go back to the first device and open an uncached page again. Note the app and system connection status on each device. If only a third-party app asks you to sign in again while network tests work on both devices, check the destination service's session rules. If the VPN status on one device changes when the other connects, record whether you can reproduce it; don't assume that timing alone proves an account device limit.
Separate shared network issues from device-specific issues
If both devices fail on the same network, the shared network or current route may have changed. Keep the route the same on one device and, where allowed, switch only its network. Leave the other device on the original network as a comparison. If only the original network fails, check Wi-Fi access, network sign-in status, and the router. If the error follows one device across networks, focus on that device's permissions, client, and cached configuration. If the same error follows one subscription regardless of device, ask support to check the account status.
When several devices are in use, distinguish slowdowns from forced disconnects. They may share a network, and large file syncs or sustained uploads on one device can affect tasks on another. Pause any large transfers and see whether pages load faster while keeping all devices connected. If speed improves but connection status never changes, continue with Slow speeds and peak-hour slowdowns. Don't sign out or reinstall everything just to check device limits; that would erase useful comparisons.
Get the configuration for the right platform
Supported platforms include Windows / macOS / iOS / Android / Linux. The same account can get the right client for each platform from the client links in the dashboard, then follow the guide to import the configuration and grant system permissions. Don't copy an app folder or saved system network configuration from one device to a different operating system. If a device can't see the expected configuration because of its account or plan status, check the dashboard instead of using a configuration from an unknown source.
If the user dashboard or GangVPN client explicitly reports a device limit, submit the redacted message and explain which device connected first, what changed on which screen after the other connected, and whether both were on the same network. Label them “Device A” and “Device B”; there's no need to list serial numbers or hardware identifiers. Support can reproduce the sequence more easily than they can review lengthy logs from every device.
When to contact support
A support ticket is useful for issues you can reproduce reliably but can't pinpoint, or for clear conflicts between the dashboard and client. Start with the action that's most affected. For example, “On the same network, several public websites won't load when connected but work again when disconnected” is more actionable than “slow” or “doesn't work.” You don't need to try every step before submitting. If more testing would interrupt your work or involve a managed device, record what you see without expanding the test.
When to contact support directly
Contact support if you've checked system permissions and regular internet access but different available routes still fail at the same stage; if the dashboard shows an active account but the client repeatedly reports a permissions error when retrieving configuration; or if the dashboard and client disagree about your plan status. You can also submit a ticket if disconnects recur under the same conditions and time period after you record the results. If you see an unexpected certificate warning, an unfamiliar import source, or suspect your credentials have been exposed, stop using the questionable source and check your account on a trusted device. Then use the contact page to reach support.
If regular internet access also fails when disconnected, contact your network provider first. If an internal work network only works through a specific connection, ask your local administrator. If the target app explicitly reports an account permission issue, contact that app's support first. If you're not sure which step is failing, submit the comparisons you've already made and say which checks you haven't tried. Don't upload piles of unrelated screenshots just to prove there's a problem.
Describe the issue so someone else can reproduce it
- Describe your setup. Include the operating system, version shown in the client, network type, route name, and connection mode. Use the version displayed on your device; if you're unsure, just give the screen label. Describe the network as home Wi-Fi, cellular data, or a managed network. Don't include the full network name or your location.
- Include the time and steps. State when the issue started using your local date, time, and time zone. List the steps in order, such as tapping Connect, switching to another app, or opening a website. Include the expected and actual results. If it only occurs at certain times, say whether it works at other times.
- Include comparison conditions. Describe what happened when disconnected, after switching routes, and after changing networks. Mark anything you haven't tested as “not tested.” Note whether you restored the settings after testing so support can tell whether the next results came from the default configuration or a modified one.
Redact sensitive details before sending, then add updates to the same ticket
Capture only the error and screens relevant to the issue. Check the edges of screenshots, address bar, notification area, and window background. Hide usernames, subscription credentials, session details, order information, and private addresses. Client logs may contain request URLs or authentication fields. Copy only a few lines related to the failure, redact them, and review them again. If you're unsure which fields are sensitive, start with the error category and steps, then wait for support to tell you what else they need. Never share your account password or upload a complete diagnostic file to a public file-sharing service.
Open support tickets in the dashboard. Use “symptom + trigger” as the title, then organize the message by setup, steps, actual result, and comparison results. If the issue later changes or recovers, add the time, any settings you changed, and whether you can still reproduce it to the same ticket. Don't open duplicate tickets for the same symptom. If support suggests a test, change one thing at a time. After the issue appears fixed, retest the original failing steps—for example, lock the screen again, reopen the app, or try at the original time—to make sure it wasn't just a temporary recovery.