Clash FAQ

Start by distinguishing the three components: clients such as Clash Verge Rev provide interfaces for importing configurations, switching proxies and viewing logs; the mihomo core handles connections, DNS and rules; and subscriptions come from service providers and typically include nodes, proxy groups and routing rules. Installing a client does not automatically give you usable nodes or establish a proxy connection. To get started, prepare a configuration that supports the core, import and select it, then enable the system proxy or configure TUN if needed.

A discontinued client does not mean your subscription stops working immediately. Whether it remains usable depends on the service and configuration format. Before moving to a client such as Clash Verge Rev, back up your custom rules and essential settings, then ask your subscription provider whether they offer a mihomo-compatible subscription. Do not overwrite the new client’s entire data directory. After importing, check the proxy group names, rule targets and listening ports. Scripts or UI settings specific to the old client may not transfer directly.

For everyday use, start with Rule mode, which routes connections according to the rules in your configuration. Global mode sends ordinary connections that have reached the core to the global policy group, where you must select an available policy. It does not enable the system proxy for apps or automatically take over your entire PC. Direct mode generally sends connections handled by the core straight to their destinations. To troubleshoot routing, you can briefly switch to Global mode for comparison, then switch back to Rule mode. Don’t treat changing modes as a universal fix for node problems.

The system proxy sets a local proxy address in Windows settings and is mainly used by apps that follow that setting. TUN mode routes traffic through a virtual network adapter, making it better suited to apps that ignore the system proxy, but it also involves service permissions, DNS and compatibility with other VPNs. For a regular browser, try the system proxy first; there’s no need to enable both modes from the start. If you need TUN, make sure its service is running, then test the target app separately. Whether to keep the system proxy enabled depends on the client’s guidance and your connection logs.

Open Windows Settings → System → About and check System type instead of relying on your PC’s brand. Most Intel and AMD processors use x64. On ARM-based devices, choose an ARM64 package if the client explicitly provides one. If the download page lists only x64, don’t substitute an ARM package intended for another platform; check Windows and client support to see whether emulation is an option. Review the system requirements before installing, since older Windows versions may not support the current client or its runtime components.

First, make sure the entire link was copied, remove any spaces at either end, and ask your provider to confirm the subscription’s expiry date, account status and current URL. Then check the client logs to distinguish a connection timeout, HTTP error or configuration parsing failure. For timeouts, check the network. A 401 or 403 usually points to authorization or access restrictions; a parsing error calls for checking the subscription format. Keep any working configuration rather than repeatedly deleting and recreating it. Subscription links may contain credentials: don’t submit them to unfamiliar converter sites or post the full link in public forums.

Open the configuration page and check that the imported configuration is selected and loaded; downloading a configuration and enabling it are separate steps. Then review the logs for YAML parsing errors, missing proxy group targets or failed proxy-providers downloads. Some configurations fetch nodes through remote providers, so a successfully loaded main configuration does not mean those providers have updated too. If the response is a webpage or account notice rather than a valid configuration, ask your provider for the correct URL. After fixing the issue, reload the configuration and check the groups on the Proxies page.

Turn off TUN, open Settings in Clash Verge Rev, find Service Mode and follow the prompts to install or repair the service. Approve the Windows permission request, then check the service status. Settings may move between versions, so use the current interface as your guide. Once the service is running, enable TUN again and check the core logs for virtual adapter or routing errors. Organization-managed PCs may block installation of these services; don’t bypass those restrictions. If the problem persists, switch back to the system proxy and note the exact error and client version for troubleshooting.

Check the active configuration and proxy group, enable the system proxy, then visit a destination that clearly requires a proxy. At the same time, open the client’s Connections page and find the connection by domain. Check the matched rule, policy group and final outbound route. A page loading successfully or a node speed test returning a result does not prove that the page used the selected node. Browser proxy extensions, separate proxy settings and existing connections can affect the result. Temporarily disable conflicting settings, close the page, visit it again and check the new connection entry.

Use the client’s persistent overrides or rule editor when available. Avoid editing a configuration file that will be overwritten at the next subscription update. mihomo generally evaluates rules in order, so put specific domain rules before broader rules that might match first, and before the catch-all MATCH rule. Policy names in the rules must match the actual proxy groups. Save and reload the configuration, create a new connection, then check the match on the Connections page. Existing connections may keep their previous policy, so refreshing the page alone won’t confirm that a change worked.

A speed test mainly measures connectivity and response time to its test endpoint; it doesn’t directly indicate video performance, download bandwidth or how every site will feel. Results vary with the test endpoint, network congestion, protocol and the destination server’s location. When choosing a node, first make sure the site you need works, then assess stability during actual use. Avoid running many speed tests and downloads at once. If a node times out in the test but works for your target site, check whether the test endpoint is blocked rather than deleting a configuration that still works.

Note the active configuration, proxy groups and listening ports. Use the client’s backup feature to save the configuration and persistent overrides; if you need to copy the data directory manually, exit the client first. Store backups somewhere secure, since they may contain subscription credentials. After updating a subscription, check custom rules and proxy group references. After upgrading the client, check the service status, system proxy and TUN. Don’t copy the entire old directory over the new version. If compatibility issues arise, restore only the settings you need, one at a time, to identify what caused the problem.

First, make sure the core is running. Then open Windows Settings → Network & Internet → Proxy and check that the local address and port match the client’s current listener. Don’t assume every client uses port 7897. Next, check whether a browser proxy extension, an app-specific proxy or another proxy tool is overriding the setting. Look for the target request on the client’s Connections page: if there’s no entry, check whether traffic is reaching the core; if there is an entry but the request fails, check the node, rules and DNS. Some apps ignore the system proxy and need separate configuration or TUN.

First, pause the proxy and check that your regular internet connection works. Then confirm that your subscription account is active, the configuration updated successfully and your device’s clock is correct. Check the error type in the logs: DNS resolution failures, refused connections and timeouts point to different causes. If permitted, try another network for comparison and temporarily disconnect other VPNs to avoid routing conflicts. Don’t disable the entire firewall. If only one node fails, try another node first. If the same subscription fails across networks, contact your provider to check service status.

First, confirm that a browser can access the internet through the local proxy. Then check whether the target app is subject to Windows app container loopback restrictions; not all Store apps use the same network model. If the client provides a UWP loopback exemption tool, open it and follow the permission prompts, selecting only the apps that need access to the local proxy. You can also run CheckNetIsolation LoopbackExempt -s in an administrator terminal to view the current list, then add an exemption using the target app’s package family name. Don’t guess the package name or exempt every app. Restart the target app afterward to verify the change.

First, check Windows Settings → Network & Internet → Proxy. If a manual proxy still points to a local port that is no longer running, turn it off and test again. If you used TUN, reopen the client, turn off TUN and the system proxy, then exit normally from the system tray to avoid leaving things in an inconsistent state by ending the process directly. If only some sites fail, check DNS and whether another VPN is still routing traffic. Don’t change organization-managed proxy settings without authorization, and don’t start by resetting the entire network, which could remove settings required for work.