FTVPN Setup Guide

Understanding Cross-Border Subscription Services

How Accounts, Plans, and Clients Work Together

FTVPN is a subscription service for cross-border network acceleration, with coverage across 120+ countries and 160+ routes. The setup involves an account, a plan, subscription details, and a client. Your account stores orders and service status; your plan determines billing and data; your subscription provides routes to the client; and the client establishes a connection on your device. Knowing how these pieces fit together helps you identify whether an issue involves payment, syncing, or your device’s network.

The marketing site is where you can check prices, read about the service, and find links. The user panel is where you manage your service. Sign-in, plan selection, subscription access, client downloads, and support tickets are all handled in the panel. Links in this guide open the relevant panel page. If you aren’t signed in, authenticate first and then return to your destination. The website itself doesn’t connect your device to the network; opening it does not mean your device is connected.

A client is a separate app on your device. It reads the routes and rules in your subscription, then handles traffic according to its current mode. Whether your browser, editor, or other software uses the connection also depends on system proxy settings, app-specific settings, and client capabilities. So, a working panel doesn’t prove that other apps are using the same route. And even if the client says it’s connected, you still need to test it.

Understand the Connection Path

A typical connection involves the local app, device network settings, the network you’re connected to, the selected route, and the destination service. A change at any point can affect performance. For example, a weak Wi-Fi signal can affect every route; switching regions may not help if the destination site is down for maintenance. Troubleshoot by narrowing down the cause first. Reinstalling the client, changing rules, and switching accounts all at once makes it harder to compare results.

“Bank-grade encryption” is FTVPN’s security messaging, but connection protection doesn’t replace account security. Keep your password, subscription details, and device access secure. The destination website manages its own login activity, account region, and app permissions. The network connection and the destination platform are separate services. Route coverage does not guarantee access to every website feature, account eligibility, or regional content.

Unlimited devices means you can configure FTVPN on your own Windows, macOS, iOS, Android, and Linux devices. Each device still has its own controls, rules, and local permissions. Connecting your computer won’t automatically connect your other devices. If you use multiple devices, keep an eye on your account’s data usage, and remember that unlimited devices does not mean unlimited data.

Prepare a Baseline for Troubleshooting

Before you start, make sure your device can access the internet, the system date and time zone are reasonable, and you can save your account details. A significantly incorrect date can interfere with secure connection checks. If the network requires web-based authentication, complete that step first. If ordinary websites won’t load either, fix your local network before treating it as a route issue.

Keep a simple baseline note with your device’s operating system, client name, network, and target app. Record what you did and what happened, but don’t include your full subscription link or password. If a problem comes up later, you can compare what changed since it last worked instead of just noting that it’s broken. Pinpointing a change is usually more useful than trying more settings at random.

Choose a route for the task at hand. Web browsing, video streaming, and AI coding connections don’t behave the same way, and a route’s name is no substitute for testing compatibility. For details on regions and route selection, see the Nodes page. This guide takes you through the full setup first, then covers ways to fine-tune a working connection. Advanced settings aren’t required to get started.

By the end of this chapter, you should be able to distinguish between signing in to the panel, syncing your subscription, and connecting through the client. Next, just choose a billing option that fits your needs—you don’t need to learn every technical term first. Leave unfamiliar settings at their defaults until you understand what they do; that makes it easier to undo changes later.

Choose a Plan or Data Package

Start by Matching Billing to Your Usage

FTVPN offers monthly subscriptions and data packages. A monthly subscription suits regular, ongoing use of international websites and apps; its data allowance resets monthly on the activation date. A data package lasts until the data is used and never expires, making it a better fit for occasional use. First consider how regularly you’ll use the service, then estimate your main activities’ data needs. Don’t compare prices alone or infer unannounced discounts by converting between product periods.

Monthly subscriptions come with set monthly data allowances. Everyday reading, email, and text collaboration typically use data differently from extended video streaming or file syncing, but this guide doesn’t make up estimates for how long a plan will last. Video quality, file sizes, and background app activity all affect usage. If you have usage history, check your actual consumption in the panel rather than guessing based on time spent online.

Understand Resets, Upgrades, and Device Usage

“Resets monthly on the activation date” does not mean that data resets on the first day of each calendar month. After activation, check your current billing period and data in the panel before scheduling large downloads or video sessions. Don’t rely on the calendar to determine when data should reset, or on stale client data instead of the panel. If the panel and client don’t match, refresh your account details, save a screenshot of the discrepancy, and then troubleshoot.

When you upgrade mid-cycle, the price difference is prorated into the remaining days. This doesn’t let you calculate a new data allowance, expiration date, or refund amount yourself; use the order confirmation for the actual change. Read the change details before submitting and make sure you’ve selected the intended plan. If you don’t understand the amount shown, stop and ask through a support ticket rather than placing more orders to test the rules.

All plans support unlimited devices, but data usage is still tied to your account. Background syncing on a computer, video streaming on a mobile device, and other connected devices can all use data at the same time. If usage rises unexpectedly, first check your devices and activities, then check whether your subscription details may have been exposed. Deleting a client at random won’t fix usage if other devices are still connected.

“Never expires” describes the data package’s usage rules; it doesn’t mean you can ignore your remaining balance or that usage never consumes data. If you use the service occasionally, check your balance and make sure your route details are current before an important task. If it’s been a while since you opened the client, update your subscription and test the connection before a meeting, file upload, or remote work session—not when the task is already underway.

Check Payment and Refund Details

Payment methods are Alipay / WeChat Pay / USDT. Before paying, verify the product type, amount, and order status. In particular, don’t confuse a monthly subscription with a data package. If you need to manage more than one product, read the account change details shown in the panel first. This guide doesn’t assume products stack automatically or make claims about the order in which data is used. Don’t count on benefits that aren’t clearly shown.

FTVPN offers a 30-day no-questions-asked refund policy. For details on how to apply, read the Refund Policy and submit your question through the panel. A refund policy doesn’t replace checking compatibility before use, and a plan’s price doesn’t guarantee that a particular website will work. When choosing a plan, consider your device, target app, and network environment—not just the price.

If you’re unsure about paying for the long term, read our guide to choosing a long-term subscription to understand service continuity and budgeting. The products FTVPN offers are the monthly subscriptions and data packages listed in this chapter; discussing long-term use in an article doesn’t mean an annual plan is available.

Once you’ve chosen a plan, note the data tier and billing type you need, then move on to your account and order. The goal is to make a choice you can verify—not to buy a higher tier just to get more complex settings. Troubleshooting routes and configuring clients are covered step by step in later chapters.

Create an Account and Check Your Order

Save Your Account Details Before Paying

FTVPN doesn’t require an email address. Create an account with a username and password through the Start Free page, then follow the on-screen instructions. Choose a username you’ll recognize and a password you don’t use on other sites. Save your details as soon as the account is created. Don’t wait until you’ve closed the page to realize you didn’t record them, and don’t rely on staying signed in in your browser as your only way to access the account.

Your account details and subscription link serve different purposes. Use your username and password to sign in to the panel; use your subscription details to load routes into a client. They aren’t interchangeable. Don’t share your sign-in details when sharing a configuration, and never include your password in a support ticket. If you use a password manager, check that it saves the panel URL and the correct username so you don’t accidentally use credentials for another service with a similar name.

Not requiring an email address makes account creation easier, but it also means you shouldn’t assume email recovery will be available. Keep your username, order records, and any details you may need to explain an issue. If you can’t sign in, check your keyboard layout, capitalization, password manager autofill, and the domain you’re visiting. Then use the available support option in the panel. Don’t enter your account details on an unfamiliar site.

Use Your Order to Verify Payment

Open the Plans section in the panel and double-check the product type, data allowance, and price. The marketing page helps you compare options; the order confirmation page confirms the transaction you’re about to make. If you already have an active service, read any change details the panel displays so you know whether you’re renewing, changing plans, or taking another action. Don’t submit based on button placement alone—check the confirmation first.

Choose Alipay / WeChat Pay / USDT as appropriate and follow the steps on the order page. Use the payment details shown for the current order. Don’t use payment information from an unknown source or reuse details from an old order for a new one. If you have questions about the currency, amount, or status, check the current order before proceeding to avoid mixing up transactions across pages.

After payment, return to the panel to check the order status and confirm that your service and data have been updated. A successful status in your payment app and completion in the panel are separate steps; one page alone doesn’t confirm the whole process is done. If the statuses haven’t synced yet, refresh the current order page and check again. Don’t pay a second time just because you haven’t seen an update yet; that makes it harder to reconcile the transaction.

If the page closes or your network drops, return to the order history in your original account first. Check the product, amount, payment result, and order ID to see whether the order is already recorded before taking another step. Reopening your browser doesn’t mean the original order is gone, and signing out doesn’t cancel it. Keeping the original record makes an issue easier to trace than creating a new account and trying again.

Payment Issues and Security

If payment succeeded but your service hasn’t updated, use the support ticket page to describe what happened. Include the order ID, selected plan, payment method, payment result, and current panel status. You can attach a screenshot with unrelated personal details obscured. Keep the information needed to verify the issue visible, but never send your password, full subscription URL, or sensitive details that could be used to make another payment.

If the order is marked incomplete and your payment app shows no charge, first check whether payment is still awaiting confirmation. If there is a charge, check the original order before trying again. Different issues call for different evidence: a payment page that won’t open points to the browser or network, while a completed payment with no service update points to the order and its result. Describing the issue clearly can reduce follow-up questions.

After signing in to the panel on a shared or temporary device, sign out and avoid saving your password. Check that screenshots containing account details aren’t left in the downloads folder or a cloud-synced location. Client configurations on your device may also contain subscription information, so signing out of the website and removing service details from the device are separate steps. Check both.

By the end of this chapter, you should be able to find the verified order in your original account and confirm your service status. Use the same account to get your subscription next; don’t mistake the order page URL for the subscription link. If the service status is still unclear, finish checking the order before troubleshooting the client. That way, you won’t mistake an account issue for a software problem.

Get, Import, and Update Your Subscription

Your Subscription Link Is the Setup Entry Point

A subscription link lets a client retrieve the route details associated with your account. It usually isn’t the address of a single route, but an entry point for downloading configuration. The client uses it to generate a route list or configuration file in a supported format. The panel URL, plan page URL, and subscription link are different things; don’t try every web address you can open in a client.

Sign in to the account overview and check your service and data status, then use the subscription or import option actually provided on the page. Interface labels may change as features are updated, so look for actions like “Copy subscription” or “Import into client” rather than memorizing button positions. Before retrieving the details, make sure you’re in the right account so you don’t overwrite the configuration on a device with another account’s information.

If the panel offers quick import, install the appropriate client first, then start the import and check which app your browser is about to open. When the system asks you to confirm an external app, verify its name and purpose instead of allowing it automatically just because it was launched by the browser. Once the import is complete, check the client for the new configuration. A browser redirect doesn’t guarantee the client saved it successfully.

If Quick Import Fails, Check Manually

If nothing happens when you click Import, the client may not be installed, the system may not have an app associated with the import link, or the browser may have blocked the app from opening. Don’t keep clicking. Instead, copy your subscription from the panel and look in the client for an option to add a remote configuration by link. Before retrieving or saving it, check that the link is complete and has no extra spaces, line breaks, or punctuation added by a chat app.

After saving a remote configuration, make sure it’s enabled. Some clients keep multiple configurations, so successfully adding one doesn’t mean it automatically replaces the current configuration. Seeing routes in a list doesn’t mean you’re connected either. Check in this order: configuration saved, configuration selected, route selected, connection enabled. This helps keep importing and connecting as distinct steps.

If the client reports an incompatible format, first check that the import option is intended for that client and that the app supports the configuration format provided by the panel. Don’t submit your subscription link to an unknown online converter or change its parameters at random. Conversion services may expose your account details; check the import options in the panel or ask through a support ticket instead.

Updating a subscription retrieves the current route details; it doesn’t renew your plan or restore used data. You may want to update after a plan change, route list update, or long period without use. After updating, check your selected route again, as names or groups may have changed. If the app kept an old selection, you may need to select a currently available route again to get the expected result.

Troubleshoot Update Errors and Protect Your Details

If an update fails, first determine whether the client couldn’t retrieve the remote configuration or retrieved it but couldn’t parse it. For retrieval problems, check your local network, panel access, and whether the link is complete. For parsing problems, check client compatibility and the import option. Note the exact error text, but make sure it doesn’t include your full link before sharing. A clear description of the error is more useful than simply saying the subscription has expired.

If you think your link has been exposed, stop sharing it and use the reset option actually provided in the panel. If you can’t find one, ask through a support ticket. Once reset, update the configuration on all your devices. Check the panel instructions and client results to confirm when the old link stops working and whether any local cache remains. Deleting a chat message alone doesn’t resolve exposed account details.

For easier maintenance, give each configuration a recognizable local name that identifies the device or account it’s for—but don’t put a password or full link in the name. When moving to a new device, get the details from the panel again instead of forwarding an old backup containing sensitive information. After retiring an old device, check its local configuration and system connection status to remove details you no longer need.

For more on getting and updating your subscription, see the Subscription Link Guide. By the end of this chapter, you should have a current subscription ready to import. The next chapter covers clients on each platform. If you haven’t retrieved your configuration yet, verify its source and your account status before changing advanced network settings on your device.

Import the Client on Each Platform

What to Prepare and Where to Download

Get clients from the client downloads section in the panel. You can download the Android, Windows, macOS, and Linux clients after signing in; you don’t need to have purchased a plan. To retrieve and use a subscription, check your account’s service status. For iOS, follow the current plan requirements shown in the panel. This page doesn’t provide direct installer links or recommend repackaged apps from unknown sources.

Before downloading, make sure the client matches your operating system and device architecture, and read the installation instructions. Client names, button layouts, and permission prompts vary by system, so the steps below focus on what to do rather than assuming every interface is identical. After installing, keep the default settings and import your subscription from the panel. If the device already has another network tool, pause any conflicting connection first so multiple programs don’t change the system proxy or virtual network at the same time.

Windows: Check Your Configuration and System Proxy

After installing and opening the client, use quick import from the panel or add your subscription link in the app. Once it’s retrieved, select the configuration and check that the route list appears. Then choose a route and enable the connection. If the app has a system proxy toggle, enable it if your use case requires it. Simply opening the client doesn’t mean every app on your system will use the connection; check the app and proxy path as well.

If Windows asks for network permission, check which client is requesting it and why. Don’t disable all security protections to fix an installation or connection issue. If your browser works but your code editor doesn’t, check the editor’s network settings and terminal environment before importing the subscription again. If ordinary internet access fails after you close the client, check that the system proxy was restored correctly.

macOS: Distinguish Installation Approval from Connection Permission

Get a compatible client from the panel and, after installing it, make sure macOS allows it to launch. Installation security prompts and network permission for the first connection are separate steps; verify the app’s source for both. Import your subscription and enable the configuration, then choose a route and connection mode. If both the menu bar and main window show status, check the client’s actual connection and test the destination app before drawing a conclusion.

If the connection acts up after waking from sleep or switching networks, stop and restart it, then test a regular website and the destination service. Don’t immediately remove all system network settings or assume that long uptime rules out a local issue. On a work-managed device, follow your organization’s network requirements and avoid overriding existing corporate connections, certificates, or proxy policies.

iOS: Verify the System Connection After Import

Sign in to the panel and get the app from the iOS client link currently available there; check the panel for access requirements. After installing the app, return to the panel to import your subscription, then confirm in the app that the configuration was saved and selected. The first time you connect, iOS may ask to add a network configuration. Review the prompt and verify its source, then return to the client to select a route rather than stopping at the authorization success screen.

When testing, start with a regular website and then open the target app. If the app was already running, end its existing request and try again so an old connection doesn’t skew the result. Check whether the connection comes back after switching between Wi-Fi and mobile data. Don’t assume every app request is working as expected just because the system shows a connection status. And a region notice in the target app doesn’t automatically mean the client failed to install.

Android: Check Background Limits and Other Connections

Download a compatible Android client, install it using the system prompts, and import your subscription. If Android asks for connection permission, confirm that the request is from the client you just installed. If the connection is replaced or won’t start, check whether another network tool is occupying the system’s connection service. Pause tools you don’t need and try again instead of letting multiple apps compete to control the network.

If the connection works in the foreground but drops when you lock the screen or switch apps, check Android’s background, battery, and data restrictions for the client. Menu names vary by device, so follow the instructions for your system rather than applying steps meant for another model. Retest the original scenario after changing a setting to see whether it helped; don’t grant every app unrestricted permissions at once.

Linux: Check the Desktop and Terminal Separately

Get a compatible Linux client from the panel, launch it according to the current installation instructions, then import your subscription, select the configuration, and test a route. Desktop apps may inherit proxy settings differently from terminal commands, which may read proxy environment variables. Get the graphical client working first, then check each tool’s settings. A working desktop connection doesn’t mean every command-line program will use it automatically.

Before changing permissions, background services, or network controls, make sure you understand what the prompt is asking. Don’t run unknown scripts with elevated privileges. Logs can help identify configuration parsing and permission errors, but redact subscription details before sharing them. If only one development tool needs a proxy, change that tool’s settings first and keep the original values so you can restore them later.

Connection Checks and Route Troubleshooting

Verify Connectivity Step by Step

To verify a connection, keep the test conditions consistent: use the same device, network, and target app, and leave the current configuration unchanged. First make sure ordinary internet access works, then check that the client has enabled the configuration you just imported, and finally test the target service. If you change the network, region, and rules all at once, you won’t know what fixed the issue—and next time you’ll have to start over.

A client showing “Connected” only means it believes the connection is established. Actual requests can still be affected by app settings, stale connections, DNS resolution, or restrictions on the destination platform. Test the service you actually need by loading it and completing a normal action, such as signing in or submitting a request. Don’t rely only on a route icon or a single diagnostic result, and don’t assume that opening the home page proves a long-lived connection is stable.

If regular websites fail even when the client is off, first check your network, Wi-Fi signal, network authentication, and system settings. If they work with the client off but generally fail when it’s on, check the selected route, proxy mode, and configuration. If most services work but one app doesn’t, focus on that app’s proxy settings, account requirements, and service status instead of changing unrelated settings.

Choose Routes for Your Needs, Not One-Off Metrics

Choose a route based on the task, geography, and actual results. Nearby regions can be a useful starting point, but no route is guaranteed to be faster on every network. A distant region may meet a destination service’s location requirements, but it can also make the network path more complex. Start with a route that reliably gets the job done, then compare load times and connection stability. Don’t switch repeatedly because of a single momentary result.

Test streaming services and AI tools on the route you plan to use. A destination service may check your account region, access rights, and request patterns at the same time; a route in a particular region doesn’t mean all content will be available. If content is unavailable or your account shows a warning, save the exact error and distinguish a connection failure from a platform restriction before deciding whether to test another route or check your account.

For meetings, remote editing, and long-running chats, check that requests stay connected—not just that the page opens initially. Switching routes may change your exit point and interrupt an existing connection, so pause transfers and save your work before changing routes and starting the request again. Testing before an important task makes it easier to assess reliability than switching repeatedly based on how things feel mid-task.

Find the Issue with Minimal Changes

Update your subscription and check the configuration and account status first. Then test another route currently offered by the client for comparison. If switching routes fixes the issue, note the original route and what you were doing. If every route behaves the same way, continue checking the device and app. Testing on another network may help isolate a local issue, but don’t expose account details on an untrusted network or assume one successful test means every environment is fixed.

If your browser works but a development tool doesn’t, check whether the tool uses the system proxy, has its own proxy settings, or needs a restart to pick up new settings. Terminal programs may inherit outdated environment variables. Keep the browser result as a reference and change settings only for the affected app. That’s easier to control than reinstalling system-wide network components.

If you keep getting sign-in checks despite a working connection, stop switching routes repeatedly and follow the destination service’s account verification process. A change in network exit point may affect a platform’s checks, but this guide can’t guarantee that using a fixed region will eliminate them. Follow the destination service’s stated region and eligibility requirements; network settings can’t replace account authorization.

For more route-selection guidance, see the Nodes page. For development, read Choosing a Route for Long-Lived AI Coding Connections. The goal of this chapter isn’t to chase a better-looking number; it’s to get your usual apps to complete tasks reliably with a known configuration, and to have a clear troubleshooting sequence when something goes wrong.

Maintenance, Renewals, and Account Details

Check Account and Device Status Separately

Once your connection works, routine maintenance means keeping track of your account benefits, subscription details, and device environment. The panel shows your plan, orders, and data; the local client handles the current configuration and connection. Check both separately when something goes wrong. A route list still appearing locally doesn’t prove you have data left, and a healthy panel status doesn’t prove your device is using the latest configuration.

Monthly subscription data resets monthly on the activation date. Use the billing period shown in the panel rather than assuming a reset at the beginning of each calendar month. Data packages last until used and never expire, but check the remaining balance before an important task. A client may show local or cached usage; if it differs from the panel, check the reporting period and last update, then save a screenshot and ask for help rather than assuming the data was deducted incorrectly.

If usage is much higher than expected, check background syncing, autoplaying video, large downloads, and other devices that are still connected. Unlimited devices doesn’t mean their activities are unrelated. Pause unnecessary transfers and watch the panel to help identify the source. If you still can’t explain the usage, check your account security and whether your subscription was shared before assuming there’s a billing problem.

Why Subscription and Client Updates Are Different

Updating your subscription refreshes remote routes and configuration; updating the client changes the app’s compatibility and features. Neither is the same as renewing your service. Before updating the client, save any custom rules and necessary settings, and read the current instructions in the panel. After the update, test the basic connection before restoring advanced settings so you can isolate any issues caused by old settings and new behavior interacting.

If a subscription update fails, troubleshoot retrieval and parsing separately. Don’t delete all your existing details because of a temporary error. First note the current configuration name, selected route, and error message, then try retrieving the subscription again. If you need to import it again, make sure the new configuration works before removing old ones so you don’t lose the only record you can use for comparison.

When moving to a new device, get the client and subscription from the panel, then check that they work before retiring the old device. If you’re handing the old device to someone else, remove account sessions, local configurations, exported files, and screenshots containing sensitive information. Deleting a desktop shortcut doesn’t delete the app’s data; check how the system and client actually store it.

Check Product Changes Before Renewing

Before renewing, check your current service status, choose the product you want, and read the order page details. Don’t assume that early renewal, buying a different tier, or combining a data package with a monthly subscription will automatically work in a particular way. For anything not covered by the published rules, use the confirmation in the panel. If you’re still unsure, ask through a support ticket before submitting instead of paying to test how the rules work.

For a mid-cycle upgrade, the price difference is prorated into the remaining days. Confirm the exact change before submitting. Don’t override the amount shown in the panel with your own calculation or apply the price of an old order to a new one. After payment, check the order and service status to make sure the change matches your expectations. If it doesn’t, keep the original order and confirmation details so support can understand what changed.

FTVPN supports Alipay / WeChat Pay / USDT and offers a 30-day no-questions-asked refund policy. To request a refund or check a charge, read the relevant policy and contact support through a support ticket. Describe the specific order and issue; there’s no need to share account details publicly. A technical support ticket doesn’t automatically count as a refund request.

Retest After Changes to Your Environment

Travel, a new router, a system update, or installing another network tool can all change how your connection works. After any of these changes, check ordinary internet access, client status, and your usual apps before starting an important task. If you’re traveling for work, see the Business Travel Network Guide. Focus on preparing ahead and keeping your configuration recoverable; don’t change every setting at once in an unfamiliar environment.

If you need help, include changes from your maintenance note in the ticket—for example, “started after a system update,” “only happens on one network,” or “the selected route changed after a subscription update.” These details help distinguish account, route, and device issues. The goal of maintenance is to keep your setup understandable and recoverable, not to keep adding settings. Review and remove rules you no longer use.

Advanced Settings and Workflows

Understand Proxy Modes and Rule Scope First

Once your basic connection is stable, you can explore rule-based routing, app proxies, and network-level routing. Not every client supports the same features, so don’t assume the option described in this guide is available in your app. Read the client’s actual settings and documentation, confirm what each setting affects, and start with changes you can easily reverse. Advanced settings are for controlling traffic paths—not for adding more toggles or terminology.

A system proxy is generally used by apps that read the system settings, but it won’t necessarily cover every program. An app-specific proxy affects only that app or process. A virtual network interface may route more traffic, but also involves permissions, routing, and local network access. Choose based on what you actually need. If the task already works with an app-specific setting, there’s no need to route more traffic just for consistency.

Rule-based routing sends different destinations along different paths. Rule order, match scope, and the final fallback all affect the result; a broad rule can override more specific rules that follow. When troubleshooting, return to a working default configuration, then restore custom rules one at a time to see which change affects behavior. Don’t replace your account subscription with an entire configuration from an unknown source, and don’t assume a rule’s name tells you the path it actually uses.

Checking Proxies in Terminals and Development Tools

Development tools may get connection settings from the system proxy, app preferences, or environment variables; the tool determines which it uses. In Linux and macOS terminals, you can start by checking whether the current shell has common proxy variables set. These commands only read your local environment—they don’t retrieve your FTVPN subscription or establish a connection. Their output may contain internal addresses, so check and redact sensitive details before sharing.

env | grep -iE '^(http_proxy|https_proxy|all_proxy|no_proxy)='

If you find existing variables, first check whether they point to a running client and whether the address and port match what the client actually shows. This guide doesn’t specify a universal port, as settings can vary by device and app. Don’t copy a local address from another tutorial without checking, and don’t put your account subscription link in a proxy server field. A subscription link and a local listening address serve different purposes.

To temporarily clear common proxy variables in the current shell, you can use the command below. It won’t change other apps that are already running or remove settings saved in configuration files. Before running it, record the original values and make sure clearing them is appropriate for your test. To restore them, use the original tool or configuration file. Don’t permanently delete settings if you don’t know where they came from.

unset http_proxy https_proxy all_proxy no_proxy
unset HTTP_PROXY HTTPS_PROXY ALL_PROXY NO_PROXY

If some features work but others fail in Cursor, command-line AI tools, or editor extensions, check whether subprocesses and extensions are using the same settings. Processes that were already running may retain old environment variables, so restart them according to the tool’s instructions. For task-specific guidance, see the AI Tools Guide. Access to the destination platform still depends on its own account requirements.

DNS, Local Networks, and Router Limitations

DNS resolves service names to connection destinations, while proxy routing determines how requests reach them. They’re related but not the same. Changing DNS settings may affect local device discovery, corporate networks, and some app behavior. If something goes wrong, note the original settings and test with the defaults before changing anything. Don’t replace system-wide DNS, routing, and split-tunneling rules all at once to fix an issue with a single website.

Printers, local file services, and company resources may need to stay on the local network. After enabling broader network routing, test these resources separately from international apps. If a local service stops working, check whether the client has a local network option and follow your organization’s network policies. Disabling every security restriction is not a general fix.

Router configuration requires special care. FTVPN’s supported platform list is Windows / macOS / iOS / Android / Linux; that doesn’t mean every router or firmware is supported. Before setting up a gateway, verify device compatibility, configuration format, administrative access, and recovery steps. If there’s no clear compatibility information, use the client on a supported device instead.

Build a Repeatable Setup Workflow

The complete workflow is: check your service in the panel, retrieve the current subscription, enable its configuration on your device, choose a route for the task, test the app you’ll use, and keep a record of settings you can restore. For a quick refresher, return to the Getting Started Guide. To compare products, see the Plans page. For help, submit a support ticket through the panel with a reproducible description of the issue. Manage your account, configuration, and apps separately to handle everyday use and troubleshoot most issues yourself.