VPNBH Troubleshooting Guide

Can’t connect: Find where the connection fails

Check whether the issue is your network, client, or route

If the client stays on “Connecting” or quickly reports a failure, disconnect VPNBH for a moment and try opening a website that normally works on your current network. If that website also fails, troubleshoot your local network first: confirm that your device is connected to the selected Wi-Fi or wired network, try reconnecting, and check whether your browser needs you to sign in through a public network login page. If the public network hasn’t granted access yet, switching VPNBH routes repeatedly is unlikely to help. If regular websites work, check whether the subscription has loaded in the client, whether the selected route is still listed, and whether the system is waiting for network connection permission.

Next, keep your current network unchanged and test a route in a different region or of a different type. If only the original route fails, the issue is more likely related to that route or its exit conditions. If every route fails while connecting, check client permissions, system network settings, and restrictions on your current network. Don’t change your network, route, protocol, and routing mode all at once: even if it connects afterward, you won’t know which change helped. For more on IEPL dedicated lines, relay routes, and direct connections, see the Global Routes page and choose based on region and use case.

Check your device, one item at a time

On Windows and macOS, make sure the client is running and that no other network tool has taken over the system proxy or VPN permissions. If another proxy, corporate network client, or browser extension is active, note its current settings and temporarily disable the conflicting option for comparison. After a system update, network change, or wake from sleep, an old network session may still appear in the client. Disconnect manually, wait for the status to return to disconnected, then select the route again. This is more useful than clicking Connect repeatedly. On Linux, also check that the client has the system permissions needed to create a network interface or change routes, and that your session’s network manager isn’t rewriting them.

On iOS and Android, watch for the system permission prompt the first time you connect. Tapping Connect in the client won’t establish a connection if you haven’t completed the system authorization. If your device has a work profile, another VPN configuration, or managed network policies, check which one is active; don’t delete a work profile you don’t recognize. When comparing Wi-Fi with another available network, test the same VPNBH route on both. Changing the network and route at the same time makes it hard to distinguish a network issue from a route issue. After switching successfully, return to the client and confirm that it shows the current route, not a cached status from the previous session.

Use the comparison to choose your next step

If switching routes lets you connect, use a working route for now and note the region, type, and error shown for the route that failed. Contact support if you need to keep using that region. If switching networks fixes the issue, check whether the original network requires a login, has device management policies, or conflicts with another proxy. VPNBH can’t replace your local network connection. If no route works on any network, check your account plan and subscription update status, then submit the client’s error message and reproduction steps using the checklist at the end of this guide. Repeatedly uninstalling and reinstalling the app can erase useful error details, so save them first.

Connected but websites won’t load: Check the exit route and DNS

First, check whether it’s all websites or just one

Once the client shows Connected, try a regular website that usually works and the site that’s giving you trouble. If regular websites load but one specific site doesn’t, don’t immediately change your device’s network settings. The site may have its own requirements for exit region, account region, browser session, or service availability. Check which region the site requires, choose a suitable exit route, close any old tabs for that site, and try again. If neither regular websites nor the target site loads, check whether the client still shows Connected and see whether regular websites work after disconnecting VPNBH. This comparison helps distinguish a local network issue from a routing or DNS issue that occurs after connecting.

A browser’s “Couldn’t resolve hostname” and “Connection timed out” messages point to different issues. The first means your device hasn’t received an address for the domain, which can be related to DNS settings, cached data, or a recent network change. The second means it tried to reach the destination but couldn’t establish a usable connection in time. Take “Certificate error” warnings seriously: check your device’s date and time and confirm the domain is correct. Don’t ignore security warnings just to continue. The website itself, your login status, or a public network redirect can also cause similar symptoms, so compare multiple destinations and results after disconnecting.

Troubleshoot DNS issues, starting with the simplest checks

First disconnect and reconnect in the client so the system can obtain the network settings again. Then close the affected browser tab, re-enter the domain, and try again. If only one browser fails while others work on the same device, check that browser’s Secure DNS, extensions, and proxy settings before changing anything system-wide. If no browser can resolve domains, check for manually configured DNS, old proxy settings, or work network settings on your system. Note the original values before changing anything so you can restore them accurately. On a managed device, these settings may be controlled by an administrator; check with them before making changes.

Clearing the DNS cache won’t fix every connection problem. Refresh it using the standard method for your operating system only if the resolved address clearly doesn’t match the current network and reconnecting hasn’t helped. If you’re not familiar with the command line, use the system’s disconnect and reconnect options instead of running scripts from unknown sources that may rewrite network settings. If regular websites work but a particular streaming or AI service keeps reporting a region mismatch, DNS is only one possible cause. Also check your browser account region, site cache, and selected exit route. For more on choosing a route, see How to Choose a VPN Route.

Check that the fix holds up

After each change, test the domain that originally failed and open one regular website as well. Testing only one destination can make a temporary website recovery look like a network fix. If switching routes restores all websites, note the regions and types of the old and new routes. If disabling a browser extension fixes the problem, the cause is more likely within that browser. If the client shows Connected but no domains resolve on any route, while browsing works after disconnecting, save screenshots of the errors and the non-sensitive parts of your system network settings, then submit a support ticket. Before submitting, you can use the IP Lookup page to check whether the exit IP is as expected, but that alone can’t confirm that DNS is configured correctly.

Slow speeds and peak-hour lag: Compare routes for your use case

First, identify what’s slow

“Slow” might mean a webpage takes a long time to appear, video buffers repeatedly, file transfers drag, or an AI tool takes a long time to respond. These experiences depend on different factors, so one download speed test can’t explain them all. First check whether your local network is also unstable when VPNBH is disconnected, then compare routes using the same device, network, and destination. If your local network already drops or fluctuates, check your router, Wi-Fi signal, and congestion on public networks first. A cross-border route can’t fix packet loss between your device and your local network. If things slow down only when connected to a particular region, note the region and route type, then test alternatives.

Choose a region based on where the service you’re using is available, not simply the nearest-looking point on a map. Streaming content often depends on your account and exit region; AI tools may have their own availability requirements; and work sites may require an exit from a specific region. Once you’ve chosen a suitable region, compare available routes nearby by loading, playback, or sign-in performance. VPNBH offers IEPL dedicated lines, relay routes, and direct connections. These labels describe how routes are organized; none is guaranteed to be the fastest for every network. The best choice may change as your destination, local network, or exit availability changes.

Make repeatable comparisons during peak hours

If performance drops during peak hours but is normally fine, first confirm that you’re using the same app and page. Keep the device, network, and destination unchanged, and switch only the route. For video, note whether playback repeatedly pauses; for websites, check whether loading stalls at the same resource each time. These observations are more useful for diagnosing a problem than a speed figure measured under inconsistent conditions. Don’t clear your browser, reinstall the client, and restart every device as soon as things slow down. Even if that temporarily helps, you won’t know why. First compare different route types in the same region, then try other exit regions that suit your use case.

If different routes have similar issues at the same time, and local internet also slows down significantly when VPNBH is disconnected, check your network connection first. For Wi-Fi, move closer to your existing access point and avoid testing at the edge of its signal. If possible, compare using another trusted network on the same device. If only one video service buffers while other websites and video services work, check that service’s playback settings, account region, and server status. Don’t assume a single site’s throttling or content restrictions mean all routes are faulty. For a more systematic way to choose by region, type, and use case, see Global Routes and Route Selection Tips.

Troubleshoot plan traffic and speed separately

If the client reports an issue with your plan’s traffic allowance or subscription status, check your current plan in the user panel first. Don’t mistake a plan status issue for peak-hour congestion. VPNBH monthly subscriptions reset their traffic allowance each month on the activation date. Data packages remain valid until used and never expire. The two billing options work differently; see the Plans page for current allowances and prices. When checking your status, distinguish the client’s local cache from the current subscription shown in the panel. If the client hasn’t updated the subscription, its interface may still show outdated information. The subscription updates section later in this guide has a separate troubleshooting process.

When contacting support about slow speeds, say whether the destination is a website, video, file, or AI tool; whether lag happens only at certain times; whether the original and comparison routes use the same region and type; and how your local network performs when disconnected. This helps avoid vague reports like “it’s very slow.” Don’t include transfer logs containing personal files. A description of the issue and non-sensitive error details is enough to start troubleshooting.

Frequent disconnects and mobile apps dropping in the background

First, note what happens just before the disconnect

Note whether the disconnect happens while the device is idle, when the screen locks, when you switch Wi-Fi, after waking from sleep, or during continuous use. If the client shows an old “Connected” status after waking from sleep but websites no longer load, disconnect manually and reconnect, then check whether the new session works. If a mobile device disconnects only after being locked for a while but stays connected during active use, check background activity and power-saving settings. If it also disconnects while in the foreground, compare your local network and selected route as well. Blaming every disconnect on an “unstable route” can overlook power management and network switching.

When a mobile device switches networks, its underlying address and routes change, and existing connections may not continue as they were. Wait for the system to finish switching networks, then check the client status. If the displayed status doesn’t match what you can access, reconnect manually. If you need to keep a work session going, check whether the work app itself requires you to sign in again after a network change. VPNBH can re-establish the network connection, but it can’t guarantee that other apps will resume their sessions where they left off. For tasks that require continuous access, choose a stable network before starting a transfer.

Check power-saving, background, and system settings

On iOS and Android, check in system settings whether background activity is restricted for the VPNBH client and whether a power-saving mode is limiting background network access. Menu names vary by device and system version, so look for settings related to “Battery,” “Background activity,” or “VPN” rather than following someone else’s exact screenshot. Note the original settings before changing them. Then test the same route through the full sequence: connect in the foreground, lock the screen, and return to the app. If your device is managed by your organization, background and VPN policies may not be changeable. Check the management rules rather than trying to bypass them.

Desktop disconnects can also be related to system sleep, network interface changes, or other network tools running at the same time. If the disconnect only happens after waking from sleep, try reconnecting and check whether the system switched to a different network interface while waking. If you’re using wired internet but Wi-Fi is also set to connect automatically, check which interface is actually carrying traffic. On Linux, network management services and manual routing rules may overwrite each other during reconnection. Save your current configuration, then compare the routes before and after connecting; don’t clear system rules you don’t recognize.

Separate route issues from device issues

If only one route disconnects during sustained use, while other routes remain stable on the same device and network, note the route’s region, type, and client message, then contact support. If every route disconnects on one device but works on another device on the same network, focus on the first device’s system settings and client permissions. If multiple devices on the same network lose access to regular websites at the same time, troubleshoot the network itself first. VPNBH allows unlimited simultaneous connections, so don’t assume a disconnect is due to a device limit just because another device is connected. Check account status and shared network conditions separately.

After a disconnect, don’t only capture a screenshot after everything is working again. It’s more helpful to note what you were doing just before it happened, whether the system locked or switched networks, what the client showed, and whether reconnecting manually restored access right away. If you can reproduce the issue reliably, include the exact steps in your support ticket. If not, note the conditions the instances had in common. Before sharing screenshots of power settings, redact the device name and any other personal information.

Subscription update failed: Check the source and account status

First, check in the panel whether your subscription is active

If the client reports that an update failed, sign in to the VPNBH user panel and check your current plan and subscription status before troubleshooting the client. If the panel shows a different status than expected, use the order and plan details there to investigate first. Refreshing the client repeatedly won’t change your account status. If the panel shows the correct status but the client still displays old routes or an empty list, check the import method and network request. Install the client and retrieve your subscription through the client access page in the user panel. Don’t copy subscription URLs from chat history or search results.

Check that the subscription entry saved in your client belongs to your current VPNBH account. Some clients can store configurations from multiple sources. If you click Update on a different entry, it may look like nothing has changed in VPNBH. Check the entry name, source, and last update message, then make sure you’ve selected the correct entry before updating manually. If you’ve regenerated or replaced a subscription, the old entry won’t update itself to the new one. Import the current subscription using the method shown in the panel, and remove the old entry only after confirming the new one works. Don’t send your full subscription URL as plain text.

Troubleshoot based on the error message

If the client says it can’t access the subscription source, first check whether regular websites load on your current network. Then check whether a system proxy, another network tool, or a public network sign-in page is blocking the client. If regular websites also fail, restore your local network access first. If they work but updates keep failing, try again later on the same network and save the client’s specific error message. A “format not recognized” error is more likely related to the import method, client compatibility, or something going wrong during copying. Don’t edit the subscription manually to make it fit. Return to the panel and choose a supported client and import method. If the update succeeds but your route list doesn’t change, check which subscription the client is displaying and whether an older local configuration is selected.

Updating and connecting are separate steps. Imported routes can appear in the list even if your account status has changed; you still need a successful update to get the current configuration. Conversely, a successful update doesn’t guarantee the selected route will connect on your current network. When troubleshooting, note whether the update succeeded, then whether the connection succeeded, and finally whether the destination was accessible. Don’t group all three into “the subscription doesn’t work.” If the update fails, save the error message first. If the update works but the connection fails, return to the “Can’t connect” section.

Protect your subscription and order details

Your subscription URL is an account access credential. When contacting support, you can provide the client name, platform, error message, and the stage where the issue occurred, but don’t include the full URL, password, or an importable configuration file. If you need to share a screenshot, redact sensitive parts of the URL first. Don’t use online conversion tools to process your subscription; you can’t know how they store what you enter. To use VPNBH on another device, follow the instructions in your own panel. VPNBH allows unlimited simultaneous connections, but each device still needs the correct import and account status.

If an update fails just after changing plans, compare the plan details with the current status shown in the panel. Monthly subscription traffic resets each month on the activation date, and the price difference for a mid-term upgrade is prorated by the remaining days. Data packages remain valid until used and never expire. Don’t infer an order’s status from the remaining traffic shown by an old client. If the panel and client continue to disagree, submit the non-sensitive status shown in each, the steps you took, and the error message so support can check the account and client separately.

An app isn’t using the proxy: Check routing rules

First, check whether it can’t connect or isn’t using the selected exit route

If a browser can access a website but an app on the same device can’t, first confirm that both are accessing the same service with the same account, and check whether the app shows a specific region or network error. Browser access only confirms that the browser’s connection path works. The app may use its own network settings, system permissions, or different service domains. If the app works but shows a region that doesn’t match your selected route, check the client’s routing mode and whether the app is included in the proxy rules. If the app can’t sign in, also check the account status and the service’s own message. A failed sign-in alone doesn’t prove that app routing isn’t working.

Routing rules decide which traffic uses the selected route and which uses your device’s original network. With rule-based routing, the domain or connection method used by the target app may not match the rule you expect. In a mode that proxies only selected apps, a newly installed app may not be included yet. Note the current mode, then check whether the app is included in the client’s routing settings. To test whether the rules are the cause, you can temporarily switch to the client’s global mode for comparison. Restore your original routing mode after the test. Global mode is a troubleshooting tool, not a long-term replacement for your configuration if you’re unsure of your work network requirements.

Check the app’s own network settings, one at a time

Some desktop apps have their own proxy settings, while some browser extensions only apply to browser tabs. If VPNBH is connected at the system level and the app is also configured to use another proxy, the two settings may conflict. When checking the app’s network preferences, don’t clear account or work settings. Note the current settings, temporarily disable any conflicting option, and try again on the same route. If the app uses different sign-in or content domains than regular websites, opening its homepage in a browser doesn’t prove the entire workflow is working. If possible, test the exact step that fails in the app and record the message it shows.

On mobile, distinguish browser tabs from native apps. A webpage opened in a browser may use the browser’s own DNS, cache, and login status. Native apps may depend on system network permissions, background activity, and region information stored by the app. If the issue only occurs when the screen is locked, check the background restrictions in the previous section. If it also happens in the foreground, keep the local network and exit region unchanged and compare the app with the browser. Don’t keep uninstalling the app to test; doing so can erase login information and unsynced local data. Check how its data is stored first.

Compare regions with the service’s requirements

If a streaming service or AI tool reports a region issue, first check which regions the service supports, then choose a suitable route. VPNBH covers 100+ countries / 150+ routes, but whether a service accepts a particular exit also depends on its own rules, your account region, and current access conditions. A working route doesn’t guarantee that every feature in an app will work. For AI tool access, see the AI guide. For help choosing an exit based on your use case, see the Route Selection Guide.

If the app works in global mode but not in your original routing mode, include that comparison, the app name, device platform, selected region, and routing mode in your support ticket. If it fails in both modes while other apps work, include the app’s original error message and say whether your account region meets its requirements. Support doesn’t need your app password or screenshots of personal conversations, viewing history, or work files.

Devices & accounts: Don’t mistake a sign-in issue for a device limit

First, check the service’s device policy

VPNBH allows unlimited simultaneous connections. If a new device can’t connect, don’t assume you’ve reached a device limit or sign out of other devices just to free up a slot. First check that the new device is signed in to the correct account, has the current subscription from your own panel, has completed the client import, and has the system permissions needed to connect. If an old device works but the new one doesn’t, compare them on the same network and route to help distinguish an account status issue from a setup problem on the new device.

“Unlimited simultaneous connections” describes the connection limit; it doesn’t mean devices automatically share system permissions, app settings, or local subscription entries. Each device needs to be set up for its platform. VPNBH supports Windows / macOS / iOS / Android / Linux. Permission prompts, background controls, and proxy settings differ by platform. If the new device shows a route list after import but can’t connect, follow the “Can’t connect” steps to check permissions. If no route list appears, use the “Subscription update failed” steps to check the import. Identify the stage where the problem occurs instead of assuming the account is restricted.

Check platform-specific issues at the right stage

The items in the table are starting points for troubleshooting, not problems every device will encounter. If one device can’t connect on different networks but other devices on the same account work, focus on that device’s permissions, subscription entry, and network settings. If multiple devices fail on the same network but work on other networks, check the shared network environment first. If different devices on different networks show the same account status error, check your plan and order in the panel. Narrowing down the issue layer by layer is more useful than reinstalling everything on every device at once.

Account status, billing options, and sign-up details

Use the information shown in the user panel as the source of truth for account issues. VPNBH sign-up doesn’t require an email address; you can create an account with a username and password. When troubleshooting, make sure you’re using the username for the account you actually use, and don’t mix subscription entries from different accounts in the same client. If you’re not sure which account you used, check your existing panel login and order history rather than repeatedly importing subscription entries you don’t recognize. When sharing account details with support, provide only the information requested by the ticket form. Don’t include your password or full subscription URL in the issue description.

Plans aren’t based on the number of devices. VPNBH monthly subscriptions are ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB. Data packages are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. Monthly subscription traffic resets each month on the activation date. Data packages remain valid until used and never expire. When checking a client message, distinguish traffic status from subscription update status and device connection status. See the Plans page for full details. VPNBH offers a 60-day no-questions-asked refund; see the Refund Policy for instructions.

When to contact support: Prepare a reproducible support ticket

First, check whether you’ve completed the basic troubleshooting steps

After completing the basic comparisons in the relevant section, submit a support ticket if the problem persists consistently. This is especially useful if the panel and client continue to show different statuses, no route connects on multiple available networks, the same route repeatedly returns a clear error, or subscription updates keep showing the same error. Further blind changes to settings are unlikely to help. If regular websites also fail after disconnecting VPNBH, restore your local network access first. If only one third-party service reports an account or region issue, check that service’s own guidance as well. Support can help check issues related to VPNBH, but can’t override device administrator policies or a third-party service’s rules.

When describing an issue through the support ticket page in the user panel, start with a reproducible symptom—for example, “The client says Connected, but no browser can resolve domain names”—rather than just “It doesn’t work.” Then include the device platform, the selected route’s region and type, whether regular websites load directly on your current network, whether the issue happens before or after connecting, and the individual checks you’ve already performed. If it only happens in one app, include its name, routing mode, and the results in global mode. If it only happens after the screen locks, describe the difference between foreground and background use. This helps support start at the right layer without repeatedly asking for basic details.

Collect evidence by symptom

Screenshots should show what’s needed to explain the problem. You don’t need to include your entire desktop, personal files, or unrelated chat history. Before submitting, check for passwords, sensitive order details, or full subscription URLs and redact them. If the client provides an error message that can be shared safely, its original wording is more useful than a summary like “network error.” If you only see a system prompt, note whether it appeared after tapping Connect, updating the subscription, or opening the target app. Don’t change system security settings or run diagnostic scripts from unknown sources just to gather evidence.

Retest after support replies

After receiving troubleshooting steps, save your current settings first, then follow the suggestions one at a time and repeat the action that originally triggered the issue after each step. If support suggests switching routes, keep the device, network, and destination unchanged. If they suggest checking system settings, keep the route fixed. In your reply, say exactly which step fixed the issue or confirm that the same error still occurs; don’t just say “I tried it.” If the issue temporarily goes away, note the route and network conditions so you have a point of comparison if it returns.

If the issue involves your account, plan, or payment, state the order status shown in the panel. VPNBH supports Alipay / WeChat Pay / USDT. Don’t post payment credentials or full transaction details publicly. If you haven’t started using the service yet, the Getting Started Guide walks you through setup and import. This guide helps pinpoint what went wrong at a particular step. Saying exactly where you got stuck usually makes support more effective.