Clash Verge Rev Help · Install / Profiles / TUN / Troubleshooting
Find answers for Clash Verge Rev installation, Profile loading, Mihomo configuration, system proxy, TUN mode, architecture selection, port conflicts, startup issues and desktop troubleshooting.
Common issues
Start with the client build, active Profile, system proxy or TUN state, then check Mihomo configuration, ports, DNS and upstream connectivity.
Installation only provides the desktop client and Mihomo runtime. You still need a valid Profile or local configuration and must enable System Proxy or TUN for traffic to enter Mihomo.
Check whether the remote source returns valid content, whether the Profile actually refreshed, and whether Merge or Script changes cause the final Mihomo configuration to load differently.
Use System Proxy for applications that follow operating system proxy settings. Use TUN when you need broader traffic capture for apps that ignore those settings.
Separate installation, Profile loading, traffic control and troubleshooting so GUI, Mihomo and upstream issues do not get mixed together.
Downloads and installation
Confirm the operating system, CPU architecture and package type first, then investigate permissions, runtime dependencies and upgrade issues.
Use x64 on most Intel or AMD Windows PCs. Choose ARM64 only for Windows on ARM devices.
Choose Apple Silicon / aarch64 on M-series Macs and x64 on Intel Macs. About This Mac shows the chip or processor type.
Check architecture mismatch, system security blocking, runtime dependencies, damaged downloads and application logs before changing your Profile or network settings.
Use DEB on Debian or Ubuntu-family distributions and RPM on Fedora or RHEL-family systems, then match the package to your CPU architecture.
An upgrade can change application files, migration logic or configuration handling. Keep a backup and verify that the intended Profile and settings are still loaded after updating.
No. Clash Verge Rev publishes desktop releases for Windows, macOS and Linux. Mobile clients that support Clash or Mihomo formats are separate projects.
Profiles and configuration
Clash Verge Rev can work with remote Profiles and local configuration files, while Merge and Script may change the final configuration Mihomo actually loads.
A Profile is the configuration source managed by Clash Verge Rev. It can come from a remote subscription or a local YAML file, and the client may transform it before Mihomo loads the final config.
Verify that the remote source returns valid content, the Profile refreshed successfully, and the final Mihomo configuration is not being changed or invalidated by Merge, Script or unsupported fields.
The active Profile may not have switched, the remote content may be unchanged, or local overrides may still affect the final config. Check the Profile timestamp and effective Mihomo configuration.
Check indentation, list structure, field names and value types, then use the Mihomo error output or Clash Verge Rev syntax hints to locate the exact failing field.
Confirm the remote URL is reachable and returns valid data, then inspect the client update error or network logs before assuming the parser itself is the problem.
Different clients may bundle different Mihomo versions, apply different defaults or modify the configuration before runtime, so compare the effective config and core version rather than only the source YAML.
System Proxy and TUN
System Proxy and TUN are different traffic-capture paths. Whether TUN is necessary depends on how applications connect and whether they follow OS proxy settings.
Rule mode follows the active Mihomo routing rules. Global mode sends traffic through the selected global policy, while direct mode bypasses proxy routing as much as possible.
Some applications do not read operating system proxy settings or use their own network stack. In those cases, TUN may be needed for broader traffic capture.
System Proxy changes the operating system proxy configuration. TUN uses a virtual network adapter to capture more traffic and typically requires additional service permissions.
Check whether System Proxy is actually enabled, whether the browser uses its own proxy or VPN settings, and whether the active rule sends that destination to DIRECT.
No. System Proxy is enough for many browsers and desktop applications. TUN is mainly useful when applications ignore OS proxy settings or broader traffic capture is required.
Disable TUN to confirm the base network recovers, then inspect service mode, permissions, DNS, route settings and conflicts with other VPNs or virtual adapters.
Troubleshooting and performance
Confirm that Clash Verge Rev and Mihomo are running first, then check the active Profile, traffic mode, ports, DNS, proxy node and local network in that order.
Latency to a test target is only one signal. Bandwidth, node load, DNS, routing rules, the destination network and your local connection can still affect real performance.
Check whether the configured mixed, HTTP or SOCKS port is already in use. If you change it, make sure System Proxy and any manual proxy settings point to the new local port.
Read the Clash Verge Rev logs first, then check the final configuration, port conflicts, service permissions and whether the bundled core files are intact.
That usually means System Proxy is working but the other applications do not use it. Check app-specific proxy settings or enable TUN when broader traffic capture is required.
Check app and Mihomo status, then the active Profile, System Proxy or TUN, rule matching, ports and DNS, and finally the proxy node and upstream network.
If Mihomo is running, the config loads, traffic control is active and only one node, website or network environment fails, the cause is more likely upstream or local-network specific.
Continue troubleshooting
Use the download page to choose the right Windows, macOS or Linux build, or open the tutorial for Profile, System Proxy, TUN and configuration steps.