Clash Verge Rev Interface Guide: Proxies, Profiles, Connections, and Logs
Learn what each sidebar page does: switch proxy groups, manage subscription profiles, inspect connections and logs, and configure key settings in Clash Verge Rev.
Understand each page—and how traffic gets in
When you open Clash Verge Rev, follow this sequence: Profiles → Proxies → Settings → Connections → Logs. Profiles determine which nodes and rules are loaded; Proxies control the active outbound choice for each policy group; Settings determine how app traffic reaches the client; Connections and Logs help verify what happened. Selecting a node alone does not mean Windows apps are using the proxy.
Clash Verge Rev is a graphical client; the mihomo core handles the actual connections. This guide covers the commonly seen Chinese-language interface on Windows. Button locations and settings groups may vary by version, and proxy group names depend on your subscription. Don’t assume a tutorial’s “node selection” button must exist under that exact name—use the labels shown in your current profile.
| Sidebar page | Main tasks | What to check |
|---|---|---|
| Profiles | Import, select, and update subscription profiles | Missing nodes or failed profile updates |
| Proxies | Switch modes, choose proxy group outlets, and test latency | Wrong node in use or an unavailable group |
| Connections | Inspect destinations, matched rules, proxy chains, and traffic | Whether an app reached the core and which policy it followed |
| Logs | Inspect profile loading, parsing, and dialing errors | Why a request failed and at which stage |
| Settings | Configure the system proxy, TUN, ports, and services | Browser works, but other apps don’t |
Profiles: Import a subscription and activate a profile
First-time import steps
- Get a configuration link for Clash or mihomo from your subscription provider. Account login pages, purchase pages, and browser share pages usually can’t be imported as subscriptions.
- Open “Profiles” in the sidebar, paste the full URL into the subscription link field, and click “Import.” Keep all query parameters in the URL.
- Wait for the profile card to appear, then click it to make it active. If your version uses a selection indicator, check that the card shows as active.
- Go to “Proxies” and confirm that proxy groups and nodes are listed. If you still see the old content, check whether you imported a new card but forgot to switch to it.
A subscription profile can include more than server addresses: it may also define proxy groups, routing rules, and DNS settings. Importing two subscriptions doesn’t merge them; switching profiles normally activates just one at a time. If you need to combine nodes or override rules, check the extension mechanism for your version instead of repeatedly clicking cards in an attempt to stack profiles.
Updating a subscription vs. editing a profile
Find the profile card in “Profiles” and use its update button or menu. An update fetches the remote content again, so local edits to the downloaded file may be overwritten next time. For changes you need to keep, use a supported override or extension method, and back up the original content first.
- Import failed: Check “Logs” to see whether the URL is unreachable, authentication has expired, or the content couldn’t be parsed. A page opening in your browser doesn’t mean its contents are a valid profile.
- Nodes suddenly disappeared: First check which profile is active and whether your provider’s service is working. Don’t assume the interface has lost data.
- Rules changed after an update: Check whether the subscription changed its policy groups or rules, then see if your local overrides still apply.
Proxies: Understand modes and proxy groups
Open “Proxies,” check the current mode, then choose a node. Common modes include “Rule,” “Global,” and “Direct.” They determine how the core chooses an outbound route—not whether Windows sends traffic to the core. Even in Global mode, an app can bypass the client if it doesn’t use the system proxy and isn’t routed through TUN.
| Mode | How it works | When to use it |
|---|---|---|
| Rule | Matches rules in order and applies the corresponding policy | Good for everyday routing; check which group handles the destination before choosing a node |
| Global | Routes connections that reach the core through the Global policy group | Useful for a brief comparison while troubleshooting; switch back afterward |
| Direct | Usually sends connections reaching the core directly | Doesn’t disable the system proxy or close the client |
Why didn’t changing the node change the route?
Rule mode may show several proxy groups. For example, one site may match a “Streaming” group while another uses “Default Proxy.” Changing “Default Proxy” won’t necessarily affect “Streaming.” A group may also select another group, creating a multi-level policy chain. Check the final outlet on the “Connections” page rather than judging by a card’s selected appearance.
Manual groups let you choose an option; automatic URL-test groups usually select based on test results and tolerance; fallback groups switch according to availability and configuration order. The group type in the profile determines the behavior. If the interface shows automatic selection, check what the group is for before treating it as a failure to save your manual choice.
What do latency readings tell you?
A group’s latency test only reports connectivity at that moment between the node and the configured test URL. For example, readings of 80 ms and 160 ms are illustrative, not measurements from this guide. An 80 ms result doesn’t guarantee faster downloads or access to a particular site. Timeouts may also be caused by the test URL, DNS, or a temporary network issue, so verify with an actual connection.
Settings: Start with the system proxy, then enable TUN if needed
System proxy and ports
Go to “Settings” → “System Proxy” and enable it so apps that follow Windows proxy settings use the client’s local listener. Some versions put this switch in a quick-access area on the home page; it still controls the same type of traffic entry. Browsers usually use the system proxy, but command-line tools, games, and apps with their own proxy settings may not.
In “Settings,” find the port options and check the “Mixed Port” value. For example, if the interface shows 7897, you can set a manual proxy on this device to address 127.0.0.1 and port 7897. These are example values: don’t assume another guide’s 7890 or 7897 is your local port, and don’t enter the controller port as the proxy port.
- For this device:
127.0.0.1refers to the current device; it won’t let another phone connect to your computer’s proxy. - For LAN access: Separately check whether LAN connections are allowed, which address the client listens on, and the Windows Firewall rules. Enabling the system proxy doesn’t share it automatically.
- Port conflict: If the logs report that an address is already in use, check whether another proxy client is running and competing for the same port.
TUN mode and service mode
“Settings” → “TUN Mode” uses a virtual network interface to route traffic that matches the routing conditions, which can help with apps that ignore the system proxy. It involves routing, DNS, and permissions; it doesn’t simply mean “faster.” First use the system proxy to confirm that the profile and nodes work, then enable TUN to distinguish node problems from traffic-capture problems.
On Windows, first open the “Service Mode” section in “Settings” and confirm that the service is installed and running. Then enable TUN as required by your version. Service mode provides the conditions needed for privileged core operations; it isn’t a proxy node and doesn’t choose an outbound route. If Windows asks for permission when installing or repairing the service, verify the program’s source before proceeding.
Connections: Check matched rules and the actual route
Open “Connections,” then make a new request from the app you’re testing. The list may show the destination domain or IP, upload and download traffic, connection time, matched rule, and proxy chain. Whether it shows a process name depends on permissions, the platform, and process-identification settings. A missing process name doesn’t necessarily mean the connection came from an unknown app.
- Narrow it down: Pause unrelated downloads, then filter by destination domain, IP, or process. Traffic appearing in the list alone doesn’t prove the app you’re testing is being routed through the client.
- Open the details: Check the matched rule and final policy. If it shows
DIRECT, that connection was routed directly. If it went through a proxy group, check the node at the end of the chain. - Establish a new connection: After switching nodes, refresh the page or reopen the app so it creates a new connection. Existing long-lived connections may continue using the previous route.
- Close connections selectively: If needed, close only the connection you’re testing and try again. Closing all connections can interrupt other downloads, videos, and live sessions.
With TUN enabled, a destination may appear as a Fake-IP mapping address. Don’t assume a request went to an unusual server just because you see an address in 198.18.0.0/16; check the domain, DNS mode, and connection details. Conversely, if the destination request doesn’t appear at all, first check the traffic entry method, filters, and whether the request was actually sent again—not the routing rules.
Logs: Troubleshoot by stage
Use “Logs” to answer “Why did it fail?” Note the time before reproducing the issue, clear any filters, and inspect the new entries. Start with the info level for routine troubleshooting; switch temporarily to debug if you need more detail, reproduce the issue once, then switch back. Debug logs are more verbose and may contain sensitive details such as domains and addresses, so don’t leave them enabled or share them publicly.
| Common log clues | Check first | What to do next |
|---|---|---|
parse and yaml errors | Check whether the profile format and fields are valid | Return to “Profiles,” review recent edits, and restore a valid profile |
address already in use | Listening port already in use | Close the conflicting app, or change the port and update the app settings to match |
lookup and DNS timeouts | The domain resolution path | Check the DNS configuration and whether upstream servers are reachable before blaming the node password |
timeout、connection refused | Connection destination and current network | Determine whether the node dial failed or the destination server refused the connection, then compare with another node |
These keywords are clues, not definitive diagnoses. For example, a timeout could occur while downloading a subscription, connecting to a node, or accessing a destination site. Check the destination address and nearby context in the same log entry before deciding whether to update the subscription in Profiles, switch nodes in Proxies, or check ports in Settings.
When asking for help, keep a few entries around the error and include when it happened, the current mode, whether TUN was enabled, and whether you can reproduce it. Before sharing, hide subscription tokens, node credentials, and any connection history you don’t want to reveal. A screenshot of one red error line is rarely enough to identify the cause.
Complete checklist for your first connection
Use this checklist to verify your first connection from start to finish. Keep to one profile and one traffic-entry method until everything works; add automatic testing, TUN, or extended rules afterward.
- Open “Profiles,” import your subscription, select the corresponding profile card, and check for parsing errors.
- Open “Proxies,” select “Rule” mode, and choose an available node in the proxy group you need.
- Open “Settings,” enable “System Proxy,” and note the Mixed Port shown. Leave TUN and DNS unchanged for now.
- Make a new request in your browser, then open “Connections” to check the destination, rule, and final route.
- If it fails, open “Logs,” find the new error by time, and return to the relevant page to fix it.
- After the browser test succeeds, try your other apps. Configure service mode and TUN only if you need them to capture that traffic.
When you finish testing, turn off the system proxy or TUN in the client if you no longer need it, then exit normally. If your browser can’t connect after the client exits unexpectedly, check Windows 11 “Settings” → “Network & internet” → “Proxy” → “Use a proxy server” for a leftover local address with no app listening. If your device is managed by your organization, confirm where the proxy policy comes from before changing any required settings.
Remember how the pages fit together: Profiles manage sources, Proxies manage selections, Settings control traffic entry, Connections show the actual route, and Logs help identify failures. Checking them in this order is more likely to pinpoint the problem than repeatedly reinstalling the client.