Clash Nyanpasu Setup Guide

Before You Begin: Install the Client and Get a Subscription

Start by choosing an installer from the Download Center that matches your operating system and processor architecture. Install and open the client. If the system asks for network access on first launch, review what it is for and allow it if needed. Don't run multiple proxy clients at once or enable TUN just yet. If another tool is managing the system proxy or a virtual network adapter, disconnect it first so it won't affect your test results.

The client loads configurations, runs the core, and manages traffic; it cannot create a working remote connection on its own. Before continuing, you'll need a subscription URL from a trusted source that hasn't expired, or a configuration file compatible with your core. Subscription links are usually available in your provider's account dashboard—not the account sign-in URL or a link to an information page. Without a subscription, you can explore the interface, but installing the client alone won't connect you to a remote proxy.

Treat your subscription URL like an account credential. Don't post it publicly or show the full address in support screenshots. This guide doesn't require changes to advanced DNS settings, listening ports, or core versions. Keep the defaults for now, and note the current profile name and the proxy group you plan to use. That makes it easier to pinpoint what changed if something goes wrong.

Step 1: Import a Subscription and Enable the Configuration

Add a Remote Subscription on the Configurations Page

Open Configurations or Subscriptions in the sidebar, then look for an option such as New, Add, or Import. If the client offers both a remote URL and a local file, choose the remote URL for a subscription link. Paste the full URL into the address field and make sure it doesn't include extra spaces, line breaks, or explanatory text at either end. Give the profile a recognizable name, such as “Daily.” Click Import or Save, then wait for the client to download and parse it.

After a successful import, the profile should appear in the list. Some versions show an update time or status, but seeing a profile card doesn't mean it's active. Click its enable option or set it as the current profile. Then open the Proxies page and check that proxy groups and selectable options are available. Names come from the subscription and may not be “Proxy” or “Node Selection,” so use the groups in your configuration rather than copying labels from a guide.

For a local configuration file, use the file import option and activate the profile after importing it. A local file usually won't update automatically like a remote subscription; editing the original file doesn't necessarily reload it in the client. For your first setup, keep just one clearly identified active profile. That way, you won't accidentally update one profile while running another.

Confirm the Import Worked Before Continuing

If parsing fails during import, stop here rather than trying to work around it with Global mode or TUN. Common causes include an expired subscription, a link that redirects to a sign-in page, an incompatible format, or indentation errors in a local configuration. Check the client log for the import attempt. If the download failed, check the URL and your current network. If the log reports an unknown field or syntax error, ask your provider which subscription format to use. A file containing only a list of nodes may not include the rules and proxy groups needed to verify traffic routing in this guide.

Don't paste your subscription into an unfamiliar online converter. If you need to handle a format mismatch, first read the compatibility notes in Protocol and Core Technical Reference. For common checks when updates fail, see Frequently Asked Questions. Move on to choosing a mode only after the profile is active and the Proxies page shows usable proxy groups.

Step 2: Choose a Proxy Mode and Proxy Group

Start with Rule Mode

Find the Rule / Global / Direct mode switch on the home or Proxies page, and select Rule. In Rule mode, requests are routed according to the rules in your current configuration, making it a good fit for everyday use when some services should connect directly and others through a proxy. Global mode typically sends requests to the global proxy group, but that doesn't guarantee the group is set to a remote node. Direct mode is primarily for direct connections. For your first setup, stick with Rule mode so you have a consistent baseline for testing.

Choosing a mode and choosing an outbound route are separate actions. After selecting Rule mode, check the main proxy group in your configuration that handles proxied traffic. Expand it and select an available node from your subscription, or use a preconfigured auto-select group. If the current selection is DIRECT, requests matched to that group may still connect directly, even with the system proxy enabled. An enabled toggle alone doesn't mean all traffic is going through a remote proxy.

Follow the Proxy Group Chain to the Final Selection

Some configurations route a group such as “Daily Proxy” through “Auto Select,” which then picks a route from several nodes. You don't need to change every group in a chain. Follow the current selection down and confirm it leads to an available node from your subscription. For separate groups that route different categories of sites, keep the subscription defaults at first. Change an individual group only if you confirm its route isn't what you need.

If the client offers a connectivity test, run it once to rule out obviously unavailable options. A successful test only means that the specific test request worked at that moment; it doesn't guarantee every site will load, and latency isn't the same as download speed. If every test fails, check the subscription status, device time, and current network first. Avoid changing the mode, DNS, and core all at once, or it will be harder to find the cause.

At the end of this step, you should know two things: that Rule mode is active and which main proxy group handles proxied traffic. For more on the differences between rules, proxy groups, and auto-select, see the Glossary. Save rule evaluation order and protocol choices for the Technical Reference. Keep your current selections unchanged; the next step is about getting app traffic into the client.

Step 3: Start the Core and Connect

Check That the Core Is Running Before Enabling the System Proxy

Return to the client's home or settings page and check that the core is running. Some versions start it automatically when you enable a profile; others require you to click Start. You don't need to switch to a test core to get started—use the current stable option. If you see a port conflict, configuration load error, or core shutdown, open the log and address that error first. If the core isn't running, enabling the system proxy may point your browser to a local service that isn't responding.

Once the core is running, enable the system proxy. This updates the operating system's proxy settings so apps that follow them send requests to the local core. Test with a regular browser first. If the browser has its own proxy extension or manual proxy settings, disable them temporarily to avoid conflicting settings. You don't need to enable Allow LAN; that option is mainly for letting other devices use your computer as a proxy, not for connecting your own device to the internet.

Keep the client running in the background while the system proxy is enabled. Closing the main window may minimize it to the tray or quit the app, depending on your settings. Keep the window open during your first test. If sites that were working suddenly stop loading, disable the system proxy and check whether your regular connection works again. Then check the core status and proxy group. Don't force-quit the client while the system still points to its local proxy.

Try TUN After the Browser Works

Not every app follows system proxy settings. If your browser works as expected but a desktop app has no connection entries, consider using TUN. TUN routes traffic through a virtual network interface and may require a service installation, administrator privileges, or system network permissions. Follow the client's prompts, make sure no other VPN or virtual adapter tool is also routing traffic, then enable TUN on its own and test again. Keep the network stack, automatic routing, and DNS at the client-recommended values; there's no need to copy settings from another device's screenshots.

If the system proxy meets your needs, you can leave TUN off. Whether both should be enabled depends on the client and the apps you use—having both on isn't a measure of a successful connection. On mobile, tapping Connect usually triggers a system VPN permission prompt. Make sure it comes from the client you're using, allow it, then return to the app to check the connection status. A desktop system proxy toggle and a mobile VPN connection are different mechanisms, so don't expect them to work the same way. Once traffic routing is enabled, test it with an actual request rather than relying on the connection indicator.

Step 4: Verify Sites, Rules, and the Outbound Route

Send a New Request and Check the Connection Log

In your browser, open a site you can access that should use a proxy under your current rules, then reload it. Don't rely on a tab that's been open for a while: cached content may not generate a new connection. Next, switch to the client's Connections page and find the domain you just visited. Check the matched rule, proxy group, or proxy chain, depending on what's shown in your version. The fields can vary, but the goal is to confirm that the request reached the core and was handled by the expected strategy.

If the page loads and the connection log shows the expected proxy strategy, that route is working. Then visit a regular site that should connect directly under your configuration and check that its log entry uses a direct route. Rule mode routes requests according to your configuration; it doesn't mean every connection should show a proxy. If you use an external IP lookup service, treat the result as supporting evidence for that request only—it can't prove that every app on your device is being routed through the client.

Troubleshoot in Order: Traffic Entry → Strategy → Outbound Route

If a site won't load and there's no matching entry on the Connections page, first check whether the browser follows system proxy settings, whether a proxy extension overrides them, and whether the system proxy is still enabled. If the app doesn't use the system proxy, try TUN after confirming that the browser works. Switching remote nodes probably won't help yet because the request hasn't reached the core. The connection may also end too quickly to appear in the list, so check the log as well.

If there is a connection entry but it shows an unexpected strategy, return to Step 2 and check the active profile, mode, and proxy group. Make sure you're looking at the profile that's actually enabled, then see which rule matched. If the strategy is correct but errors persist, check the log for timeouts, DNS resolution failures, or handshake errors. Change one thing at a time—for example, select a different node in the proxy group and retry the same URL. Don't rewrite the entire configuration to troubleshoot a single request.

If the browser works but other apps don't, check whether those apps support proxy settings and how their traffic enters the client. If nothing connects, disable traffic-routing features and check your basic network first. For deeper DNS and network stack issues, continue with the Troubleshooting category; there's no need to dig into complex settings during your first setup. Once one request that should use a proxy and one that should connect directly both behave as expected, keep your settings and consider the initial test complete.

After Setup: Update Your Subscription and Exit Safely

After your first successful connection, return to the subscription page and enable automatic updates if needed. You can use the update interval recommended by your provider; there's no need to refresh constantly. After an update, check that the same profile is still selected and that your chosen node hasn't been renamed or removed. A successful subscription update only confirms that the content was downloaded and parsed—it doesn't verify that every node works in practice.

For everyday use, follow the same checks: confirm the profile, mode, and proxy group. If something goes wrong, retry the same request and check its connection entry; that's usually more useful than repeatedly reinstalling the client. When asking for help, share your operating system, client name, the steps that triggered the error, and redacted logs. Hide subscription URLs, authentication details, and any connection history that isn't needed.

When you no longer need the proxy, disable the system proxy first. If TUN is enabled, turn it off too, then exit the client. This reduces the chance that leftover routing settings will disrupt your connection later. Once the basics are working, read the Technical Reference to learn about protocol differences and core compatibility, use the Glossary to look up a setting, or visit Frequently Asked Questions for common installation and connection issues.