Clash Meta FAQ Center 5-minute self-service troubleshooting of typical faults
Complete the most common faults and solutions when using Mihomo kernel clients such as Clash Verge Rev, FlClash and so on. Each FAQ is organized in the order of "Symptom Self-Check → Quick Diagnosis → Classified Troubleshooting → Platform Differences". Most problems can be solved by yourself within 5 minutes.
No matter what the problem is, take these 5 steps first
90% of proxy client issues can be located through the following general process. Please check step by step in order, only change one variable at a time, and remember the results of each step.
-
1See subscription
If I paste the subscription link in the browser, can the content be returned normally? Is YAML, Base64, or blank returned?
-
2See node
Does the client parse the delay one by one, is it ∞/timeout? Or is there a number?
-
3See proxy status
On the desktop side, confirm that the "System Proxy" or "TUN" switch is turned on; on the Android side, confirm that there is a VPN key icon in the status bar.
-
4See rule
Comparison of temporary switching between rule mode and global mode can determine whether DIRECT is taken away by rule matching.
-
5See log
View real-time records on the client's "Log" page, keyword search
error/timeoutFind clues.
Included fault topics
The following are frequently asked questions that have been written into special pages. Each article includes a complete diagnosis process, root cause analysis, platform troubleshooting and log reference.
Subscription shows that the import is successful, but the node list of the agent page is empty? Common causes include expired subscriptions, mismatched formats, and airport addresses blocked by operators. This article gives a complete process of troubleshooting in order.
The agent is turned on and there is a delay in node display, but the browser just can't open the web page? It involves many aspects such as node survival, system agent taking effect, TUN and system agent conflicts, rule matching, DNS pollution, etc.
Small problems that can be solved without a special page
The following scenarios usually only require one or two steps to solve. Click to expand to see the answer.
Clash Verge Add the installation directory to the trust whitelist. Windows Defender path: Settings → Privacy and security → Windows Security Center → Virus & threat protection → Exclusions.
- Right-click the Clash Verge icon → "Open" → click "Open" again in the pop-up window
- Or execute in the terminal:
sudo xattr -dr com.apple.quarantine /Applications/Clash\ Verge.app
- Windows: Settings → Network and Internet → Proxy → Turn off "Use proxy server"
- macOS: System Settings → Network → Current network → Details → Proxy → Turn off all check options
- Linux GNOME: Settings → Network → Network Proxy → Change to "None"
- Turn on "Auto-start at boot" + "Automatically connect at startup"
- Enable "Installation Service Mode" on the desktop (Windows) or allow background running (macOS/Linux)
- When using the client, manually click "Refresh Subscription" once to confirm synchronization with the latest billing status of the airport
- The node is speed-limited by the operator's QoS
- Evening peak congestion (Beijing time 20:00 - 23:00)
- The node's own bandwidth budget has been used up
- The line is a transfer, a long detour
If you encounter problems, check the log first
Logs are the key to troubleshooting. You can see real-time connection records, error messages, and rule hits on the client's "Log" page. The following are the standard locations of log and configuration directories for each platform.
%APPDATA%\io.github.clash-verge-rev.clash-verge\
Contains subscriptions, configuration files, and running logs.
~/Library/Application Support/
io.github.clash-verge-rev.clash-verge/
Finder ⌘⇧G Enter the path directly.
~/.config/clash-verge/
~/.local/share/clash-verge/
The former puts the configuration, and the latter puts the running data.
/Android/data/com.follow.clash/
files/
Android 11+ requires access via SAF.