Clash Verge Rev
FAQ and
Troubleshooting

Clash Verge Rev is a desktop graphical client built on the mihomo core. It reads subscriptions or local configurations and routes connections according to rules through direct, proxy, or reject policies. The client does not provide proxy nodes itself, so you need a valid subscription or usable Clash configuration file before getting started.

Rule mode is usually the best choice for everyday use: traffic is matched against the rules in the configuration file from top to bottom. Global mode sends most connections through the current global policy and is useful for temporarily checking whether rules are causing a problem. Direct mode bypasses the proxy, which helps when pausing proxy use or checking the local network.

mihomo is the core program responsible for protocol connections, DNS, rule matching, and TUN forwarding. Clash Verge Rev provides the interface for configuration management, policy selection, log viewing, and system integration. When troubleshooting, distinguish interface settings, configuration content, and core behavior, since issues in all three can look similar.

A subscription is usually a remote configuration source that can provide updated nodes, proxy groups, and rules. The configuration file is the YAML content actually loaded by the client. A proxy group organizes multiple nodes or other policies into a selectable outbound, such as URL-test, fallback, direct, or reject.

The iOS and desktop clients have different interfaces and system permissions, but they can usually import the same subscription. Full support for a configuration depends on the client core, protocol type, scripting capabilities, and rule format. If an import fails, first check whether the subscription provider explicitly supports the iOS client you are using.

Rules are normally checked from top to bottom, and matching stops after a connection hits a rule. More specific domains, processes, or rule sets should come before broader rules, with the catch-all rule at the end. After making changes, check the matched rule and final policy in the connection log instead of judging only by whether a webpage opens.

A latency test only shows whether the test target was reachable at that moment and how long the round trip took. It does not fully represent download speed, stability, or the availability of the target website. Choose nodes based on sustained access, protocol compatibility, and proxy-group test results; a single timeout does not mean a node is permanently unavailable.

Whether the selection is preserved depends on the proxy-group name, node name, and the client's cache. If an update removes a node, renames a proxy group, or changes the configuration structure, the previous selection may become invalid and fall back to the default. For long-term custom rules, use override or merge features rather than editing a local copy of the remote configuration directly.

fake-ip generally provides more complete domain mapping and rule matching, making it suitable for typical desktop use. Some programs that rely on real addresses, LAN discovery, or unusual network environments may need additional exclusions. redir-host follows a more traditional resolution flow. Before switching, keep a copy of the original configuration and check both nameserver and rule settings.

Allow LAN connections in the client, make sure the bind address is not limited to localhost, and allow the relevant port through the firewall. On other devices, enter the LAN address of the computer running Clash Verge Rev and the proxy port. Enable this only on a trusted LAN, and avoid exposing the listening port to the public internet.