The complete VPN user guide.

How the service and your connection work together

Understand cross-border network services.

First, understand the difference between your account, subscription, and client

VPNShunshun provides subscriptions for cross-border network acceleration. Your account is where you manage plans, orders, and support tickets. Your subscription gives your client access to available routes and related settings. The client handles the connection on your device. These are linked, but they are not the same thing. Being able to sign in to the dashboard means your account is accessible; it doesn’t mean your device is routing traffic yet. Likewise, a client showing as connected isn’t enough: make sure the subscription is valid, a route is selected, and the app you’re using is actually following the intended path.

Think of a connection as a chain of handoffs: your device joins the current network, the client reads its configuration, and rules direct each request to the appropriate route before it reaches the destination. A problem at any point can make a website appear unreachable. Troubleshoot one link at a time instead of changing every setting as soon as an error appears. Once you know where the problem starts, you can choose the right next step.

Coverage doesn’t guarantee the same result in every situation

The service covers 90+ countries / 220+ routes and supports Windows / macOS / iOS / Android / Linux, with unlimited devices online at once. Coverage describes the routes available to choose from; it doesn’t guarantee access to every site from every location or local network. A destination service may have its own account-region, licensing, or risk-control requirements. Those checks are separate from network connectivity and can’t necessarily be resolved by changing your exit route.

IEPL, relay, and direct routes are common labels for understanding how traffic is routed. They can help narrow down your options, but they don’t guarantee a particular experience. Your home or office network, wireless signal, and destination all affect the result. Check the network page and the current list in your dashboard for specific regions and route types. Don’t infer a city, exit characteristics, or support for particular content from a route name alone.

Rule mode vs. global mode

Rule mode routes requests differently according to the configuration. Global mode generally sends requests handled by the client through the selected route. Global mode doesn’t necessarily capture every app on your device: system proxies, virtual network interfaces, and app-specific proxy settings work differently. For everyday use, keep the dashboard configuration and the client’s default recommendations. Change modes temporarily only to troubleshoot, and note what you changed and what happened.

A browser may load pages while a desktop app can’t connect because they use different network paths. Conversely, an app may work while a website has trouble due to browser cache, extensions, or the site’s account status. Don’t assume that these differences mean the entire route is down. Test on the same device, with the same route and similar conditions, and check both whether the client is handling traffic and how the target app behaves.

Establish a baseline you can restore before you start

Before you begin, make sure your device can reach the websites you normally use, its clock is correct, and your current network doesn’t require a separate web-based sign-in. Note any existing proxy settings. If you have other networking tools installed, disconnect them first. Multiple tools running at once can compete for the system proxy or network interface and send requests in circles. A simple, well-understood starting point is easier to troubleshoot than several connection switches turned on at once.

VPNShunshun follows a no-logs policy. See the Privacy Policy for details about how data is handled. A privacy policy and the security of your personal information are separate concerns: keep your account password, subscription details, and browser sign-in sessions safe. A network service doesn’t replace your account permissions on other sites, device updates, trusted software sources, or everyday account security practices.

By the end of this chapter, you should be able to pinpoint where you’re stuck: signing in to the dashboard, finding your subscription, configuring the client, or using an app after setup. Identifying the right stage cuts down on trial and error and makes it easier to describe the issue in a support ticket. Next, choose a billing option that fits your needs before moving on to your account and payment.

Choose a plan that fits your usage

Plans and data usage.

When to choose a monthly plan or a data pack

A monthly plan suits regular use when you want to manage your data month by month. Plans include ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB. Data resets monthly on the day you activated the plan, not on a fixed calendar date. Check the activation and reset dates in your dashboard rather than guessing from the month on the calendar. A data reset also doesn’t mean your paid order renews automatically.

A data pack works well if your usage is irregular and you’d rather draw down a set amount over time: ¥158/300GB, ¥358/1000GB, or ¥658/3000GB. Data lasts until it’s used and never expires. That refers to the validity of the data pack, not unlimited data. Before ordering, check the dashboard for details on whether a pack can be used alongside an existing plan and how data is deducted. Don’t assume that plans stack unless the terms say so.

Start with what you do online, then choose a data tier

Text-based websites, remote collaboration, file transfers, and extended video streaming all use data differently. Before choosing, make a list of the things you do online most often and note whether apps sync files in the background. HD video, cloud storage syncing, and large file transfers can account for much of your usage, but this guide doesn’t estimate a fixed amount based on viewing time: quality, encoding, app caching, and transfer settings all affect data use. Use your dashboard’s usage records as your guide.

When you’re getting started, don’t assume you need a particular tier just because you have multiple devices. Unlimited devices means there’s no device-count limit on simultaneous connections; it doesn’t change how data is metered under your plan. Devices transferring data at the same time still use the plan’s data. A better approach is to distinguish devices you use occasionally from those that transfer data for long periods, then adjust based on usage in your dashboard.

Likewise, a higher-priced plan doesn’t automatically mean a faster route. The listed facts cover price and data, not speed guarantees or dedicated resources for any tier. If you’re looking for a particular route type, check the plan page and dashboard for details. Inferring protocol, exit quality, or access results from price alone can muddle billing questions with network issues and leave you with the wrong plan.

Check upgrades, refunds, and payment details before checkout

If you upgrade a monthly plan mid-cycle, the price difference is converted into remaining days. Before submitting, review the dashboard’s calculation of the updated validity period and order amount; don’t try to replace the system’s calculation with simple subtraction. If you have an unfinished order, check its status before deciding whether to continue payment or choose again. This helps avoid duplicate orders. If the total doesn’t match your understanding, keep the order details and check with support before proceeding.

The site accepts Alipay / WeChat Pay / USDT and offers a 14-day money-back guarantee. See the Terms of Service for the full refund terms. A refund policy doesn’t replace the need to verify your connection. Check that your usual devices and apps work early so you can make an informed decision. For prices, billing periods, and data terms, cross-check the plans page and the order confirmation before submitting.

If you don’t have usage history yet, start by identifying your main needs, then check how your data changes once you’re connected. Remember to account for background syncing, not just the pages you open. For a closer look at free and paid options, read Free vs. Paid VPNs: A Cost Comparison and consider how each service model fits your needs.

Create your account and check your order

Account setup and payment.

Create your account through the right channel

Use the site navigation or the user dashboard to open the account creation page. VPNShunshun doesn’t require an email address; create an account with a username and password. Before submitting your details, check that the browser address belongs to this site. Don’t enter account information through a similar-looking link from an unfamiliar message. Save your username and password in a trusted password manager rather than relying on your browser to remember them.

Because account creation doesn’t require an email address, don’t assume you can recover access by email. Before signing out, make sure you’ve saved the complete, correct credentials. Watch for full-width punctuation, extra spaces, and differences in capitalization. If you use a password manager, check that it fills in the credentials for this site rather than a similarly named account elsewhere. Avoid staying signed in on a public device.

After creating your account, open the overview page and confirm which account is signed in before choosing a plan. If your browser has saved another account, it may still be using that session. Orders, subscriptions, and support tickets belong to the account you’re currently signed in to; using the same device doesn’t make them part of the same account. If you’re signed in to the wrong account, sign out normally and sign in again before paying.

Confirm the plan and payment separately

In the plans section of the dashboard, check the billing type, data allowance, and amount before placing an order. Don’t distinguish a monthly plan from a data pack by price alone; reread the order summary, especially after changing your selection. If you’re upgrading, check how the remaining days are calculated. Don’t assume the order includes discounts, extra data, or extensions that aren’t explicitly shown on the confirmation page.

Choose Alipay / WeChat Pay / USDT and follow the instructions on the current order page. If you switch to a payment app, keep the original order tab open so you can return and check it afterward. A completed transaction in your payment app and a completed order in the dashboard are separate statuses. Return to the order page to confirm the result rather than relying on a redirect or browser notification.

If you pay with USDT, carefully check the recipient details, network requirements, and amount shown for the current order. Don’t send funds based on an earlier order. Each order page may show different details, and an old screenshot isn’t a substitute for the current payment instructions. This guide doesn’t provide a wallet address or fixed network parameters. Confirm all payment details in the current dashboard flow. If anything is unclear, stop and ask support before proceeding.

What to do if your order status doesn’t update after payment

Return to the dashboard and check whether the order is complete and the plan appears in your overview. If your payment app shows a completed transaction but the dashboard still says pending, keep the order ID and payment receipt, then refresh the order status normally. Don’t pay again straight away. A network switch, blocked redirect, or interrupted session can leave the page showing an outdated status. Signing in again can confirm your session, but don’t create another identical order to replace the original.

When contacting support, explain which payment method you used, the order’s current status, the steps you took, and whether the payment app shows the payment as complete. Redact personal information that isn’t needed to review the issue. Don’t share your password, subscription details, or full payment credentials in a public forum, or with anyone whose identity you can’t verify. A support ticket doesn’t require you to share account access.

You’re done with this chapter when you can find the matching order in the correct account and see an active plan in the overview—not just when you’ve been redirected to a payment page. Next, get your subscription. If the plan isn’t showing yet, setting up the client won’t resolve an account-side issue. For common questions about refunds and billing, visit the Help Center.

Add your account configuration to your device

Getting your subscription and updating your configuration.

Your subscription isn’t a public URL

Once you’ve confirmed the plan in the right account, find the subscription link in the dashboard overview. It gives your client access to routes and rules linked to your account, so treat it as sensitive information. It isn’t a public download link to share in a group chat or a page to show others which plan you have. If you need help, describe what happened during setup instead of sharing the subscription itself.

A subscription URL, a shared node configuration, and a local configuration file may all be recognized by a client, but they serve different purposes and update in different ways. Using the subscription link in your dashboard usually makes it easier to receive route changes later. A manually saved configuration for one route may not update when the subscription refreshes. Unless you know where a configuration came from and how it’s maintained, don’t mix configurations from different sources under the same name. You may not be able to tell which one you’re using later.

Use the import option first; paste it manually only if needed

Install the site’s client for your platform, then choose the corresponding import option in the dashboard. If your browser asks to open an external app, make sure it’s the client you installed before allowing it. Opening the app is just the start: confirm that the new configuration appears in the client and that its name, route list, and update status look right. If the dashboard offers multiple import options, choose the one that matches your client instead of guessing based on button placement.

If the client doesn’t open automatically, check that installation finished, that the app opens on its own, and that your browser didn’t block the request to open it. Try starting the client first, then return to the dashboard and try again. If that doesn’t work, use the dashboard’s copy-subscription option and paste it into the client’s subscription or configuration manager. Don’t add quotation marks after copying, and don’t paste the dashboard page URL in place of the subscription.

Before importing manually, check for line breaks, missing characters, or extra spaces, especially if you copied the link between devices. Some messaging apps change how links are displayed, and text recognized from a screenshot may not be accurate. When possible, sign in to the dashboard on the device you plan to use and get the subscription there to reduce extra handoffs. Clear the copied subscription from your clipboard when you no longer need it, and don’t store it in a publicly shared notes app.

Tell apart a retrieval failure from an incompatible format

If the client can’t retrieve your subscription, first check whether your device can reach the dashboard, whether your account is still active, and whether the copied content is complete. If the dashboard opens but the client can’t download the configuration, the issue may involve the client’s network path, the system proxy, or the retrieval method. Disconnect other networking tools, keep your local connection available, and try updating again. Don’t turn on multiple proxies that depend on one another just to retrieve the configuration.

If the content was retrieved but the client reports a parsing error, unsupported fields, or an empty configuration, check whether the import method matches your client. Clients can support different configuration formats and extension fields; changing a filename won’t convert a configuration. Return to the dashboard and choose the matching import option, or download the site’s client again. Keep any configuration that still works before updating so you don’t overwrite a usable setup.

Updating your configuration doesn’t mean you need a new account

Route names, groups, and rules may change when you update your configuration. Before updating, note the configuration name and route that currently work. Afterward, check that the route list has loaded and that your previous selection is still there. If an old name has disappeared, don’t assume there’s a problem with your account. Review the new groups and descriptions, and check the network page if needed. Confirm the new configuration works before deleting the old one.

Whether local rule or group changes survive a refresh depends on how the client manages configurations. If you’re unsure what will be overwritten, don’t edit the main content generated from your subscription. Prefer a clearly labeled local override or separate rules option in the client, and keep a record of your changes. Keep the service subscription separate from your personal customizations so you can tell whether an issue came from an updated route or a device-specific setting.

Before moving on, make sure you have a client for your platform, can retrieve the subscription, and know which account you’re using. A successful update and a visible route list are key checks at the import stage. Whether traffic from your apps is actually being handled is a separate question for the connection-check stage. Don’t confuse “imported successfully” with “access works.”

Handle system permissions and importing separately

Set up the client on your platform.

Get the site’s client from the client section of the dashboard; don’t install a similarly named download from search results. You can download the site’s client after signing in on all platforms except iOS. To get your subscription, sign in and open the relevant account page. The dashboard determines current access for iOS. Client menu labels can differ across system versions and app updates, so the steps below follow these functions: manage configuration, import subscription, choose a route, and enable the connection.

Windows: Load your configuration, then check how traffic is handled

Download and install the client as instructed, then open it on its own and make sure the main screen loads. Return to the dashboard and use the import option, or add the subscription from the client’s configuration manager. When the route list appears, set the new configuration as active and choose a route. Don’t stop at saving the subscription: some clients keep multiple configurations, and the selected one determines which rules are in use.

Enable the system proxy or the client’s recommended connection method, then test with a browser you use regularly. If the browser works but another app doesn’t, first check whether that app follows the system proxy rather than changing the entire configuration. If additional system permissions are needed, read what they’re for before approving them. Work-managed devices may restrict network interfaces or installations; follow your organization’s device policies. For a more detailed walkthrough, see the Windows Setup Guide: Start to Finish.

macOS: Launching the app and granting network permissions are separate steps

In the client section, choose an installer that matches your system and device architecture. Follow the system’s instructions to install and open the app. The first time you connect, macOS may ask you to approve a network configuration or extension. Check the app name and source before proceeding. Seeing the app in your Applications list doesn’t mean it has network permissions, and seeing routes after importing doesn’t mean macOS has allowed it to handle traffic.

If the connection switch won’t stay on, check System Settings for a permission request that still needs approval and see whether another networking tool is active. Don’t use unknown Terminal commands to bypass system protections. Keep the default configuration, test your browser and commonly used Apple services, then consider adjusting split routing. For help choosing network extensions and checking device compatibility, read the Mac VPN Guide.

iOS: Follow the current option shown in the dashboard

After signing in, open the client section and follow the option currently shown in the dashboard. If it says you need to meet current access requirements, check your account and plan status instead of looking elsewhere for a supposed universal download link. After installing the app, return to the dashboard and import your subscription. Allow it to open the relevant app, then confirm the configuration was saved. If iOS asks to add a VPN configuration, make sure the request came from the client you just opened.

Choose a route, turn on the connection, and test the app you want to use. If the connection status changes when you leave the client, check VPN status in iOS Settings and the client’s own message rather than relying on the status-bar icon alone. After switching between Wi-Fi and mobile data, check whether the app works again. If there’s a problem, return to the client and check its configuration and route instead of repeatedly deleting system settings.

Android: Approve the connection and check background restrictions

Get the site’s client from the dashboard and follow the installation instructions on your device. The first time you connect, Android will ask to establish a VPN connection. Check which app is requesting access, then approve it. Import your subscription, select the active configuration, and choose a route. If another VPN app is already running, disconnect it first so the clients don’t compete for the system connection. Installation and connection permission are separate steps; check both.

If things work while the app is open but the connection often drops after you lock the screen or switch apps, check your device’s background activity and battery settings for the client. Menu names differ by device, so read the system’s explanation instead of following screenshots from an unknown model. Adjust permissions only for the client that needs to stay connected. Don’t disable security settings across the board to troubleshoot a network issue, and verify that each change actually helps.

Linux: Separate desktop apps from terminal tools

Sign in to the dashboard to get the client. Check that the download matches your system, then install and launch it as instructed. Import the subscription and test with a desktop browser first, then check your terminal tools. A desktop system proxy may not carry over to an existing terminal session, and command-line tools may use their own proxy settings. If a website works but a command-line tool fails, check which network path the tool actually uses before changing routes.

The commands below only check proxy variables already set in the current shell. They don’t create a connection or replace the client configuration. If the output includes internal addresses or account details, redact them before sharing. If you find an old value, check whether it’s needed for your work environment before changing it. Don’t remove system-wide settings without understanding their purpose.

printenv http_proxy https_proxy all_proxy HTTP_PROXY HTTPS_PROXY ALL_PROXY no_proxy NO_PROXY

From connection status to working access

Verify your connection and find the cause of issues.

Don’t rely on the connection switch alone

When the client says the connection is on, it usually means that a connection feature has started—not that every destination is reachable as expected. Check the active configuration, route, and mode first, then open a familiar website. Next, test the app you actually need. Testing a basic website separately from the target app helps distinguish a general network problem from an issue with one service. Don’t mistake an account problem on the destination site for a route issue.

Use the site’s IP lookup page to check the current browser exit address. The result only describes the route used for that web request; it may not reflect the path taken by terminal tools or other apps. If the address hasn’t changed, first check whether the browser is using the client and whether the rules route the lookup request as expected. A location label for one address doesn’t prove that every app’s traffic is being handled.

Narrow down the problem by its scope

If every website is having trouble, disconnect the client and make sure your local network works on its own. If it doesn’t, troubleshoot Wi-Fi access, network sign-in, or your router first; switching international routes won’t restore a local connection. Once your local network is working, reconnect the client and check whether the subscription updated, the plan is active, and another networking tool isn’t using the system proxy.

If only one app fails, note the type of error: can’t connect, DNS lookup failed, sign-in rejected, or content unavailable. Different errors call for different next steps. For a connection timeout, check traffic handling and the route. For a sign-in rejection, review your account and the service’s rules. Content may be unavailable because of regional licensing. Don’t treat every error as a reason to “switch to another country.”

Keep conditions comparable when switching routes

To compare routes, keep the device, app, destination, and local network as consistent as possible, and change only the selected route. Note which route connects, whether you can complete the action you need, and whether the connection drops during use. Don’t change the mode, update the configuration, and restart the router all at once. Even if things start working, you won’t know which change helped. A result you can explain is more useful than a one-time page load.

IEPL, relay, and direct routes are useful categories for comparing paths, but route labels don’t guarantee reliability. When choosing a route, start with the destination region and how it performs for your needs, then consider whether it works well over time. Assess performance during busy evening periods through repeated tests under similar conditions, not one quick page load. For guidance on structuring your tests, read How to Test Connection Success and Dropouts.

How DNS, cache, and old sessions can affect results

DNS translates domain names into addresses that can be reached over a network. A lookup failure doesn’t mean your account is inactive or that the route is completely down. First use the configuration’s default settings, check that your device clock and local network are correct, then reconnect. Don’t combine custom DNS settings from multiple places unless you know why you need them. System, browser, and client settings can interact and handle the same domain differently.

After switching routes, an app may keep using an old connection or cached data. Fully quit the app and reopen it. If needed, compare in a temporary browser session, keeping in mind that you may need to sign in again. If the client provides a connection list, check whether new requests appear. Don’t stop system services if you’re unsure what they do. Confirm the new session is using the new route before deciding whether switching helped.

If you still can’t identify the issue, use the support ticket form to share your operating system, active client configuration, selected route, mode, target service, and full error message. Say whether your local network is working. Include only the relevant part of any logs, and redact your subscription, password, and personal information. A clear set of steps to reproduce the issue helps pinpoint the cause; there’s no need to reinstall your whole system or make sweeping changes first.

Keep a working configuration

Everyday maintenance, renewals, and multiple devices.

Track data, plan validity, and connection status separately

A connection that worked before doesn’t mean you can stop checking your account. For routine maintenance, first check your data usage and plan status in the dashboard, then see whether the client can update its configuration. Monthly plan data resets on the activation date; that’s different from the plan’s validity period. Data packs last until used and never expire. Seeing route names in the client doesn’t necessarily mean your account still has available data.

If data usage changes differently than expected, check cloud storage, system updates, media downloads, and background syncing on your devices. They may transfer data even when you’re not actively using them. Client or system network reports can help, but different screens may count usage differently. Don’t treat one app’s local counter as a billing record. If you have a question about account data usage, use the dashboard details when contacting support.

Check which account you’re using before renewing

Before arranging continued access in the plans section of the dashboard, check your current username, plan, and order status. A renewal, choosing a different plan, and upgrading mid-cycle can each produce a different total. Read the current order summary instead of relying on what you remember from your last payment. For a mid-cycle upgrade, the price difference is converted into remaining days. Check the amount shown before submitting rather than guessing the new validity period from the plan name.

After paying, check the order and account overview again. Then update the subscription in your client and verify the connection. If the account has updated but a device still shows the old status, try refreshing the configuration or reconnecting before deleting settings. Different devices may retain different versions of the configuration. If one works and another doesn’t, check each device’s subscription update time and active configuration instead of paying again.

Unlimited devices still need individual setup

There’s no device limit on simultaneous connections, so you can switch between computers, mobile devices, and other supported platforms. That doesn’t mean every device has the same network conditions. The same subscription can behave differently depending on system permissions, background restrictions, app proxy settings, and the local network. Set up and verify each new device separately instead of copying every custom setting from another device.

Give the configuration a recognizable local name and note how traffic is handled on each device to make troubleshooting easier. Names are only for your own reference; don’t put passwords or full subscription details in a configuration title. Before retiring, transferring, or repairing a device, clear the account configuration from the client and sign out of the browser. If you think someone else may have obtained your information, follow the dashboard’s options or ask support how to secure the subscription and account.

Keep a checkpoint before and after each update

Updating the client, updating the operating system, and refreshing the subscription are separate maintenance tasks. Don’t do them all at once and delete the old configuration while troubleshooting. Instead, note the current working state, make one change, then test the websites and apps you use regularly. If something breaks, you can check the permissions, configuration compatibility, and network path affected by that specific change instead of guessing among several unknowns.

When making backups, keep ordinary notes separate from configuration files containing sensitive information. It’s fine to save notes such as “rule mode, usual route, permission settings, recovery steps.” Store files containing subscription or account details somewhere protected. Don’t share an entire configuration folder publicly just to sync it across devices. After restoring a configuration, check that the subscription is still valid; an old backup isn’t proof that it will keep working.

What to expect from auto-start and network changes

If you want the client to connect automatically at startup, first make sure the manual connection process is reliable, then use the auto-start setting provided by the client or system. Auto-starting the app, updating the subscription, and establishing a connection may be separate options. After enabling them, test by signing out and back in or restarting. If the network isn’t ready when the system starts, the client may need to retry later. Don’t add a large number of background apps just to avoid that delay.

When you move from a home network to an office network, or switch from Wi-Fi to mobile data, you may need to reconnect. First make sure the new network works, then check whether the client recovers. When you’re not using the service, disconnect normally in the client and make sure the system proxy is restored. If websites stop working after you force-quit the app, check for leftover proxy settings rather than resetting your entire network configuration.

Add advanced options only after the basic connection is stable

Split routing, AI tools, and advanced settings.

Understand rule matching before changing it

Split routing sends different requests along different paths. Clients usually check rules in a specific order, so adding a rule doesn’t guarantee it will take effect: it may not match the domain the app actually uses, or another rule may match first. Before making changes, review the subscription’s existing groups and the client’s documentation. Change only the routes you need to. Don’t send all traffic through an untested route just to address one app.

Domain rules and IP address rules solve different problems. An app may use separate domains for sign-in, APIs, images, and updates, so routing only its homepage may not be enough. If a page loads but a feature doesn’t work, check the connection details available in your client to see which requests are involved before changing rules. If you’re unsure about the matching syntax, don’t paste a large set of rules from the internet over the main configuration; keep a working setup you can restore.

For AI tools, check the network path and the account

AI tools such as ChatGPT and Gemini may use separate requests for webpages, APIs, authentication, and file transfers. Loading the homepage doesn’t mean chat, uploads, or sign-in will work. Start with the default routing and try the task you need to complete. If it fails, note the step where it happens. If the client shows connection groups, check whether the relevant requests use the intended route. Don’t mistake an account restriction on the service for a failed subscription import.

If you need a stable session, avoid frequently changing exit regions while using the service. A destination may make decisions based on your account, regional policies, and session activity; a network route can’t replace those requirements. If you see a region warning, repeated verification requests, or an account notice, read the destination service’s rules before changing network settings. The service’s coverage doesn’t guarantee access to any particular AI feature or account eligibility.

Consider streaming access and content availability separately

Opening a streaming site, signing in, playing a video, and seeing content from a particular region are different outcomes. Content licensing, account settings, device capabilities, and app cache can all affect the experience. When choosing a route, test actual playback instead of checking only the homepage or cover art. If a title isn’t available, first check whether it’s offered in the target region and whether your account is eligible, then look at the route and app session.

After changing your exit route, an app may still use its previous regional settings. Quit and reopen it normally, and follow the app’s own instructions to clear its cache if needed. Don’t delete account data without a reason. Video quality can’t be judged from a route name alone; your local connection, playback device, and video encoding all matter. Streaming uses data, so keep an eye on your dashboard usage. Unlimited devices doesn’t mean unlimited data or guaranteed playback quality.

Treat router setup as an advanced compatibility check

The supported platforms listed in the service facts are Windows / macOS / iOS / Android / Linux. This doesn’t mean every router is supported. Before using the service on a router, check its firmware, supported software, configuration format, and required permissions. Router plugins with similar names don’t necessarily support the same fields. If you can’t confirm compatibility, use the site’s client on a supported device instead.

Router-level routing can affect other devices on the same network and may duplicate routing already handled by a client on your device. Before making changes, save your current network settings and make sure you can still reach the router’s admin page. Don’t turn on whole-network routing at the router and global mode on your device at the same time, then troubleshoot by guesswork. First decide which layer handles routing and DNS, and which devices should keep their usual path. Then test local network access and international services one at a time.

Only change terminal settings when you have a clear reason

Command-line tools may use environment variables, app-specific configuration, or the system proxy—or may not use a particular setting at all. Check the tool’s documentation to confirm how it handles proxies, then use the details shown by your client. Don’t guess the local listening address or port, and don’t copy parameters from someone else’s screenshot. If you use the device for work, preserve its existing settings so you don’t disrupt access to internal services.

Make advanced changes to answer a specific question: what are you changing, what result do you expect, and how will you undo it if it doesn’t work? After each change, test a basic website, a commonly used app, and local network features. If you can’t verify an improvement, restore the original setting rather than adding more parameters. For the full journey from setup to a working connection, revisit the Complete VPN Guide for Beginners. For help with a specific issue, visit the Help Center or contact support.