Complete Shadowrocket User Guide
Follow the steps in order: getting the app, permissions, importing, routing, testing, and maintenance. Instructions use the iPhone / iPad interface; installation guidance covers all platforms.
This page is a reference guide to the conditions behind each step, how settings relate, and what to check when something fails. To make your first connection, start with the quick-start workflow in the user guide, then return to the relevant chapters for more detail. If you have already completed the initial setup, use the contents to find what you need—there’s no need to rebuild all your settings.
Before you begin, have your subscription URL or server details ready; get them from your service provider. Domains, addresses, and credentials shown in examples are fictional and cannot be used to connect. Layouts may vary by platform, so follow the labels and options shown on your device.
Getting the App
First check how to get the app for your device, then handle any system installation prompts. The iPhone / iPad version costs $2.99 as a one-time App Store purchase. The Mac / Windows / Android / Linux versions are free. Mac downloads are available for Apple Silicon and Intel; get installers for other computers and Android from the all-platform downloads page. Download links are under /dl/shadowrocket/ on this site. Packages for different processors are not interchangeable.
iPhone / iPad: Check the App Store listing
Open the App Store product page linked from the downloads page. Check that the developer is Shadow Launch Technology Limited, the app ID is 932747118, and the icon matches the official artwork. Check the system requirements shown on the App Store page before purchasing. The listing may not appear in the mainland China storefront; check the region associated with your Apple ID. Changing regions may be subject to conditions involving your balance and active subscriptions, so follow the instructions in your account settings. If the listing does not appear in search, that alone does not mean there is a problem with your device.
Keep access to the account used for the purchase. When you switch devices or reinstall, use that account to find the app in your purchased items rather than relying on a fresh name search. To redownload on an iPhone or iPad using the same account, see Using Shadowrocket on iPad and finding purchased apps to confirm that the accounts match. Family Sharing eligibility depends on what the storefront shows; don’t assume other accounts have the same access.
Desktop and Android: Check the architecture before opening
On Mac, check About This Mac to identify the chip: choose the Apple Silicon package for an Apple chip, or the Intel package for an Intel processor. Move the app to Applications before opening it. On Windows, use the installer listed on the downloads page. On Android, choose a file that matches the architecture listed there. On Linux, select the package format used by your distribution: deb, rpm, or AppImage. Similar file extensions do not mean packages are interchangeable. If the app will not start, check the architecture and package format before changing network settings.
Desktop and Android installers are not code-signed, so the system may block the first launch. Before allowing the app to open, confirm that the file came from this site’s downloads page and that its name matches the platform you selected. Stop if the source is unclear, the download was interrupted, or the system explicitly warns of a risk. The system paths below may vary slightly by language and version. Only change the settings for a Shadowrocket file whose source you have verified; there is no need to disable system-wide security protections.
| System | Installation or allow-open location |
|---|---|
| macOS | If you see “cannot verify the developer,” go to System Settings → Privacy & Security, find the record of the block, then select “Open Anyway.” |
| Windows | When SmartScreen appears, confirm the source first, then select “More info → Run anyway.” If your organization’s policy blocks the app, contact your device administrator. |
| Android | Enable “Allow from this source” only for the browser or file manager you’re using to open the installer. You can turn off this permission afterward. |
| Linux | Install deb / rpm packages with the corresponding package manager. For an AppImage, allow it to run as a program in the file properties, or run chmod +x on the file. |
If Mac says the app is “damaged,” delete any incompletely downloaded file and download it again from the downloads page. Only after confirming the app is intact, in the location shown below, and from a trusted source should you consider using Terminal to remove the quarantine attribute. This will not repair a genuinely damaged file or verify its source. If the path differs, confirm the actual location first; do not apply the command recursively to an entire directory.
xattr -cr /Applications/Shadowrocket.app
First Launch and Permissions
When you first open the app, start by learning what Home, Config, Data, and Settings do. Home is where you select a server and Global Routing mode and control the connection. Config manages configurations used for routing. Data shows traffic and connection details. Settings groups tests, connection options, and other behavior controls. Navigation may differ across devices; find controls by their page names rather than fixed screen coordinates. Not having a server yet or not having granted permission does not mean installation failed.
What does the system VPN configuration do?
The first time you connect, the system may ask to let Shadowrocket add a VPN configuration. This permission lets the app create a system network tunnel; it does not add a subscription or fill in a server address, password, or protocol settings. Confirm the prompt comes from the Shadowrocket app you are using, then approve it with your device passcode or biometric authentication as requested. You still need to select a valid server. Permission alone cannot make a connection work without the correct settings.
A system VPN configuration and an in-app Config file are different things. The former is a network connection managed by the system; the latter stores rules and settings used by the app. Removing the system entry may prompt you to grant permission again next time. Deleting a Config may change routing behavior. When troubleshooting, identify which layer you need to change. Don’t clear all system VPN entries to edit one rule, or treat an in-app subscription update as a fix for system permissions.
If you tapped Deny by mistake, return to Home and try starting the connection again to see whether the authorization prompt reappears. If needed, check existing entries in the VPN section of system settings. If your device is managed by a school or employer, a configuration profile may prevent adding a VPN; check the applicable policy rather than repeatedly reinstalling the app. For more about the system prompt and VPN entries, see Understanding the Add VPN Configuration prompt.
Grant other permissions only when needed
When you use Scan QR Code, camera access lets the app read the code. If you denied permission, you can allow it later in the app permissions in system settings, or import using an existing share link instead. Clipboard prompts relate to paste actions; first confirm that the clipboard contains information you intend to import. For requests involving photos, files, or the local network, consider what you are doing at the time. You don’t need to grant every permission in advance just to “complete setup,” and denying an optional permission does not mean the server is unavailable.
QR codes and clipboard contents may include passwords, user IDs, or full subscription URLs. After scanning, check the item type, address, and port before saving; recognized text is not proof of a trustworthy source. Photos, screenshots, and screen sharing can also expose credentials, so hide them before asking for help. To preserve an error, record its text and the steps that led to it rather than sharing the entire server editor.
Check for other connections and automatic triggers first
Before establishing a baseline connection, check whether another VPN is active on the system and whether On Demand might reconnect automatically. Usually, stop other related connections so the test applies to this configuration alone. If the switch turns off and then back on, check automatic connection settings and system status before assuming the app cannot disconnect. A system status icon indicates tunnel status; by itself, it does not prove the remote server or destination website is reachable.
For the first baseline test, use a stable Wi-Fi connection. Don’t switch to cellular, enable extra automation, or change DNS at the same time. Note the selected server, Global Routing mode, and configuration name, then change only one condition per test. This makes it easier to tell whether a result came from restored permissions, a network change, or a parameter change. If you enable several features at once, it can be difficult to identify what caused a problem.
Adding Servers and Subscriptions
Identify what kind of information you have before choosing an import method. A single share link usually describes one server; a subscription URL retrieves a list of servers that can be updated; a configuration file may also include rules, DNS settings, and other options. These aren’t interchangeable just because they’re all links. Get the information from your service provider. If you only have an instruction image, first check whether it shows a subscription entry point or individual server settings; don’t paste a webpage URL into a server address field.
Add Server: Check what each field means
When you select Add Server on Home, choose the protocol specified by your information, then enter the address, port, and matching authentication details. The address field usually should not include a webpage path, and the port must match the server. The display name is for identifying the entry locally; changing it does not change where it connects. After pasting, check for leading or trailing spaces and line breaks. Don’t include Chinese punctuation, explanatory text, or a colon before the port in a field that does not call for it.
Fields called “password” are not used the same way by every protocol. Shadowsocks requires the correct encryption method and password; VMess and VLESS often use a user ID; Trojan uses its authentication information, with TLS settings to consider. WireGuard uses keys and peer settings, not a regular password. Don’t switch protocols at random to troubleshoot. Compare every field with the complete settings from your service provider. If a parameter is missing, check the original information rather than guessing a common value.
| Parameter group | What to check | Common mix-up |
|---|---|---|
| Address / port | The destination and listening port must match the server. | Using a subscription URL as the server address. |
| Authentication | The password, user ID, or key must match the protocol. | Pasting it into the notes field and leaving the authentication field empty. |
| TLS / SNI | Confirm the activation conditions and server name against the supplied details. | Changing the name used for certificate validation to the connection IP at random. |
| Transport settings | Keep the type, Host, path, and related settings consistent as a set. | Copying the path but omitting its corresponding transport type. |
Subscribe: Check the update result after importing
To add a subscription, paste the full URL in the relevant Subscribe or subscription-type entry in the app, then enter a name that makes it easy to recognize. Save it, update once, and check that the expected server list appears. A successful update does not mean every listed server can connect; it only means the data was retrieved and parsed. If the update succeeds but shows no entries, check the response, filters, and service status rather than immediately clearing the existing list.
The example below shows the structure of a subscription URL, not a working service. Parameters after the question mark may contain access credentials; losing part of the URL when copying it can cause authentication to fail. Don’t post a complete URL in a public help request. The example domain is for illustration only and is not an external access point.
https://example.com/sub?token=xxxx
If a subscription update fails, first check whether your current network can reach the URL, whether the original source has changed its address or shows an expiration notice, and whether a messaging app truncated the copied text. A login page, verification page, or error message is not a server list and cannot be imported as one. Keep the last working subscription entries until you can retrieve the new list; repeated refreshes won’t fix expired credentials.
Manage share links, QR codes, and configuration files separately
Share links such as ss://, vmess://, vless://, and trojan:// usually contain information for a single server. Import them through an entry supported by the app or scan them with Scan QR Code. After importing, open the entry and check its fields, especially if the link was forwarded as text. For more, see Share links and subscription links explained. Don’t judge whether a link is complete by its length alone.
Importing a configuration in Config requires a separate check for remote rules, rewrites, and other settings. Save a copy of the current configuration before importing, then check which one is active. A new file appearing in the list does not mean it is in use. Subscription entries may be overwritten during updates, so check how they are maintained before editing an individual server. For personal changes you need to keep, use a separately managed copy and record its source.
Global Routing and Rules
Global Routing determines how connections are handled overall. For everyday rule-based routing, choose Config mode. To compare a server path temporarily, use Proxy mode. To establish a direct-connection baseline, use Direct mode. These are explanations of what the modes do; the interface labels remain Config, Proxy, and Direct. The mode and selected server are separate choices: changing servers does not prove that a rule matched, and selecting Config does not guarantee that the configuration behaves as expected.
| Mode | Typical use | What to check |
|---|---|---|
| Config | Let the current configuration determine where connections go. | The active configuration file, rule order, and final policy. |
| Proxy | Route intercepted connections through the proxy for comparison. | The selected server and remote reachability; traffic excluded from interception is not covered by this test. |
| Direct | Route intercepted connections directly for comparison. | Whether the current network can reach the destination. |
Config depends on selecting the right configuration file
In Config, first confirm which file is selected, then review its rules. With several imported files, similar names can make it seem as though “changes had no effect.” Save a copy before editing. After making changes, save and confirm that the same file is still active. If needed, disconnect and reconnect so new connections use the updated settings. Existing connections may continue along their previous path, so don’t rely on a page that has been open for a while to check whether a change took effect.
Rules are generally checked in order, and the first matching rule determines the policy. Put a narrow exception before the broader rule that would otherwise cover it; place the fallback rule last. An exact-domain rule after a suffix rule that already matches that domain usually won’t override it. Rules don’t vote on a result, and later rules don’t automatically have higher priority. To troubleshoot, scan from the top and find the first rule that could match.
Understand the condition before the policy
DOMAIN matches an exact domain, DOMAIN-SUFFIX matches a domain suffix, and DOMAIN-KEYWORD matches a keyword in the domain. Keyword conditions can cover a broad range, so don’t add them in bulk without understanding their impact. IP-CIDR and IP-CIDR6 match address ranges, while GEOIP relies on geographic data. Domain and address matching operate at different levels; the destination name alone doesn’t tell you which rule will match.
[General]
bypass-system = true
dns-server = system
[Rule]
DOMAIN,example.com,PROXY
DOMAIN-SUFFIX,example.org,PROXY
DOMAIN-KEYWORD,example,DIRECT
IP-CIDR,192.168.0.0/16,DIRECT
IP-CIDR6,fc00::/7,DIRECT
GEOIP,CN,DIRECT
FINAL,PROXY
This snippet is for understanding the syntax, not a general-purpose replacement for your existing configuration. In a rule, PROXY and DIRECT specify policies, while REJECT means to reject; none of them is a server address. FINAL,PROXY catches connections that were not matched by earlier rules. Changing it to FINAL,DIRECT changes where that traffic goes. Don’t copy only the last line without understanding the fallback behavior.
Use comparisons to narrow down the problem
If a destination works in Proxy but not in Config, check the configuration and matching policy before changing servers. Conversely, if it works in Direct but not in Proxy, investigate the proxy path first; a single result still doesn’t prove there is an authentication or server-side problem. Test the same destination on the same network using a new connection. Keep other variables unchanged so the comparison is meaningful.
DNS translates domain names into addresses, so the actual behavior of some address rules also depends on resolution results. If you can’t reach a local network device, check private address ranges, local network names, and current routing rather than switching all traffic to Direct. Conditions such as USER-AGENT have limited applicability; don’t assume they can read request information from every encrypted connection. For domain-based routing, first check whether an existing domain condition can match.
Connections and Testing
Test connections at three levels: whether the system tunnel is established, whether the server path works, and whether the destination request follows the expected rule. Check all three; success at one level does not prove the others work. Before you begin, confirm the current server, Global Routing mode, and Config file on Home, and stop unrelated tests. For initial troubleshooting, choose one server with complete details, stay on the same network, and avoid switching between several entries during a test.
Check system status after starting the connection
Turn on the connection switch on Home, approve any system prompt, and wait for the status to change. If it disconnects immediately, note the exact message and check permissions, server fields, and configuration parsing errors; toggling repeatedly usually just repeats the same error. If the switch stays on but pages won’t load, continue checking the network path rather than repeatedly deleting the system VPN configuration. If the connection restarts after you stop it, check On Demand and other automatic connection conditions.
A system status icon means the device has a corresponding network tunnel; it does not confirm that a subscription is current, remote authentication works, or destinations are accessible. Some requests may also bypass the connection you are checking. To test, actively make a new request and note when you do it, then look for a record from the same period in Data. Refreshing an old page is not a reliable new test; caching, existing connections, or background requests can affect the result.
Test with Connectivity Test and real-world access separately
Use Connectivity Test on Home, and first check which test method is selected. Methods test different things: some focus on establishing a connection, while others also make application-level requests. Results from different methods are not directly comparable and do not guarantee that every website will load. If a test fails, compare it with access to a real destination. Don’t judge availability solely by the order of entries in a list, or treat test results as a service-quality guarantee.
Next, open a page you can normally access as a baseline, then visit the destination that is causing trouble. Try to make both tests use new connections. Check whether all requests fail or only a particular domain, login flow, image, or video resource. A single page may rely on several domains, and a loaded main page does not mean all its related requests use the same policy. Recording the specific resource that failed is more useful than saying “the network isn’t working.”
Choose a troubleshooting path based on what you see
| Symptom | Check first | Next comparison |
|---|---|---|
| Disconnects as soon as it starts | System permission, configuration errors, and server fields. | Restore a known-good configuration and record the new prompt. |
| Connection stays on, but nothing loads | Current server, basic network access, authentication, and DNS. | Test basic access after disconnecting, then compare with another existing server. |
| Proxy works, but Config does not | Current configuration, matching rules, and final policy. | Check the actual policy applied to the destination connection. |
| Only one website has a problem | Related domains, website status, login, and region restrictions. | Make a new request on the same network and check other pages on the site. |
| Problems start after switching networks | Wi-Fi sign-in page, cellular permission, and network reconnection. | On a stable network, disconnect and reconnect before testing again. |
For a domain resolution error, first check whether all domains fail or only one. Then review DNS settings in the configuration and on the current network. Don’t replace a domain in the address bar with an IP address as a permanent fix: TLS certificate checks, server names, and website virtual hosting may depend on the domain. Directly opening an IP is not equivalent to the original request. If results may be cached, check that your next test actually triggers a fresh lookup.
If only cellular data fails, check that the system allows the app to use cellular data and look for data restrictions or network access problems. Public Wi-Fi may require you to complete a web sign-in first. Switching networks can invalidate existing connections, so a brief interruption does not necessarily mean a setting is wrong. Return to a stable network, reconnect, and repeat the same test against the same destination instead of mixing results from two networks.
Keep a reproducible troubleshooting record
A useful record includes the device OS, network type, action taken, current mode, configuration name, and exact error text. You can use your own shorthand for server names; there is no need to share addresses, passwords, subscription links, or keys. “This destination works in Proxy but not Config” is more useful than several screenshots without context. If you have run comparisons, note which single condition changed each time.
Data: Traffic and Connection Records
Data helps explain network activity that has already happened; it is not a subscription billing page. First check what the current view tracks, its time range, and whether it has accumulated data since the last reset. Then review uploads, downloads, or connection records. App traffic figures may differ from those calculated by your service provider because the measurement points, billing periods, and counting rules may differ. A mismatch alone does not mean either side is wrong.
Distinguish device activity, app statistics, and server-side measurements
A device may sync photos, receive notifications, refresh content, or maintain app sessions in the background, so traffic can appear even when you haven’t opened a webpage. Interpret changes in Data in context with their timestamps and connection records; don’t assume that a server entry is “downloading by itself.” To inspect one action, pause obvious background tasks, close unrelated pages, and perform one clearly defined action within a short time window.
Interpret upload and download directions relative to the current measurement. Web requests usually involve a small amount of upload and more download, but video calls, cloud sync, and file uploads can work quite differently. Encryption, protocol overhead, retransmissions, and network activity outside the tunnel can all cause byte counts to differ between measurement layers. If your service provider bills on its own schedule, follow its measurement details; the app’s display does not replace account records.
Subscription entries can also include information that is separate from live traffic statistics on your device. Some subscriptions return account traffic or expiration text. That information comes from the subscription response; it is not an independent check of your server-side balance by Shadowrocket. A text change after updating the subscription does not mean your device has just used that amount of data. Check the source first, then decide whether to update the subscription, view Data, or check your provider account.
Match requests to rules and policies
When troubleshooting a website, note when you start accessing it, then look in Data for a corresponding domain or address record. If the current view supports search or filters, narrow the results to relevant entries. If no record appears, first confirm that you made a new request, the connection is still running, and the app isn’t serving cached content. No new connection by itself does not prove that a rule is wrong; the page may not have generated new network activity.
When you find a record, compare the destination, matching rule, and actual policy. If you expected PROXY but see DIRECT, go back to Config and check earlier rules from the top down. If you expected a domain match but see only an address, consider the resolution process and how records are displayed. Don’t add an address-range rule just because you see one IP; a broad range may serve many unrelated domains and affect more than the current issue.
A single page often makes several connections; login, images, APIs, and media may use different domains. If the main page loads but content is blank, look for the failing requests rather than adding the main domain rule repeatedly. For apps that maintain or reuse connections, you may need to close the relevant page or app after changing a rule before testing again. That lets you observe behavior under the new settings rather than an existing session.
Use a short observation window instead of relying on long-term estimates
To investigate an unexpected increase, first note the current statistics range, then perform one clearly described action, such as refreshing a page or uploading a known file. Compare the figures before and after, and check connections from the same period. Test one type of activity at a time; don’t combine a system update, photo sync, and webpage test in one window. If you reset local statistics, save any summary you need first. A reset gives you a fresh baseline; it does not restore your service provider’s data allowance.
Failed connections can still use data because connection attempts, authentication, and retries require network traffic. Conversely, increased traffic does not mean the destination content loaded completely. Check actual access as described in the previous chapter; Data provides clues for interpreting what happened. For battery issues, also check system battery usage and background activity. Low traffic does not mean the wireless radio woke less often, and high traffic alone does not indicate a configuration fault.
Common Settings and Their Limits
Use Settings to make deliberate, individual changes to a connection that already works—not to try every switch at once. Before opening Settings, define the problem: do you want automatic reconnection, a different test method, or help with a resolution issue? Change only the setting directly related to your goal, note its original value, and test again. Available options may differ by platform and app version. If an option is missing, check the interface you are using instead of copying a path from another device.
On Demand: Let conditions trigger connections
On Demand triggers a connection when specified conditions are met. Its behavior depends on whether it is enabled and which conditions apply; it does not mean that traffic occurs only when you open a particular webpage. Before enabling it, make sure a manual connection works, then review the available in-app conditions and system behavior. If you want the connection to stay off after stopping it manually, first check whether automatic triggers are still enabled. A network change or matching request may start it again.
To test automatic connections, start on one stable network, then switch between Wi-Fi and cellular as planned, checking system connection status at each step. Don’t quickly cycle through locking the screen, switching networks, and toggling the connection; those actions can combine several trigger conditions. If automatic connections aren’t needed for now, disable the related settings and check whether manual control works as expected. This is easier to undo than deleting all your configurations.
There is no single battery setting that works for everyone. Background request frequency, signal strength, connection retries, and activity from other apps all affect battery use. Check foreground and background activity in the system battery view for the same period, then consider how you use the device. On Demand being enabled or disabled alone does not explain the result. For more, see Troubleshooting On Demand and background battery use.
DNS: Identify where settings come from and how to test them
DNS options may come from the current Config, interact with app-wide settings, or both. Before changing anything, check relevant configuration sections such as [General] to identify which layer you are modifying. If the same option appears in multiple places, find out which one takes precedence; avoid leaving conflicting settings without a record of them. The example dns-server = system means to use system DNS settings; it is not necessarily right for every network.
If resolution fails, first check that the network is connected, then determine whether the issue affects one domain or many. Before trying another resolver, note the original setting and retest the same destination. Changing DNS won’t fix a wrong password, an expired server, or mismatched transport settings. Be especially careful with corporate and local network names: changing the resolution path at random may prevent access to internal services that worked before.
Caching can also affect test results. After changing DNS settings, existing connections or cached resolutions may make the first test look unchanged. Start a new connection and check the records to confirm. Don’t delete all app data just to force an “immediate refresh.” First use the relevant options in the current interface, and consider separately what clearing DNS cache, stopping a connection, and deleting a configuration will affect.
Tests, Background Behavior, and Diagnostics
Keep the Connectivity Test method and destination consistent between tests. Results mean something different if you change methods, so don’t compare their values directly. If you set a custom destination, make sure it is reliable and appropriate for the test. Testing is a troubleshooting tool; more frequent background checks are not always better. Running many tests can generate extra requests and make real application traffic harder to identify.
Enable logs or diagnostic options only when needed, at an appropriate level of detail, and return to everyday settings as soon as you have reproduced the problem. Detailed records may include addresses, paths, or authentication-related information, so inspect them before exporting. System cellular permissions, Low Power Mode, notifications, and background management may also affect the experience, but they may not be in Settings. Distinguish app settings from system settings so you don’t keep looking in the wrong place.
Routine Maintenance and Recovery
Routine maintenance should keep configuration sources traceable, changes reversible, and problems reproducible—not involve changing every setting frequently. Keep a known-good configuration and a brief record of essential actions; this is usually more useful than accumulating several files with the same name. Before tidying up, confirm which server, subscription group, and Config are in use so you don’t delete information you still need. Treat backups containing authentication details as sensitive.
Back up three kinds of information separately
The first is server and subscription information, the second is rule configurations, and the third is personal settings and diagnostic records. They may be saved through different parts of the app; exporting a Config may not include all servers and credentials. After backing up, check what the file actually contains and note how to restore it. Don’t wait until the old device has been erased to discover that you saved only a filename or a screenshot without the full address.
Backups may contain passwords, keys, user IDs, and subscription URLs with credentials. Keep them somewhere protected that you control. Before transferring them through the cloud or between devices, confirm the account and receiving device; never upload the original file in a public discussion. If credentials are exposed, ask your service provider how to replace or revoke them, then update the entries on your device. Deleting a shared image does not guarantee that the credentials are no longer valid.
Verify subscription and configuration updates separately
Before updating a subscription, make sure you still have a way to recover. After the update, check entry names, changes in the number of entries, and whether your currently selected entry is still present. If names have changed, familiar entries may be harder to recognize; don’t assume settings are the same based on the name alone. If everything behaves differently after an update, compare the original information and error messages, and keep the old record for reference. Repeatedly deleting and rebuilding entries can erase useful differences between attempts.
A remote Config update may overwrite local rule changes, so record manually maintained exceptions separately before updating. Afterward, recheck the active file, rule order, and FINAL policy, then test a few consistent destinations. A successful subscription update does not prove the configuration updated successfully; check the two results separately. Similarly, one working server does not prove that the whole list works. You don’t need to test every entry frequently just to “check them all.”
App Updates and Moving to a New Device
Manage iPhone / iPad app updates through the App Store. For Mac, Windows, Android, and Linux, get the appropriate installer again from this site’s downloads page. Before updating, stop the connection and save any configuration you need. Follow the system prompts described in Chapter 1 when installing. Don’t uninstall before confirming what your backup contains; some systems delete local data when an app is removed, so don’t assume it will be restored automatically after reinstalling.
When moving to a new device, install the app first, confirm system permissions, import servers and configurations, and restore personal options such as automatic connections last. This order lets you verify each stage separately. Don’t copy every setting from the old device before testing anything on the new one: network conditions, system permissions, and background controls may have changed. First establish a working manual connection, then restore additional behavior one setting at a time.
Recover from problems in small steps
Check the basic network first, then permissions, server fields, Global Routing, and the current Config. Next, compare against a known-good server or configuration. Only then consider reimporting or reinstalling. Keep the exact error text and result from each step so “I’ve tried a lot of things” still leaves useful information to compare. Remove a system VPN entry only when you know that specific record needs to be rebuilt; clearing all configurations should not be the first response to an ordinary access problem.
If a problem began after an update, first identify what was updated: the app, subscription, configuration, or device system. Then check the corresponding change. If only one destination is affected, use Chapter 5 to inspect its actual requests. If only automatic background connections are affected, see Chapter 7 for trigger conditions. Following the chapter for the relevant layer is more efficient than repeating every step and reduces the chance of introducing new variables.
When asking for help, prepare the device system, network type, steps taken, current mode, error message, and comparisons you have already tried. Remove all credentials before describing the issue. Check the FAQ for common symptoms and the glossary for interface terms. To repeat the shortest connection workflow, return to the user guide; there is no need to enable every advanced option in this complete manual.