Specific rules first, FINAL last
- First check whether the destination matches a specific domain rule.
- Then check whether its address falls within a defined network range.
- If neither matches, use the FINAL policy at the end.
Rule routing lets you apply different policies to different destinations. Requests follow the rules in the active configuration only when Config is selected under Global Routing on Home. DOMAIN-SUFFIX matches domain suffixes, IP-CIDR matches address ranges, and PROXY, DIRECT and REJECT mean proxy, direct connection and reject. Rules are generally evaluated from top to bottom: put more specific conditions first and FINAL at the end as a fallback. After editing, retest the same destination to avoid mistaking an unreachable server for a rule failure.
Read about rule types and priority →
Check On Demand separately from manual connections
SettingsOn DemandHome
Settings → On Demand
Home → Global Routing
On Demand triggers a VPN connection based on configured conditions. Set it up after you have verified a manual connection. First check the available On Demand options in Settings and identify which network conditions should trigger a connection, then return to Home and observe the connection status. It does not replace server parameters or fix an expired subscription. When troubleshooting repeated connections or unexpected reconnections, note the current conditions, temporarily disable automatic triggers, and test the manual switch. Verify each change on the intended network, changing one condition at a time.
See the connection verification steps →
Match Type to the server configuration
ShadowsocksVMessVLESSTrojanHysteria2WireGuard
Add Server → Type
Host / Port / Password
Support for multiple protocols allows connections to different types of existing servers; it does not mean their parameters are interchangeable. In Add Server, select Type first, then enter the details provided by your service provider. Check Host, Port, authentication details, transport and TLS options together. Fields for protocols such as VLESS and VMess differ; do not change only Type while reusing old values. If the connection fails after import, compare the entry with the original details, paying particular attention to spaces, ports and server names, then check the routing rules.
See how to use Add Server →
Handle existing subscriptions and individual servers separately
SubscribeAdd ServerScan QR Code
Subscription details: get them from your service provider
Individual server: check Type first, then enter the fields
Subscriptions help maintain existing server entries in one place; get the link from your service provider. Confirm whether it is a server subscription or a rule configuration URL, then use the corresponding Subscribe or import option to avoid mixing the two. Add an individual server with Add Server, Scan QR Code or clipboard import. When finished, check that the group and entries appear, then run a connection test. If an update fails, first verify the address and your current network. Subscription links may contain credentials; do not include them in public screenshots or diagnostic notes.
Compare the four import options →
Read each section; do not replace the whole file blindly
[General]
dns-server = system
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
FINAL,DIRECT
Configuration files control DNS, rules, Host and URL Rewrite, while server lists serve a different purpose. In Config, check which file is active and keep a copy of the original before reviewing settings section by section. General contains common options; Rule contains matching conditions and policies. Changing one section does not automatically update the others. When using iCloud sync, also check which file and entries are actually selected on the current device; sync completion alone does not confirm they are enabled. Change one type of setting at a time, save, return to Home to check Global Routing, then retest the destination.
Read about configuration file structure →
Use test results to narrow down issues, not replace real-world checks
Connectivity TestDataDiagnostics
Server parameters → Connectivity Test
Connection status → destination request → rules and DNS
Connectivity Test can help check a server's test response, but one successful result does not guarantee access to every destination. Note the test method and network, then verify with a real request. Traffic changes in Data can help confirm whether data is being transferred; Diagnostics in Settings can help investigate further. If only certain domains fail, check rule matches and DNS. If all destinations fail, start with the server and authorization status. Before sharing logs, remove subscription URLs, authentication fields and other personal information; keep only the steps that reproduce the issue.
Troubleshoot connection issues step by step →