Subscribe: import and update existing entries
Subscriptions let you import and update server entries in one place. In Add Server, choose Subscribe, enter the complete subscription URL you already have, and give it a recognizable name. After saving, check that the expected group appears and review its entries. If the list is empty, don't keep adding the same URL. Updating fetches the data returned by the subscription, so keep any essential information before making manual changes. Subscription URLs may contain credentials; when troubleshooting, describe the error without sharing the full URL or its QR code.
# Example subscription URL; cannot be used to connect
https://example.com/sub?token=xxxx
Read the Subscribe import guide →
Add Server: check fields for each protocol
Before entering settings manually, confirm the Type, then fill in fields such as Host, Port, and Password using the details you already have. Shadowsocks, VMess, VLESS, Trojan, HTTP, SOCKS5, WireGuard, and Hysteria2 use different parameter formats; changing only the protocol name does not make the rest of the settings interchangeable. For TLS, also check SNI and certificate verification options. Disabling verification should not be treated as a routine fix. After importing with Scan QR Code or the clipboard, open the entry and check that the address, port, and additional parameters are complete.
# Example Trojan share link format
trojan://[email protected]:443?sni=example.com#example
Read the Add Server field guide →
Global Routing: check the mode before reviewing Rule
In Global Routing, Config, Proxy, and Direct are the available routing modes. To route traffic using rules, select Config and confirm that the intended configuration is active. Proxy and Direct apply different overall routing choices; neither means you edited Rule. Rules are generally matched from top to bottom: put specific domain or network conditions first, then use FINAL for remaining traffic. PROXY in a rule is a policy keyword, not a server address; make sure it maps to an available selection.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT
FINAL,PROXY
Read about rule order and configuration sections →
On Demand: test first, then automate connections
On Demand starts connections when configured conditions are met. First test your server and rules with a manual connection, then check the On Demand conditions and current status in Settings. It controls when a connection starts; Rule controls how traffic is routed. These are separate settings, so check Global Routing after enabling On Demand. If the connection drops and reconnects repeatedly, check whether the On Demand conditions are still being met rather than repeatedly toggling the Home switch. Test again after changing networks to confirm the behavior matches your settings.
# The following comments describe the check order; they are not On Demand directives
# Settings → On Demand
# Home → Global Routing → Config
# Rule snippet:
FINAL,PROXY
View connection and verification steps →
Config: manage general settings and rules separately
Configuration files in Config contain general options, rules, and other sections; they are not the same as the server list in Subscribe. Keep a copy of the original file before editing, confirm which configuration is selected, and then make changes section by section. DNS options in General affect name resolution, while Rule determines the policy for matched traffic. Changing both at once makes it harder to identify the cause of a problem. To use iCloud sync, check the available in-app options and your system iCloud status, then verify the result on another device. Don't treat syncing as a separate backup that's already complete.
[General]
bypass-system = true
dns-server = system
[Rule]
FINAL,PROXY
Read the .conf file structure guide →
Diagnostics: relate test results to the problem
Connectivity Test checks whether an entry can connect. The Test Method in Settings affects what the results mean, so a single number cannot tell you whether all access is working. If something fails, check your local network first, then review server settings, DNS resolution, and rule matches; change one thing at a time. Data can help you observe traffic, but traffic activity does not prove that a request to its destination succeeded. When reporting a problem, include the error, selected mode, and test method, but remove subscription credentials, passwords, and other personal information.
# Check the matching conditions first, then the policy
DOMAIN-SUFFIX,example.com,PROXY
FINAL,PROXY
# Verify test readings and access to the destination separately
Read about tests, rule order, and troubleshooting →