01 Import a Subscription and Enable the Configuration
Before you begin, install a client and get a Clash-compatible subscription link from your provider. This link downloads network settings, usually including server details, proxy groups, and routing rules. Installing a client does not provide these automatically. If you don’t have a subscription yet, ask your provider how to get one and which formats are supported. This guide covers importing an existing subscription; you don’t need to write a YAML configuration file first.
Find the Subscription Field and Paste the Full URL
Open the client and look for “Subscription” or “Configuration” in the sidebar. In Clash Verge Rev, you can usually paste the link into the subscription page’s URL field and click “Import.” Other clients may ask you to click Add first, then choose “Remote Configuration” or “URL.” If prompted for a name, enter something easy to recognize, such as “Daily setup.” This label only identifies the local entry; it does not change the subscription.
Use your provider’s subscription-copy button whenever possible instead of copying part of a link from a chat. Spaces, line breaks, or missing query parameters can cause an import to fail. An account login or product page is not a subscription URL; opening it in a browser doesn’t mean the client can parse it as a configuration. If your provider offers multiple formats, choose one explicitly supported by your client or the Mihomo core.
After clicking Import, wait for the configuration to download and parse. On success, a configuration card usually appears with its name and last-updated time. Open the Proxy page to check that the proxy groups defined in the configuration are there. Then click the card’s Enable, Select, or Use option to make this subscription active. Note the difference between “saved” and “in use”: importing a new configuration may not replace the one already enabled.
Confirm It Works Before Troubleshooting Updates
If you see a name but no proxy groups, check the import message or logs. A download timeout means the configuration wasn’t retrieved; a parse error means the downloaded content isn’t in the expected format. If the result is a login page, verify where the link came from. These issues don’t all mean the proxy nodes are unavailable, and reinstalling the app should not be your first step. Check that your device can access the internet, then try updating once.
For a local configuration, choose “Import File” and select the relevant .yaml or .yml file. Don’t paste a file path into the subscription URL field. Local files won’t update when a remote subscription refreshes. For your first setup, enable just one configuration from a trusted source. Avoid switching repeatedly between subscriptions, or it may be hard to tell which one supplies the active rules.
Done when: The configuration is imported and selected as active, and the Proxy page shows its proxy groups. Once all three are confirmed, choose how to route traffic.
02 Choose Rule Mode and a Proxy Route
Open the Proxy page or the mode settings on the home screen. You’ll usually see Rule, Global, and Direct modes. These control how traffic is handled; they don’t turn the connection on or off. For your first setup, choose Rule. The client will use the configuration’s rules to decide whether each request connects directly, goes through a proxy group, or is blocked. This lets you start with the routing scheme provided by your subscription.
Use Rule Mode; Choose the Route in a Proxy Group
After choosing Rule mode, check the proxy groups below. A proxy group offers routes to choose from. Its name depends on the configuration author: it might be “Proxy,” “Default Proxy,” or something else. Find the group identified as the primary route in your configuration guide, expand it, and choose an available node. Don’t rely on the name alone; a separate service group may only handle certain sites, not serve as the default route for the whole configuration.
A group can point to another group—for example, the primary group may use “Auto,” which then chooses a route according to the configured test policy. This is a selection chain, not multiple connections. If choosing a node manually, make sure the expected entry is selected. With automatic selection, check that the group has found an available route. If the final choice is DIRECT, that traffic connects directly without using a remote proxy.
If the client offers connection tests, test candidate routes to rule out nodes that clearly time out. A test only shows how a node performed against one test address; it doesn’t guarantee a good browsing experience. For an initial setup, focus on a clear, repeatable route. There’s no need to compare nearly identical results or change every service group at once. Leave other groups at their defaults and confirm only the primary route.
Keep the Rules As They Are for Now
Global mode usually sends requests that reach the core through the global proxy group, which still needs an appropriate route. It does not mean every app is being routed. Direct mode sends requests that reach the core straight to their destination, so it can’t verify that a remote proxy works. The mode controls how the core handles a request; system proxy or VPN settings control whether the request reaches the core in the first place. Treat these as separate settings.
There’s no need to delete subscription rules during your initial setup, and don’t rewrite the whole configuration file without a backup. Subscription updates may overwrite manual edits, and rule order affects which rule matches. If a site needs custom routing, finish the checks on this page first and note which rule it currently matches. Then see the user guide for routing rules, overrides, and proxy group settings. This gives you a clear basis for comparing results before and after changes.
Done when: The mode is set to Rule and the primary proxy group has the route you expect. Your routing policy is ready, but the next step is to send app traffic through the client.
03 Connect and Route Traffic Through the Client
Return to the client’s home or settings page. Confirm that the current configuration has loaded and the core has no startup errors. The core processes connections and rules; an open window doesn’t guarantee that it’s running properly. If you see a port conflict, configuration load failure, or permissions error, resolve it before enabling the traffic entry point. To keep troubleshooting simple, quit other proxy and VPN clients during your first test so they don’t change system settings at the same time.
On Desktop, Enable the System Proxy and Test in a Browser
In the Windows or macOS desktop client, find and enable “System Proxy.” This tells apps that follow system proxy settings to send requests to the local proxy listening port. Many browsers follow this setting, making them a good choice for an initial test. Some apps use separate network settings and won’t follow it automatically. If one app doesn’t change, don’t assume the entire setup has failed.
Clash Verge Rev commonly uses 7897 as its mixed port, but check the current client settings; other clients may use a different value. A mixed port is a single local listening endpoint that supports both HTTP and SOCKS proxy protocols. When using the client’s system proxy switch, you usually don’t need to enter a port manually. If you already configured a manual proxy, make sure the system isn’t still pointing to an old client.
If your browser has a separate proxy-switching extension, set it to use system settings or temporarily disable it before testing. For your first setup, avoid enabling the system proxy, TUN, and multiple browser proxy rules at the same time; if access works or fails, it’ll be hard to tell which route was responsible. First get Rule mode, the system proxy, and one browser working together. Then expand coverage to suit the apps you use.
On Mobile, Approve VPN Access and Check the Connection
In the Android or iOS client, return to the home screen and tap “Connect” or the start button. The first time, the system may ask to add a VPN configuration or allow a VPN connection. Check which app is making the request, then approve it; you may need to unlock your device to confirm. Return to the client and check that it shows Connected or Running. Here, VPN means the system’s traffic-routing entry point; it doesn’t mean every remote route in the configuration uses the same VPN protocol.
A VPN icon in the phone’s status bar only confirms that the system traffic entry point is active; it doesn’t prove the remote route works. If another VPN is connected, disconnect it before starting the current client. Android app filters, per-app proxy settings, and battery restrictions can also affect which traffic is covered. For your first test, keep the client’s default coverage. Once you’ve verified it works, adjust the scope one setting at a time rather than adding many exclusions upfront.
Done when: The system proxy is enabled on desktop, or the mobile connection is active, and the client isn’t reporting persistent errors. Keep the client running and test real traffic.
04 Verify Access, Rule Matches, and Routes
Open a browser and first visit a site that normally works and is expected to connect directly under your configuration. This confirms your basic internet connection is working. Then visit a site expected to use a proxy—for example, github.com if your rules explicitly route GitHub through a proxy. Check the actual rules in your configuration, not just the site’s name. If the subscription doesn’t route a site through a proxy, it can’t be your only test of whether the proxy works.
Check Page Loads Alongside Connection Logs
Open the client’s Connections page, then reload the test page in your browser. Look for the destination domain or connection that just appeared. Fields vary by client; focus on the destination, matched rule, proxy group, and final route. A page may request images, scripts, and other domains, so you may see several connections. Find the request for the main page and check whether it uses DIRECT or the expected proxy group.
If the request uses the expected proxy group and the page loads, the main route from the app to the remote exit is working. If the page loads but the log shows a direct connection, that only proves the site is reachable directly—not that the proxy is working. Conversely, no new request in the connection list doesn’t necessarily mean the route is broken: browser caching may prevent a new connection, or the app may bypass system proxy settings. Reload a new page and check again.
To check your exit IP, you can use a trusted public IP lookup site and compare the result with the connection turned off. But in Rule mode, the lookup site itself may connect directly, so check the matched rule for that request too. Don’t rely solely on the displayed region; geolocation databases can be inaccurate, and a changed exit IP doesn’t prove that every app is being routed. Verify the apps and sites you actually use, one by one.
If Something Goes Wrong, Recheck the Four Steps in Order
If you can’t access a site, first return to the subscription page and confirm the current configuration is still enabled and its last update succeeded. Then check that the mode and primary group on the Proxy page haven’t changed. Next, confirm the system proxy or mobile connection is still on. If the request appears in the connection log but keeps timing out, try a known-working route for comparison. Change one setting at a time, then revisit the same site so you can identify what made a difference.
If the log reports a DNS resolution failure, investigate DNS. If it reports a connection refusal or a local port error, check that the core is running and the listener settings are correct. A site’s login prompt, access restriction, or application error doesn’t necessarily mean the proxy route is broken. Before asking for help, note the client name, operating system, selected mode, time of the error, and a redacted copy of the error text. For full DNS, port, and TUN troubleshooting, see the Clash user guide. This page focuses on getting your first connection working.
Once everything is verified, keep the working configuration and remember your primary group and connection entry point. Update the subscription as needed; if an update changes group names or rules, check the selected route again. Before closing the desktop client, you can turn off the system proxy so apps don’t keep pointing to a stopped local port. On mobile, disconnect from the client when you’re done. If something goes wrong later, start by checking what you changed most recently; there’s no need to repeat the entire setup.
First-time setup complete: The site expected to connect directly loads, the site expected to use a proxy loads, and the connection log shows the corresponding route. From here, add settings only for the apps you actually use—there’s no need to enable every option just to make the setup feel complete.