On this page
When you first open Clash Verge Rev, the home-page switches and proxy list may not yet have anything usable. After saving a remote address, download its configuration, select it, and confirm the node in use. Match a browser visit to the client’s records to tell whether setup is complete or you have only saved an address.
Add and Select a Subscription in Profiles
The profile selected on the Profiles page determines which YAML configuration Mihomo currently reads. Remote subscriptions, local profiles and overrides can coexist, but start with one remote profile so the source of its nodes and rules is clear.
Add a remote Profile
Copy the complete subscription URL
Do not omit parameters after the question mark or include extra spaces.
Add the remote configuration in Profiles
Use the ordinary link-import entry and remain on the page after saving.
Update manually
Wait for a status message and a new update time.
Select it as current
The selection marker should be on the item you just updated.
Did the Subscription Update Succeed? Check the Update Time, HTTP Errors, and Parsing Errors
Saving a remote address only creates a local record. Clicking update downloads and parses the configuration; the update time changes on success. If it fails, follow the specific error message.
401 / 403
Sign in to the subscription service and inspect the account and token; the client already reached the server.
client error(Connect) / timeout
Compare another network or an alternative import method documented by the client.
parse / yaml error
The response arrived, but its format or fields are incompatible with the current core.
200, but there are no nodes
Confirm that the response is not sign-in HTML and that the configuration contains proxies and policy groups.
A working old configuration does not mean the current update succeeded. Clash Verge Rev continues using the prior local copy, so troubleshoot updates by time and error. Do not first delete the sole working configuration.
Choose One Node in Proxies
After updating, open Proxies. The upper level normally contains policy groups such as “Node Selection,” “Auto Select,” and “Fallback”; expand them to see individual nodes. Group names come from the subscription and differ among services.
For the first test, click a specific node in the primary select group. Use url-test or fallback only after networking works, because an automatic group may switch outbound routes while you observe. Latency beside a node proves only that the test URL responded; verify a real page separately.
The proxy screen should clearly show
- The primary policy group is not empty
- The manual selection group points to a specific node
- Required service groups ultimately reference that node or a parent group
- The current mode is Rule, not accidentally left on Direct
Enable System Proxy and Check the System Proxy Address
Return to the home screen or settings and enable System Proxy. Clash Verge Rev writes the local proxy address into Windows or macOS system settings; browsers and programs that honor the system proxy then send requests to Mihomo.
If an old Clash client, VPN, or proxy extension remains on the computer, quit it first. When two clients can change the system proxy, the interface may show enabled while another program writes an old port back into the system. Use the current Clash Verge Rev mixed-port or HTTP port.
Rules and the Final Node in Connections
Verify that the system proxy actually captures traffic
Open a familiar website
Use the node you just pinned and Rule mode.
Open Connections
Find the record by time or domain.
Inspect Rule
Confirm whether the connection matches DIRECT, REJECT, or a policy group.
Inspect Chains / outbound route
Confirm that the final node matches the selection in Proxies.
If the page opens and Rule and Chains / Exit match the selected policy and node, the system proxy has captured this request.
Handling Missing Connection Records, DIRECT, and timeout
Profiles has no new update time
This update may not have succeeded. Check the subscription link, account status, and download error, and keep any old configuration that still works.
Proxies has no policy group or node
Confirm that the Profile is selected and the response uses the Clash / Mihomo format.
The browser fails, and Connections is empty
Confirm that System Proxy points to the current mixed-port, and quit the old proxy client.
The connection shows DIRECT
Rule mode selected direct access according to subscription rules; determine whether that is expected for the target site.
The connection uses the fixed node and then shows timeout
Switch to another known-good node while keeping the same page for comparison.
Request the same page again after the fix. Confirm that it opens and Connections shows the expected rule and node. Use this configuration for a while, then consider TUN or overrides only as needed.