“系统代理” (system proxy) handles traffic only from apps that honor the OS proxy settings. TUN uses a virtual network adapter to capture traffic within its routing scope and can also handle apps that ignore those settings. If you mainly use a browser or other apps that support system proxy, start by enabling “系统代理” (system proxy). Enable TUN as needed when you also want to capture traffic from apps that ignore the OS proxy. On first use, confirm the node and basic connection work, then grant the permissions requested for TUN.
On Windows, choose setup.exe for everyday use with installation through the setup wizard. Choose portable.7z if you want to run the app from a folder after extraction without installing it, and retain the complete extracted folder. Both formats must match the processor architecture: x64 for 64-bit Intel/AMD or arm64 for Windows ARM64. On macOS, choose the x64 PKG for Intel or the arm64 PKG for Apple Silicon. On Linux, use DEB for Debian/Ubuntu, RPM for Fedora/RHEL, or the PACMAN-format .pkg.tar.zst for Arch, then match the architecture. If this site offers a corresponding verified backup, you can select it directly; for other variants, use that page’s official latest-download link.
Open “订阅管理” (Subscription Management), paste a compatible Mihomo/Clash subscription URL and choose “导入” (Import). Select the downloaded profile, choose an available node in “代理组” (Proxy Groups), and verify browsing with “规则” (Rule) mode and “系统代理” (system proxy). If no selectable profile appears, inspect the download error and URL response. Test TUN separately with the requested permission only after the basic connection works.
Distinguish URL, response-format and download-proxy errors using the failed address and port in “日志” (Logs). In “订阅管理” (Subscription Management), open the subscription card’s three-dot menu, choose “编辑信息” (Edit Information) and check “使用代理更新” (Update Using Proxy). It needs a working core and local proxy listener when enabled. If the subscription is directly reachable, disable it and retry; if a proxy is required, restore a working proxy first. Check for a stale OS proxy if errors still point to a stopped local port. If downloading succeeds but parsing fails, confirm the complete URL returns a compatible Mihomo/Clash profile, not a login or expiry page.
Keep persistent edits in “覆写” (Overrides), rather than changing only the downloaded subscription. Inspect the final rule order, group names and DNS fields, then run an update to verify persistence. If edits are missing, confirm the override applies to the active subscription and inspect script or merge errors.
Use the same node on the same network, match the clients’ test URLs and methods, and repeat the test instead of comparing one sample. Sparkle can use a global test target or a group’s test URL; different destinations are not directly comparable. Check real requests to the same site and connection records for the outbound route and response. Latency is not download speed. If actual access is also slow, compare a verified working node and use logs to distinguish node, DNS and rule failures.
Disable TUN and return to the verified system-proxy setup, checking for another running VPN. Confirm the profile loads and the node works, then inspect the first configuration, DNS or permission error in “日志” (Logs). After restoring a backup, also check the content of “覆写” (Overrides) and the selected core branch in “内核设置” (Core Settings). If you recently switched core branches, retest with the previous core and verified profile. If normal access also fails, disable system proxy and TUN, check for an OS proxy still pointing to a stopped listener, and test a normally direct site. Keep the original backup. Restore and verify one setting at a time, without changing several network parameters together.
