Complete VPN Guide

Service and cross-border connections

Understand the service, subscription and client

88888888VPN is a subscription service for cross-border connectivity, with 100+ countries / 250+ routes, support for Windows / macOS / iOS / Android / Linux, and unlimited simultaneous devices. Setup involves a few distinct components: your account stores orders and plan status; your plan determines available data and billing; your subscription provides route configurations to the client; and the client establishes a connection on your device. Being able to sign in to the web dashboard does not mean network acceleration is enabled on your device. Installing a client does not mean you have an active plan. Understanding the difference helps you work out whether an issue is with your account, configuration or local network.

When you visit an international website, requests travel through your local network, the route selected by your client and the destination service. The client configuration determines which requests use a route and which continue over your regular network. The destination website sees the exit point, which is different from your device's local address. To check whether your connection is working, verify the actual exit route and the target app—not just the client's status icon. Browser cache, app-specific proxy settings and your local network can all affect the result. One site failing to load does not necessarily mean the entire route is down.

Route location does not determine content access

Route names commonly include a region or city and a connection type, such as an IEPL dedicated line, a relay route or a direct route. The region indicates the exit location; the type describes how the connection is routed. They serve different purposes. A route near your intended region is a reasonable starting point, but performance also depends on your carrier's routing, the destination service's location and the time of day. A region in the name is not a speed ranking, and no route type is the right choice for every app. Check the current list in your user dashboard and client. Visit the Routes page to learn about route types and how to choose one.

AI tools and streaming services also have their own account requirements, regional policies and content licensing. A successful connection only means your request can reach the destination; it does not satisfy the platform's eligibility checks. Even exits in the same region can produce different results because of platform detection, account status or changes to content delivery. Follow the target service's terms and verify access directly. If a page clearly identifies a regional or account restriction, review the platform's guidance first instead of repeatedly changing local settings to address a non-network issue.

Understand privacy and usage limits

The service's privacy commitment is anonymous, no-logs usage. You can create an account with a username and password; no email address is required. See the Privacy Policy for details of how data is handled. Your account and subscription are still access credentials and should be kept secure. Not needing an email address is no reason to share them. Network acceleration does not replace operating system updates, encrypted website connections or app permission management. If your browser warns about a certificate, check the URL and device clock; do not ignore the warning just to continue. After using a shared device, sign out of the dashboard and remove any saved credentials.

Unlimited devices means you can use the service across your own computers, tablets and other devices without tracking a device allowance. All devices share the plan's data, however, and background syncing, video playback and file transfers all use it. A never-expiring data package lasts until its data is used up; it does not provide unlimited data. When choosing a plan, consider device count and data needs separately: the former affects how you use the service, while the latter helps determine which billing option fits. Home and workplace networks may have different management requirements, so make sure you are authorized to change network settings on a device before installing or enabling the client.

Account access, subscription updates, route connections and access to the target app are separate checks. Check them in order rather than assuming every issue is a route problem.

Before you begin, make sure you have a working local network, an account for the target platform and access to your device's system settings. Get the client and subscription through this site's user dashboard—not from links in articles or unfamiliar messages. For a short checklist, use the quick-start guide. This manual also explains how to confirm each step and how to roll back changes. By the end of this section, you should be able to identify whether you still need an account, plan, configuration or client. Then move on to choosing a plan instead of repeatedly trying downloads from different pages.

Choose a monthly plan or data package

Match the billing option to your usage

Choose a plan based first on how regularly you use the service, then on how much data you need. Monthly plans suit ongoing use, with data resetting each month on the activation date. Data packages suit occasional use: the data lasts until used and never expires. The difference is how data renews or runs down—not which devices are supported. A package does not automatically refill, and a monthly plan does not give you a fresh allowance every day. Check the full details on the Plans page before buying, then review the currently available options and order information in the dashboard.

To estimate your usage, list the activities that actually use accelerated routes rather than adding up all the network traffic on your devices. Text chats, web pages, image generation, video streaming and large downloads use data differently. Even within one app, text interactions and media uploads can vary considerably. If you have no usage history yet, there is no need to guess an exact allowance. Start by identifying your main activities, then check the dashboard after using the service. Your own usage gives a more useful estimate than someone else's.

Factor in your devices and background tasks

There is no device limit, but plan data is shared rather than allocated separately to each device. Cloud sync on a computer, video on a tablet and background tasks on other devices can all use data at the same time. When choosing an allowance, consider automatic activity as well as what you do yourself, including media preloading, photo backups and app updates. If these tasks do not need an international route, adjust their paths in the split-tunneling section later. Do not route all traffic through the service by default and then use a larger plan to compensate for a configuration issue.

Monthly plan data resets on the activation date, not necessarily at the start of a calendar month. When checking the billing period in your dashboard, look at both your remaining data and the relevant dates—not just the plan name. High usage in the current period does not always mean you will need a larger plan long term; a one-off download or batch sync may be the cause. Find out what used the data before making a change. Mid-cycle upgrades convert the price difference into remaining days. Use the confirmation shown in the dashboard; do not calculate a payment or infer a new expiry date from the data difference yourself.

Check the plan and any changes before ordering

A data package means you do not need to plan around a monthly reset, but you should still keep an eye on the balance. A long video session or large file transfer can use up the remaining data. Check the dashboard to see whether a monthly plan and data package can coexist in one account, how switching works and how charges are handled. This guide does not assume any unlisted stacking, merging or credit rules. If you already have a plan, review the change preview first and confirm whether the action extends your current plan or switches billing options. These are not necessarily the same thing.

Compare plans on an equal basis: monthly plans include a periodic data reset, while data packages last until their data is used. The listed price alone does not show which option is right for you. If you use the service often, consider your data use in each billing period; if you use it occasionally, consider whether the data can be used at your own pace. The service accepts Alipay / WeChat Pay / USDT and offers a 30-day no-questions-asked refund. Refund terms and data rules are separate; the refund period is not the plan duration. See the Terms of Service for full details.

Before moving on, note your chosen billing option, price and data allowance, and confirm that your devices run supported platforms. You only need to record plan details here—never save a sensitive link. If you are still comparing, go back to the plans page and review the details; there is no need to create multiple accounts to test checkout. Once you know what you need, setting up an account and placing an order will be more straightforward. If you change plans later, you can use your original reasons to work out whether your usage, frequency or local routing settings have changed.

Set up your account and confirm your order

Create an account with a username and password

Use this site's navigation to open the user dashboard account page. Check that the browser address uses this site's domain before entering a username and password. No email address is required. Choose a username you can remember accurately and that does not reveal sensitive personal information. Do not reuse a password from another important service; consider saving it in your device's password manager. Follow the dashboard prompts to create the account, then confirm that you are signed in to your own account page—not still on the public landing page or an old page loaded from browser history.

When saving your login details, make sure you remember the username's exact spelling. Browser autofill may use an old account or fill in fields from another site, so check everything before submitting for the first time. If a username is unavailable, choose another and try again; do not create multiple accounts to get around the message. If your account exists but you cannot sign in, check your typing, capitalization, keyboard input method and password manager entry. Never send your password to support or leave the full login fields visible in a screenshot.

Confirm the plan before proceeding to payment

After signing in, open the plans page in the dashboard and compare the displayed product with the details you chose in the previous section. For a monthly plan, check the price, data and billing-period rules. For a data package, check the price, allowance and never-expiring terms. If the account already has an order or plan, review any change notice as well. Confirm that you are signed in to the right account before creating an order. If you have used different accounts in the same browser, do not assume an order belongs to the account shown in a saved username; check the current account details in the dashboard.

Once the order is created, review the amount, product name and status before choosing a payment option that is currently available. The service accepts Alipay / WeChat Pay / USDT. Payment flows may differ, so follow the instructions on the current payment page rather than relying on payment details in an old screenshot. For payment methods that take you out of the browser, return to the dashboard and check the original order instead of creating another for the same product. If a redirect fails during payment, check the order status first. A page that does not return automatically is not a reason to pay twice.

A completed payment is not the same as an active order

A payment app's success message means the payment-side steps are complete. Confirm delivery by checking that the dashboard marks the order as successful and shows the updated plan details. Return to your account and review the order list and account overview to confirm the product appears in your current plan. The page may be showing cached information, so refresh and check again, but do not keep creating new orders. If the order is still pending, keep the payment result and original order details, then contact support through a dashboard ticket. Do not assume your funds are lost just because the browser closed, failed to return or showed a blank page.

If a payment fails or is canceled, first check whether an unfinished order still exists. If the dashboard offers options to continue payment or cancel, follow the prompts on that order. Confirm it is closed before deciding whether to create another. If the payment provider charged you but the order has not updated, do not try to make up the difference by submitting the same amount through another payment method. The most useful details are the order ID, product, dashboard status and payment result. In a support ticket, provide only what is needed to investigate and hide unrelated payment account information. Never include your full password or subscription link in payment records.

Creating another order will not fix one that has already been paid. Check the original order and plan status, then report any discrepancy through a user dashboard ticket.

Keep order records and understand how to request a refund

After an order is active, you can save a screenshot of the product name, amount and status for future reference when checking renewals or plan changes. Store it somewhere you control; do not post payment receipts on public forums. See the Terms of Service for full details of the 30-day no-questions-asked refund. To request a refund, sign in to the relevant account and submit the order details and your request through a user dashboard ticket. Do not infer processing times, payment fees or other conditions that are not stated on the plans page. The Terms and support response govern the process.

You have completed this stage when you can sign back in to the same account, the order status matches the payment result and the correct plan appears in your account. If you have created an account but do not have an active plan, subscription and client setup in later sections will not give you permission to use routes. Once you have confirmed the order is active, continue to the subscription section. This sequence helps distinguish order issues from client problems and makes it easier to tell whether you need to restore your login or your device's configuration when switching devices.

Get and manage your subscription

Get your configuration from your account

Sign in to the user dashboard and look for an import, copy or subscription access option in the account overview or subscription section. Your subscription provides the routes and related configuration available to your account to the client; do not use an example from a public article as a substitute. First confirm that your plan is active, then check the import options shown in the dashboard. If no subscription is available or your plan status is flagged, resolve the account or order issue first. Do not search other pages for a replacement link. Get both the client and subscription through the dashboard; this site's articles do not contain real subscription URLs.

A subscription link may contain credentials that identify your account permissions. Protect it like a password. Paste it only into your own client; do not send it to an online converter, put it in a public note or commit it to a code repository. To demonstrate an import, use an obviously fake value such as https://example.com/sub?token=YOUR_TOKEN. This URL is an example of the format only and cannot be used to import a subscription. Before sharing a screenshot, hide not only the link itself but also check the search box, clipboard preview and browser history for the same information.

Direct import or manual paste

If the dashboard offers direct import, your browser may ask whether to open the client. Make sure the app it is about to open is the client you installed before allowing the redirect. If nothing happens, check that the client is installed and opens correctly, and that your system permits the app to handle the import action. A failed direct import does not necessarily mean the subscription is invalid. Try the client's manual add option and paste the address copied from the dashboard into the subscription URL field. Do not paste the link into a route name, note or browser address bar as a substitute for importing it.

Manual setup usually involves a URL and a display name. The name is only for identifying your local configuration, so use something short that helps you tell it apart. The URL determines where the configuration comes from. After pasting, check for extra spaces, line breaks, quotation marks or punctuation added by a messaging app. Save it and refresh or fetch the configuration. Check whether a route list appears in the client. A local name without any routes does not mean the import worked. If the client asks for a configuration format, use the content provided by the matching dashboard option. Do not guess based on a file extension or convert the URL to another format without a reason.

Know the difference between updating and switching

Updating a subscription fetches the configuration again; choosing a route changes the active path within the existing list. One does not replace the other. If the list is out of date, switching routes will not fetch new entries. If a website is temporarily unavailable, repeatedly refreshing the subscription may not improve the route. Identify the problem first. If the list is empty, route names are missing or configuration fetching fails, check for a subscription update. If a route is listed but a particular app fails, go to the connection verification section. After a successful update, confirm that the updated configuration—not another older one—is active.

If a subscription update fails, check whether the error concerns a network request, permissions or format parsing. For a failed request, check your device's local network and access to the dashboard. For a permissions issue, check your plan status and whether the link has been reset. For a format issue, confirm that you copied the option compatible with your client. If the old configuration still works, keep it for comparison rather than deleting it. A support ticket only needs the error text and the step where it occurred; do not include the full subscription. Avoid importing and starting the configuration in several apps at once, as this can make it difficult to separate configuration problems from network takeover conflicts.

After a successful subscription update, confirm that the route list has appeared and the configuration is enabled. Seeing “Saved” does not mean the configuration is active.

What to do if your credentials are exposed

If you have posted a subscription in a public place, first check the dashboard for an option to reset the subscription or update its access credentials, and follow the instructions. If there is no such option, contact support through a ticket. After a reset, each of your clients will need to fetch the configuration again; the old URL may no longer work. Deleting a public post does not guarantee that copies of the URL are unusable. Changing your account password alone does not necessarily change subscription credentials. Check the account password and subscription access credentials separately, then confirm that none of your devices is still using an old configuration.

At the end of this stage, you should have a recognizable local configuration obtained from the dashboard and updated successfully, and know which client stores it. Do not copy a real subscription into a public cloud document as a backup. Back up the instructions and display name, not the sensitive credentials; store those securely. The next section covers installation, permissions and import on each platform. If you already have a client installed, still check the platform permissions: a correct configuration cannot connect if the system has not allowed the client to manage network traffic.

Import and permissions for each platform

Get the instructions and client for your device from the user dashboard client page. Supported platforms are Windows / macOS / iOS / Android / Linux. Choose the option for your current device; do not rename an installer for another operating system and try to use it. Once installation is complete, open the app and import the configuration from the previous section. Client menus may change, so look for the equivalent actions to add a subscription, update the configuration, choose a route and connect. The interface does not have to match this guide word for word.

Windows: install, import and system proxy

Choose the Windows option in the dashboard, follow the download page instructions to install the client and open it. If the system asks for permission, verify that the app and requested action are expected. Do not disable system protections just to address a routine import issue. In the configuration area, add the subscription and update it. Confirm that the route list appears, then choose a route. If you use system proxy mode, make sure the corresponding client option is enabled; a background process alone is not enough. Apps outside your browser may not use the system proxy, so check them separately. If you want the client to launch at startup, enable this after confirming the connection works and check the result after signing in to Windows again. See the Windows setup guide for beginners for more details.

macOS: app permissions and network extensions

Get the macOS client and follow the system prompts to install it. If macOS asks you to approve the app or network-related permissions, verify in System Settings that the request comes from the client you are using. Import the subscription, update it, choose a route and check the connection status. If you see a message that the network extension is disabled or permission was denied, resolve it in the relevant settings rather than pasting the subscription again. If you have other network tools installed, pause their traffic management first and check the current client. Closing its window may only hide the app; it may not disconnect. When you are finished, disconnect explicitly in the client and check the system's network status.

iOS: import and VPN configuration permission

Open the dashboard's client page on your iOS device and follow its instructions to get the app and import your subscription. If direct import prompts you to choose an app, confirm the target. If it cannot open the app, add the subscription manually in the client. When you connect for the first time, iOS may ask permission to add a VPN configuration. Check the app name before allowing it. After updating the subscription, choosing a route and connecting, verify access in the target app instead of relying only on the status bar icon. If access fails after switching networks or waking the device, check the client status first, then try reconnecting. Do not enable multiple VPN configurations at the same time to address one problem.

Android: connection permissions and background limits

Get and install the Android client, import your subscription, update the route list and choose a route. When Android asks for permission to connect, make sure the request comes from the client you are using. If the connection works in the foreground but drops after the screen locks, check the system's battery optimization, background activity and data restrictions for the app. Allow the background operation it needs in your device settings. Menu locations vary by device, so look up the relevant setting rather than following a screenshot from another manufacturer. Lock the screen again after making changes, then reopen the target app and check access. For more help, see the Android subscription import and battery settings guide. Do not mistake background restrictions for an invalid subscription.

Linux: desktop and terminal workflows

Linux users should first check whether the client instructions in the dashboard apply to their environment, then install it as described. With a graphical client, follow the usual sequence: add a subscription, update it, choose a route and connect. If you need to use the terminal, follow the instructions for your environment in the dashboard and do not run installation scripts from unknown sources. Terminal apps may not automatically use the desktop system proxy, so check the app's proxy options or environment settings. For a temporary test, limit changes to the current session and restore them when you are done. Do not add unchecked network settings to system-wide startup files just to make one command connect.

On every platform, check import success separately from connection success. If no routes appear after import, return to the subscription section. If routes are listed but the connection will not establish, check system permissions and other network tools. If the client says it is connected but an app still uses your regular network, check how traffic is routed. During setup, do not change your subscription, DNS, split-tunneling rules and system permissions all at once. Otherwise, even if the connection starts working again, it will be hard to identify why. Start with the client's recommended basic settings and make other changes one at a time after verification. To set up another device, get a fresh configuration from the dashboard rather than sharing a full screenshot that contains sensitive information.

You have completed this section when the current platform shows active routes, the required system permissions are in place, the selected configuration is enabled and only the intended client is managing network traffic. Unlimited devices does not mean you should run multiple network-management clients on one device at the same time. You can set up other devices separately, but each needs its own permission and exit-route checks. Once connected, note the local display name and connection method. Keeping this non-sensitive information makes it easier to recreate your setup after a system update, when switching devices or when restoring settings.

Connection status and exit-route checks

Start with a baseline you can compare

Before enabling the client, check that your existing network can reach the sites you use every day, and close any other tools that manage network traffic. This gives you a point of comparison: if ordinary websites still fail when the client is disconnected, the issue may be with your local network rather than an international route. Once the local connection is confirmed, enable your current subscription, choose a route and connect. A connected status in the client is only an initial check. Next, verify the actual exit route and target app. Avoid repeatedly changing regions and modes during testing; keep the current settings steady so you can reproduce the result.

Open this site's My IP page to see the available exit information and compare it with your selected region. If the lookup fails, that does not necessarily mean the connection is down; the lookup service may be unreachable or the browser request may have failed. Check the target app as well. If the displayed information is not what you expected, first check whether your browser uses the system proxy, is excluded by a split-tunneling rule or is showing a cached page. Reload the page and check again, or use a fresh browser session for comparison. A changed IP address alone does not prove that every app uses the same route.

Test the app you actually want to use

After checking the exit route, open the app you need. For AI tools, test that the page loads, you can sign in and a normal request works—not just that the home page appears. For streaming, check that the specific content starts playing and continues, not just that its thumbnail loads. For apps that need a persistent connection, keep the session open and check how it recovers. If the home page loads but a feature fails, note what you tried and the message shown. This helps distinguish a network timeout from a regional restriction or account permission issue. See the AI Tools guide for related scenarios. Do not treat a paid feature or permission issue on the target platform as a route failure.

A browser, desktop app and terminal on the same device may use different network paths. If the browser works but another app does not, check that app's proxy settings before changing your subscription. A system-proxy-only mode may not cover apps that ignore system settings; broader network routing may require additional system permissions. Identify the current connection method and test apps one at a time. If an app has its own proxy configured, check or reset that setting first to prevent it from overriding the route provided by the client.

Narrow down the issue by its symptoms

If the connection will not establish at all, first check your plan status, subscription update and system permissions, then compare with a route that uses a different path. If only one website fails, check its message and account requirements before testing another region. If the connection drops after working for a while, check for network changes, wake-from-sleep behavior and background restrictions. If performance changes during peak hours, compare routes on the same device, app and network without adding extra tasks such as large downloads. Change one factor at a time so you can tell whether the result came from your route choice or a local change.

Testing is not about chasing a single number at one moment. Whether a page loads, an app can keep making requests and a video plays without repeated interruptions is more relevant to everyday use than an isolated speed test. This guide makes no fixed latency or bandwidth promises and does not permanently rank one region as the best. Keep the name of a route that works for your needs, then compare it using the same task if results change. For live sports, pay particular attention to continuous playback and viewing time. See the guide to choosing a route for live sports; one page load does not predict the experience for an entire event.

Change only one thing at a time when troubleshooting: the route, mode, app or local network. Keep the original settings so you can compare results and restore them if needed.

If you need help through a support ticket, include your device platform, the step where the issue occurred, the status shown in the client, the target app's message and what you have already tried. You can attach a screenshot with sensitive details obscured, but do not upload passwords, full subscription links or detailed logs containing sensitive URLs. If the problem occurs only on one local network, mention that comparison too. After checking the connection, note a working route and mode, then confirm that your regular network works again when the client is disconnected. This baseline will help with maintenance and any advanced changes in the next section.

Everyday maintenance, data use and renewals

Keep account status and device status separate

You do not need to reinstall the client for routine use. Start by checking your plan status, remaining data and billing period in the account, then check whether the local configuration can update and whether the selected route still fits your needs. Monthly plan data resets each month on the activation date; data packages last until used and never expire. Check each option accordingly. Local data counters in the client may use different calculations from the dashboard, so do not rely on them alone to estimate your allowance. Use the dashboard to check available data and orders, and contact support through a ticket if anything is unclear.

When checking data use, review your recent activities rather than immediately upgrading your plan. Video playback, media uploads, file downloads and background sync can all cause noticeable changes. With unlimited devices, activity on your other devices also matters. If a device runs in the background for long periods, check whether the client is still enabled and whether it is syncing continuously. For tasks that do not need acceleration, review their routes in the advanced section. Do not disable essential system maintenance just to save data, or route every app through the client and then guess which task caused the increase.

Update the configuration without losing a working baseline

If the client reports that a configuration update failed, first check dashboard access and your current plan rather than assuming the app is broken. After an update succeeds, confirm that the route list is intact, the current configuration is still enabled and any saved or manually selected routes have not changed unexpectedly. Updating the client and updating the subscription are different operations: the former changes the local software; the latter fetches your account's route configuration. Follow the dashboard's guidance for client updates. Before installing one, note your current mode, configuration display name and custom rules. Afterward, verify the connection again as described in the connection section.

Do a quick check after an operating system update, waking from sleep, switching Wi-Fi networks or installing another network tool. Check the client status first, then test the target app. If something is wrong, check permissions, background restrictions and network-management conflicts before deleting the account configuration. Treat a setup that has worked reliably as your recovery baseline, and record the purpose and result of each new change. If a change does not help, revert it instead of adding more rules. The more complex the configuration, the more important it is to know what each change is meant to fix; otherwise, problems become harder to trace.

Review the confirmation details before renewing or upgrading

To renew, sign in to your original account and open the plans page in the dashboard. Do not create another account just to keep using the service. Check your current plan, the product you want and the order details before confirming. Monthly plans and data packages have different billing rules; do not assume that renewal, a tier change and switching products have the same effect. Mid-cycle upgrades convert the price difference into remaining days. Follow the confirmation shown in the dashboard. If the page does not match your expectations, stop and ask support about the difference rather than trying to explain the remaining time or amount due with your own calculations.

After payment, repeat the checks from the account section: confirm that the original order succeeded and the plan details in your account have updated, then check the client connection. If the plan is active but the device still shows the service as unavailable, try updating the subscription and enabling the configuration again. Do not treat a screen that has not refreshed yet as a reason to reinstall the client. Conversely, the fact that an old client can still open a page does not replace checking your account status. Keep product and order records over time so you can distinguish renewals, upgrades and changes in billing options.

Switching devices, unused devices and credential management

When switching devices, get the client and subscription from the dashboard on the new device, then complete its permissions and exit-route checks separately. When you stop using the old device, sign out of the user dashboard, remove sensitive configurations and clear any saved browser credentials as appropriate. Take particular care with borrowed devices or devices you plan to hand over. If a subscription remains on a device you can no longer control, check the dashboard for a reset option or contact support through a ticket. Unlimited devices is not a reason to share credentials publicly; you are still responsible for keeping your account and subscription secure.

Maintenance records only need your setting names, route names and the symptoms you observed. Never put passwords, real subscription links or payment details in public notes or chat screenshots.

Make routine maintenance simple: check the current status before use, return to a verified baseline when something changes, confirm delivery after renewing, and clear old credentials when switching devices. If you need help, sign in to the user dashboard support page and say whether the issue followed a client update, network change or order action. The service offers a 30-day no-questions-asked refund; see the terms for details. This maintenance guide does not add any refund conditions. Once these basics are covered, consider advanced rules only if needed; complex settings are not a prerequisite for everyday connections.

Split tunneling, DNS and advanced settings

Start with rule mode and adjust to solve a specific problem

Advanced settings should come after you have verified a basic connection. Rule mode generally uses conditions such as domains, addresses or apps to decide where requests go. It is useful for separating traffic that needs an international route from other requests. Global mode sends the requests covered by the current mode through the selected route, which can help with a temporary comparison. It does not necessarily cover all system traffic; coverage still depends on how traffic management is configured. Direct mode restores or checks your regular network. Client terminology varies, so read the current app's guidance before deciding what each mode actually does.

Before changing rules, identify the specific problem you want to solve—for example, an app not using the proxy, a device on your local network that cannot be reached or a domain classified incorrectly. Copy or note your existing non-sensitive settings, then change only the relevant item. Rules usually have a matching order: an earlier match may prevent later rules from taking effect. After adding a rule, check not only its contents but also its position and whether the active configuration has loaded it. Do not combine rule lists you do not understand or use global routing long term to hide an app's separate proxy settings.

System proxy and broader network routing

A system proxy mainly serves apps that follow the system settings. Some terminal tools and desktop apps need separate configuration. Broader network routing may use a virtual network interface to handle traffic and require corresponding system permissions. Whether to enable it depends on client support and your needs; more settings do not necessarily make a connection more reliable. After enabling it, check your local network, printers and frequently used apps. If only one tool needs a proxy, check its own proxy settings first rather than changing the network path for the whole system.

Local network access issues can arise after expanding the scope of network routing. When accessing local shares, device management pages or workplace resources, check whether traffic is being sent to an international route by mistake or whether local name resolution is affected. Before making changes, disconnect the client and confirm that your regular network works. If it works normally without the client but not with it, check split-tunneling exceptions. Do not casually delete system routes or disable network security settings. If a device must follow workplace network policies, follow your administrator's requirements; an app working is not permission to change those policies.

DNS troubleshooting and certificate warnings

DNS translates domain names into addresses. If name resolution and request traffic take different paths, pages may fail to load or region detection may not behave as expected. If one domain fails, first check whether the client reports a resolution error, then review the DNS settings recommended for the current configuration. Do not copy server addresses found online into every device, or mix system and client settings without understanding the existing setup. After making a change, reload the target app and compare the result. Do not draw conclusions about the entire connection from a label on a single lookup page.

If your browser warns about a certificate, first check the URL you entered, the device clock and the target service's status. Network routing is not a reason to ignore certificate warnings. When testing HTTPS access in a terminal, keep certificate verification enabled. The command below requests response headers from a public example site and can only help you check whether a connection completes over the terminal's current network path. It does not show that your browser uses the same path, or prove that your subscription, target account or every app is working. The command uses a public example address and contains no 88888888VPN subscription credentials.

curl --head https://example.com

Keep a working setup for each use case

AI image generation can involve web pages, task requests and persistent sessions, so test the actual workflow. For Midjourney and Discord, see the AI image generation and Discord connection guide, but do not treat any route as a permanent guarantee. Streaming also depends on available content and account region; see the Disney+ region and connection stability guide. Keep a combination of route, mode and app settings that works for your needs. Recheck it if the target service changes its policies, and do not assume old results will remain valid.

If several apps stop working after an advanced change, first undo the most recent change and restore the baseline confirmed in the connection section. Once the basic connection works again, add necessary settings one at a time and note what each one does. When contacting support, mention whether you use custom split-tunneling rules, additional DNS settings or other network-management tools. That background is more useful than a large volume of unfiltered logs. The complete workflow is now in place: your account and plan provide access, the subscription provides configuration, the client connects, verification confirms the result, and maintenance and advanced settings help you adapt to changes. Return to the relevant section in the contents whenever you need it, or review the main steps in the quick-start guide.