First-Time Setup · 4 Steps

Clash Quick Start

Import a subscription, route traffic by rule, then verify the path with a new connection.

Import and Enable a Subscription

Import from a Link or File

Start with a subscription link from a trusted source that supports Clash or mihomo, or an existing YAML configuration. A subscription link retrieves a configuration; it is not a server address to enter in your system proxy settings. Subscription links may contain account credentials, so paste them directly into the client. When troubleshooting, never post the full link in public discussions or screenshots.

Open the client's Profiles or subscription page and find the add option. For a link, choose Import from URL or Remote Profile, paste the full address, and confirm. For a YAML file, choose Import File or Local Profile, then select the file. These options are not interchangeable: the client fetches a link, while a local file is read directly from your device. If asked to name the profile, choose a label that identifies its source; this makes updates and logs easier to track.

Make Sure the New Profile Is Active

Wait for the download or parsing to finish, then return to the profile list. A new entry means the profile was added, but it may not yet be loaded by the core. Select it and choose Enable or Apply, as prompted. Look for a checkmark or status label to confirm. Then open the Proxies page and check that the expected nodes or proxy groups appear under the profile you just selected. If the list still shows the previous profile, check which one is active rather than adding the same link again.

If importing fails, first identify when the error occurred. For a download failure, check that the device is online, the full URL was copied, and the subscription is still active. If the download succeeds but parsing fails, the response may be a login page or a configuration format for another client; changing the file extension won't fix it. Check the export format at the source. If the error specifically names an unsupported field, see the configuration file reference. Once the new profile is confirmed as loaded, continue to mode settings.

Choose a Proxy Mode

Start with Rule Mode

Find Mode at the top of the Proxies page or on the client's home screen, then choose Rule. Rule mode checks connections that reach the core against the configuration's rules in order, and uses the outbound route specified by the first matching rule. Some requests may connect directly while others use a proxy. So a DIRECT entry in the connection log doesn't necessarily indicate a problem; what matters is whether the route matches the configuration for that destination.

If Global and Direct appear alongside Rule, don't mistake them for connection toggles. Global mode typically sends connections handled by the core to the global policy, making it useful for briefly checking rule-matching or outbound issues. Direct mode sends those connections out without a proxy. Neither mode determines whether the browser sends requests to the core in the first place. For this initial setup, stay in Rule mode and enable a traffic entry point in the next step. This makes it easier to pinpoint the cause if something goes wrong.

Check the Current Proxy Group Selection

Expand the proxy groups provided by the configuration and find the one responsible for proxy traffic. Group names depend on the configuration and can vary between subscriptions. If there's a manual selection option, choose a node known to work and note its displayed name. Choosing a node only affects connections routed to that group. If a rule sends a request to another group, your selection won't apply to it.

If the configuration routes traffic through an automatic selection group, keep its default setting for now and check the actual outbound route in the connection log. If the client offers a node test, use it for a preliminary check within the group. A successful test only confirms that the node can reach the test address; it doesn't mean your browser is connected or that a particular site will use that group. For more on nodes, proxy groups, and routing rules, see the glossary.

Connect and Route App Traffic

Desktop: Test with the System Proxy First

Find System Proxy on the desktop client's home screen or in its tray menu. If the client has a separate Start button, start the core first and make sure there are no profile-loading or listening errors, then enable the system proxy. Test with a browser that follows system proxy settings. If the browser has an extension that changes proxy settings, or the app uses its own proxy, make sure it isn't overriding the system settings. A running status only means the process has started; it doesn't confirm that your app is sending requests to the core.

You don't need to enable TUN for the first test. Use TUN only if the system proxy works in your browser but an app doesn't follow system proxy settings. To isolate any issues, finish testing the system proxy first, then enable TUN on its own. Follow the prompts to configure permissions or services and make another request. If enabling it triggers an error or switches itself off, read the current error and identify whether it's a permissions, service startup, or configuration issue. Don't keep toggling the setting.

Mobile: Approve the System Connection

Return to the mobile client's home screen and confirm that the newly enabled profile is shown. Tap Connect or the power icon. The first time you connect, the system usually asks whether the client can establish a VPN connection. Check the app name in the prompt and approve it, then return to the client to check the connection status. A VPN icon in the status bar can confirm that a connection is established, but it doesn't prove that a specific domain is using a proxy node; a rule may still send the request directly.

If the client disconnects again after you tap Connect, check whether you dismissed the permission prompt, another VPN connection is already active, or the profile failed to load. On a managed device, follow your organization's device policies. Before trying again, change only one setting at a time so you can tell what made a difference. Once the client no longer reports a startup error, keep the current mode and node as they are and move on to the final check.

Verify Your Connection

Check the Logs with a New Request

Open Connection, Connection Log, or Logs in the client, then visit a site in your browser that you can reach and whose expected route you know. Choose a domain with a clear rule in the configuration. If the site is already open, close that tab and visit it again. If no new entry appears, try another domain with a known expected route. The browser may serve a cached page or reuse an existing connection, so a refresh or successful page load alone doesn't confirm that a new, observable connection was made.

Find the entry by time and destination domain, then check three things: whether the core received the request, which rule it matched, and which proxy group or outbound route it used. Some clients show these details in the connection view rather than the list. A DIRECT entry is expected for traffic that should connect directly. For traffic that should use a proxy, look for the expected group and node or a corresponding outbound entry in the log. Verification is complete when the page loads and the connection takes the expected route.

Return to the Relevant Step Based on What You See

If there's no matching entry, go back to the connection step. Confirm that you're viewing the running core, the browser is using the selected traffic entry point, and a fresh request rules out cached results. If an entry appears but the outbound route is wrong, revisit the proxy mode and group, paying particular attention to broad rules that may match first. Don't assume the proxy is broken just because your public IP hasn't changed; the IP-check site may match a direct-connection rule.

If the expected proxy group is selected but the site still won't load, check the error at the same time as the request. For a DNS error, check the destination domain and the DNS settings in the configuration. If the error points to a proxy node connection timeout, choose another known-working node in the same group and test the same destination again. Keep the group and destination the same so you can tell whether the node made a difference. If every node fails, check the network, subscription status, and core errors; there's no need to reinstall the client right away.

After testing, keep the profile that passed verification and leave Rule mode enabled. If you temporarily switched to Global mode or another traffic entry point, restore your usual settings and check the connection log once more. For changes to DNS, proxy groups, or override order, consult the configuration file reference. Change one thing at a time and retest with the same destination.