Choose a Global Routing mode first, then check rules, servers, and DNS. On Demand controls when to connect; Data and Diagnostics help verify what happens afterward.
This page uses the iPhone / iPad interface to explain the steps. Menu locations may differ on other platforms; follow the options shown in your app.
Global Routing
Config, Proxy, or Direct: choosing a mode
Global Routing sets how requests are handled overall. Check the selected mode first to determine whether the rules in Config apply to the current request.
Open Global Routing from Home to see options such as Config, Proxy, and Direct. This guide refers to these common modes as configuration-based routing, proxying, and direct connections, but use the English labels to find them in the app. These modes aren’t separate servers and don’t indicate connection quality. Check the selected server and global mode separately.
For everyday routing by domain or IP address, choose Config and confirm the selected configuration file on the Config screen. To temporarily check whether a particular server can handle a request, switch to Proxy. To compare with the device’s normal network behavior, briefly use Direct. When testing is complete, restore the mode you normally use; don’t leave a troubleshooting setting in place by mistake.
What the three Global Routing modes do and when to use them
Interface option
How it works
When to use it
Things to note
Config
Uses the policies specified by the current configuration’s rules.
Everyday rule-based routing for handling different destinations separately.
Check the active configuration, rule order, and policy references.
Proxy
Routes traffic through the proxy, subject to what the system and apps can actually route through it.
Temporarily check the selected server or rule behavior.
This mode does not guarantee that all traffic from every app follows the same route.
Direct
Routes traffic directly.
Compare with normal network behavior and check whether the proxy route is causing the issue.
Selecting Direct is not the same as turning off the system connection.
Config · Rule
Rule-based routing: match conditions and actions
Each rule answers two questions: which requests match, and what happens to them next.
What it is and where to configure it
Rules are usually in the rules section of the configuration selected under Config. DOMAIN matches an exact domain; DOMAIN-SUFFIX matches a domain suffix; DOMAIN-KEYWORD matches a keyword in the domain. IP-CIDR and IP-CIDR6 specify IPv4 and IPv6 address ranges. GEOIP uses an IP database to determine a location; its classifications don’t necessarily reflect where a website’s organization is based.
PROXY, DIRECT, and REJECT specify what happens to matching requests: send them to a proxy policy, connect directly, or reject them. The server used by PROXY depends on the current server selection and policy references in the configuration. USER-AGENT applies only when the relevant field is available; it can’t identify apps across all encrypted traffic.
Rule syntax example
This example illustrates the matching structure only; it is not a complete, ready-to-use configuration.
The example domain is for demonstrating syntax only and contains no server details.
How to configure rules and what to watch for
Back up your current configuration before editing rules. Put specific exceptions before broader rules, and use FINAL to handle requests that don’t match earlier entries. Rules are generally evaluated in order, so an earlier match can determine how a request is handled. If several rules apply to the same destination, check the entries higher up rather than only the one you just added.
Save your changes and confirm that the edited file is the one currently in use. For testing, reopen the destination page or start a new connection; existing connections may continue using the previous route. If a rule uses IP matching, also check DNS results, IPv6, and any related resolution options in the configuration. Don’t delete all your rules just to make one test pass—you’ll lose a useful baseline for comparison. For protocol field details, see the protocol reference.
Home · Add Server · Subscribe
Managing subscriptions and servers
This section assumes you already have your own subscription or server details. Manage server entries, subscription groups, and Config files separately.
Add and verify servers
The SERVER section on Home lets you view and select servers. To add one manually, open Add Server, choose Type, then enter the address, port, and authentication details. Shadowsocks, VMess, VLESS, Trojan, HTTP, SOCKS5, WireGuard, and Hysteria2 use different fields; don’t switch protocol types just because the address and port are the same.
After importing with Scan QR Code, open the entry and check its Type and required parameters. A QR code may contain a single server or other import data; a successful scan doesn’t guarantee that every parameter is correct. Enter passwords, certificate options, and transport settings using your existing details—don’t guess based on a connection error.
Updating and organizing subscriptions
If you already have a subscription, choose Subscribe from the add menu, enter the subscription URL, and save it before updating. A successful update only means the app retrieved and parsed the content; it doesn’t mean every listed server is currently reachable. If no entries appear, first check that the URL is complete and still valid, then check the network and the response content.
Give subscriptions from different sources clear names. Test with one group first, then organize groups and sort entries as needed. Entries created by a subscription update may be overwritten the next time it refreshes, so check where an entry comes from before making persistent edits. Before deleting duplicates, check which subscription they belong to; importing the same URL again can make troubleshooting harder.
Subscription URLs may contain access credentials. Remove the full URL, passwords, and user identifiers before sharing screenshots, logs, or configuration files. iCloud sync does not replace checking whether server details are still valid. This site does not provide, sell, or recommend servers or subscriptions; importing only handles information you already have.
On Demand
On Demand: set conditions and verify triggers
On Demand asks the system to connect or disconnect when specified network conditions are met. It controls when to connect; Global Routing controls how requests are handled after connection. Enabling On Demand won’t create routing rules or fix incorrect server settings.
Find On Demand and its rule options in Settings, then configure conditions for Wi-Fi, cellular networks, or domains based on the options actually shown. Start with one condition that’s easy to reproduce, such as an action tied to a known Wi-Fi network name. Save it, connect to that network, wait for the system to respond, then check the connection status on Home. Options can vary by system version; don’t assume an option exists just because it appears in a screenshot from another version.
When multiple conditions are enabled, check their scope and order. A broad condition may take effect before a more specific Wi-Fi condition. Domain-based triggers don’t necessarily trigger for every DNS query made by every app; caching, existing connections, and system behavior can all affect what you observe. Change one condition at a time and test with a new request.
If the connection comes back immediately after you disconnect manually, first check whether On Demand conditions are still being met instead of reinstalling the app. To pause it, check both the app settings and the On Demand status in the system VPN settings. Test after switching networks, waking the device from sleep, and restarting to confirm the behavior is as expected.
Data shows the traffic records and statistics provided by the app. Check the measurement scope, time range, and counter labels, then compare upload and download changes. These figures reflect activity according to the app’s measurement method; they shouldn’t be treated as total traffic from every app on the device or as billing figures from a server or carrier.
To check whether an action generated traffic, note the current counters, perform one clearly defined action, then return to Data and compare. If the app offers a reset option, save any records you need first. Resetting only affects the relevant statistics; it doesn’t change server status or reset usage measured by an external service.
Settings
Common settings: adjust one issue at a time
Keep a working configuration as your baseline and change one setting at a time. Menu locations below may vary; check any related settings in the configuration file too.
DNS
DNS resolves domain names to addresses and can affect rules that match IP addresses. Review the DNS servers and related options in Settings or in the current Config. Note the original values before making changes, and reconnect and send a new request afterward. Don’t combine multiple untested DNS setups at once.
If an IP address works but a domain doesn’t, DNS is one possible cause; certificate issues or a mistyped domain can look similar. Changing DNS servers won’t automatically fix every problem. Also check IPv6 results and whether local network domains need to use the resolver provided by the current network.
Test Method
Test Method determines how Connectivity Test checks a connection. Find it in Settings, choose from the options available, and set the test target before running the test from the server list. To compare servers, keep the test method, target, and network environment the same.
A test result measures a specific probe; it doesn’t measure sustained download speed or guarantee that every website will work. If a server fails the test, try connecting to the actual destination. If the test succeeds but a page won’t load, check rules, DNS, TLS, and the destination service’s response.
Today Widget
Today Widget provides status or shortcuts through system widget controls where supported. Check the relevant option in Settings, then see whether the widget can be added in the system’s widget editor. Available content and controls depend on what the current system and app support.
Widgets may take time to refresh. If the widget and the connection status on Home don’t match temporarily, open the app to check; don’t rely on the widget label alone to confirm a connection. After using a shortcut, also check the system connection status and test an actual request.
iCloud
iCloud features save or sync supported data across devices. Check the items available for syncing in Settings, along with system iCloud permissions and the Apple Account currently in use. Treat only the items explicitly listed in the interface as part of the sync scope; this doesn’t mean the entire app state is copied.
Before switching devices, back up important configurations manually and wait for syncing to finish. Editing on both devices at once can cause changes to be overwritten or conflicts to occur. Choose one device as the source for the current edits, then confirm the other has received them before continuing. App purchases and configuration sync are separate; restoring a download doesn’t guarantee that all server details have transferred.
Diagnostics
Diagnostics provides information for troubleshooting connection issues. Open the relevant option in Settings, check the logging options, reproduce the issue once, then find the related error by its timestamp. Note when it happened, the current network type, the Global Routing selection, and the exact error text to help distinguish DNS, connection, and authentication issues.
Logs may contain destination domains, server addresses, and other sensitive information. Review and remove credentials and private details before sharing logs with anyone authorized to view them. If you collect extensive logs, restore your usual settings after testing. A single log entry alone doesn’t establish the cause of an overall network issue.
Troubleshooting steps
How to verify a settings change
Keep a baseline for comparison
Note the current Config, Global Routing mode, selected server, and network type. First confirm that the device’s normal network is working, then reproduce the issue. Change only one variable per test; otherwise, even if the connection recovers, it’ll be hard to tell which setting made the difference.
From checking the mode to reviewing the result
After confirming the connection status, check the mode, whether the right configuration is selected, whether an earlier rule overrides the one you’re testing, and the server’s authentication fields. Then check DNS and Diagnostics. If behavior changes after switching modes, continue troubleshooting along the relevant route instead of resetting everything at once.
Restore your usual settings
When testing is done, restore your preferred Config, On Demand conditions, and logging options. Reconnect and test one destination expected to use PROXY and another expected to use DIRECT; check whether REJECT is matching unexpectedly if needed. For a specific error, continue troubleshooting by symptom in the FAQ.