1. Import a Subscription and Activate the Configuration
Before you start, make sure you have a subscription URL you’re authorized to use or a working local YAML configuration file. The client reads the configuration and routes requests; installing it does not provide proxy service access. Subscription URLs often contain credentials, so don’t share the full URL in public screenshots, forums, or online conversion tools. If you don’t have a configuration yet, confirm where to obtain one before continuing.
Paste the Subscription URL on the Profiles Page
Open Clash Verge Rev and select Profiles in the sidebar. Find the subscription URL field, paste the complete URL, and click the import button beside it. Button labels and layouts may vary slightly between versions, but the process is the same: import a remote configuration URL. Check the beginning and end of the URL to make sure you haven’t included instructions, quotation marks, or line breaks. Don’t use your provider’s login page URL as a subscription URL.
After importing, wait for a new profile card to appear on the Profiles page. Downloading and parsing can take a little while, so avoid clicking repeatedly and creating duplicate cards. Once the card appears, select it or use its menu to activate it as the current profile. Saving a subscription to the list isn’t enough—you must confirm that it’s selected as the active profile.
Next, open the Proxies page and check that the profile’s proxy groups and available options appear. Seeing the groups means the client has at least read the relevant configuration; it doesn’t guarantee that a node can connect, but you can move on to the next step. If you still see groups from the previous profile, return to Profiles, confirm the new profile is active, wait for the core to reload, and check again.
Local Files vs. Subscription Formats
For a local file, use the file import option on the Profiles page, select the .yaml or .yml file, and activate the imported profile. The file extension is only a clue; its contents must still match a configuration structure supported by the client. Don’t save a web page as YAML and import it, or simply change a file’s extension to pass off a list of proxy nodes as a complete configuration.
Remote subscriptions can be updated from their source, while local files usually need to be replaced or edited manually. Some subscriptions offer multiple formats, such as Clash YAML and generic node lists. Choose a configuration intended for Clash or Mihomo. A Base64-encoded node list may not work as a complete configuration; if the format isn’t supported, ask the provider which formats are available. Learn more about the differences between subscriptions, configuration files, and nodes in the Glossary.
If the import fails, start with the error message. For a download timeout, check whether your current network can reach the subscription URL. For a parsing error, check whether the response is a login page, an error message, or an unsupported format. Import errors and node connection failures happen at different stages; switching proxy nodes repeatedly won’t fix a configuration that hasn’t downloaded. Once the import issue is resolved, return to the Proxies page.
Step complete when: The target profile is selected on the Profiles page, and its proxy groups appear on the Proxies page. Don’t enable multiple traffic-routing options yet; first decide which proxy mode to use.
2. Choose a Rule Mode and Proxy Strategy
Once the profile has loaded, open the Proxies page or the mode selector in the interface. For your first setup, choose Rule mode. It applies the rules in your configuration to route different requests directly, through a proxy, or another way, making it a good choice for everyday use. Routing depends on the rules in the active profile, so the same mode can produce different results with different configurations.
The Mode Controls Routing; the Proxy Group Chooses the Exit
Rule, Global, and Direct are modes—not three connection switches. Rule mode selects a strategy based on matching rules. Global mode sends requests that reach the core to the global strategy. Direct mode connects requests that reach the core straight to their destinations. Global mode does not automatically capture traffic from every app; traffic that never reaches the client is unaffected. Start with Rule mode so you can inspect which rules are matched.
After choosing a mode, expand the main proxy groups on the Proxies page. Group names depend on the configuration author and may be something like “Select Node,” “Proxy,” or another label, so don’t expect an exact match. Review the options and choose an available node. If the configuration includes an auto-select or failover group, you can choose that instead. Confirm the selected option has changed before continuing.
Some configurations use different groups for different purposes, such as general browsing and specific services. Changing one group may not affect the route for every request. You don’t need to reconfigure everything for your first setup; keep the defaults and check that the group used by the site you plan to visit points to an available option. If you’re unsure what a group does, read the proxy group glossary instead of deleting unfamiliar groups.
Test Results Are Only a Clue
If the Proxies page has a test button, run it once to see whether the selected node responds. The test uses a specific address and request method, so a successful result doesn’t guarantee that every site will work. A timeout may also be caused by the test address. In step 4, visit the actual site and check its connection record to confirm the route works as expected.
After switching subscriptions or updating a profile, check the selected proxy group again. The new configuration may use different group names and rule references, so don’t assume your previous selections carry over. If a group has no available nodes, return to step 1 and check the subscription content instead of switching straight to Global mode. Once you’ve connected successfully, learn about nested groups, rule sets, and auto-select settings in the Advanced Config guide.
Step complete when: Rule mode is selected, and the main proxy group points to an available option. Next, route app traffic through the client. Choosing a node alone won’t change your browser’s network route.
3. Enable the System Proxy and Connect
Open Settings and confirm the core is running normally, without repeated startup or configuration-loading errors. Find Port Settings or the equivalent network section and note the current mixed port. A common value is 7897, but use the port shown in your client—the example isn’t a fixed requirement.
Start with the System Proxy
Find and enable System Proxy. This directs your desktop’s system proxy settings to the client’s local listening address, so apps that follow those settings send requests through the client. Check that the switch stays on. If it immediately turns off, check the client’s notices and logs; a switch that briefly appears enabled doesn’t mean the connection is working.
Open a browser that follows system proxy settings, start a new tab, and visit the site you want to test. If the browser was already open, refresh the page or restart the browser if needed, so it doesn’t reuse an existing connection. Browser extensions, custom proxy settings, and other proxy software can override system settings. For your first test, use just one clearly configured proxy entry to make troubleshooting easier.
The system proxy doesn’t route traffic from every program. Some command-line tools, games, and apps with their own network settings ignore it, so a working browser alongside an app that’s still unchanged doesn’t necessarily mean the node is at fault. First check whether that app supports its own proxy settings; then decide if TUN mode is needed. Don’t change the system proxy, DNS, and virtual network adapter all at once before verifying the browser connection.
Configure TUN and Manual Ports Only If Needed
For your first connection, leave TUN mode off. TUN uses a virtual network interface to capture traffic and involves system permissions, routing, and DNS. It won’t make a node faster or fix every problem. Enable it separately only if a target app ignores the system proxy and you need to route more of its traffic. Follow the TUN section in the Advanced Config guide.
If an app asks you to enter a proxy server manually, use the local loopback address 127.0.0.1 on the same computer, along with the actual port you noted earlier. Choose HTTP or SOCKS as required by the app. Don’t copy a port from another guide or enter your subscription URL as the proxy server address. The mixed port accepts supported proxy connections; it is neither a subscription URL nor a remote node’s server port.
If you see a message that the listening port is already in use, check whether another instance of the client or another proxy tool is running. Close the duplicate, or choose an unused port in Settings. After changing the port, confirm that the system proxy uses the updated value. Update any apps you configured manually as well. If you change the app’s port but leave the client unchanged, the app will connect to a port with no service listening.
Step complete when: The core is running, the system proxy is on, and the browser has sent a new request. Next, check how that request was handled rather than relying on the switch’s color.
4. Verify Request Routing and Connection Results
Open the client’s Connections page, then revisit the site you need in your browser. Check both screens for the destination domain or address from your latest request. Fields can vary between versions; focus on the destination, matched rule, and proxy chain. Some requests finish quickly, so check the history if available, or look immediately after refreshing the page.
Match the Page Result to the Connection Record
If the target request appears on the Connections page, it has reached the core. Check which rule it matched and which strategy it used. A site expected to use a proxy should show a proxy strategy in its chain; DIRECT may be perfectly normal for a site expected to connect directly. Rule mode allows different destinations to follow different routes, so not every direct connection is a failure.
If the site loads but there’s no matching record on the Connections page, rule out cached content: open another page or trigger a new resource request, then check again. If the request is still missing, the browser may not be using the system proxy, or an extension or custom network setting may be bypassing it. A page loading successfully doesn’t prove its request went through the client. Likewise, a connection record alone doesn’t prove the remote service responded successfully.
An optional IP lookup can provide another clue, but it’s not conclusive. Rules may send the lookup site directly and route another site through the proxy, so one result can’t represent every app. Prioritize the connection record and page response for the site you actually need. Change just one setting at a time, then make a new request to see what changed.
Troubleshoot in Order
If the browser can’t reach a site, first confirm the correct profile is active, then check that the selected proxy group points to a working option. If switching nodes fixes the issue, investigate the original node or its service status. If all options fail, check the proxy entry point, core status, and current network. Don’t delete the whole profile straight away; you may lose settings that could help narrow down the problem.
If no new requests appear on the Connections page, check the system proxy switch, the browser’s custom proxy settings, and any manually configured listening port. If requests do appear but keep failing, check the Logs page for entries around the time of your test. Connection timeouts, DNS resolution failures, and configuration parsing errors happen at different stages; follow the specific error instead of assuming the subscription has failed. Hide subscription credentials and other private information before sharing logs.
Once the connection works, note the profile name, proxy mode, main proxy group, and actual mixed port. Compare against these known-working settings if problems arise later. To explore DNS, Fake-IP, local overrides, or rule sets, make changes one at a time in Advanced Config. If you’re unsure about a term, check the Glossary and keep your first-time setup simple.
Stop the Connection and Start Again Later
Before you stop using the client, turn off the system proxy and then exit the client. If you enabled TUN, turn it off first and wait for network settings to be restored. This prevents apps from sending requests to a local port after the client has exited. If pages won’t load after you quit, check whether the system still points to the client’s proxy port, restore the settings, and test your regular connection again.
Next time you start the client, quickly check that the profile is active, the right proxy group is selected, and the connection entry point is enabled. Only enable startup launch or automatic system proxy settings after you’ve manually tested connecting and shutting down. If a subscription update changes the proxy groups, review your selection again instead of relying on the update-success message.
Step complete when: The target site responds, its connection record shows the expected rule and strategy, and your regular connection works again after you turn off the proxy. You’ve now completed all four steps of the initial setup.