Clash Nyanpasu
Subscription Import and Connection Guide

Before you begin

Prepare the client and a valid subscription URL

Before starting setup, confirm that Clash Nyanpasu is installed and opens normally. On the first Windows launch, if the system shows a firewall access prompt, decide whether to allow access on private networks based on how you use the network. If macOS blocks the first launch, approve it under System Settings > Privacy & Security. Linux users should complete installation according to the package format and make sure the current account can launch the client. Do not enable the system proxy yet; leave the client without traffic takeover so later troubleshooting is clearer.

Next, obtain a valid subscription URL generated by the service provider you use. It is usually a complete link beginning with https://, which lets the client retrieve proxy nodes, strategy groups, routing rules, DNS settings, and other configuration. Copy the URL from your service management page. Do not remove parameters manually or mistake an ordinary login page URL for a subscription URL. After copying, you can paste it into a local text editor to check for extra spaces or line breaks at either end, but do not share it publicly because subscription URLs are often linked to your account.

If you only have a single proxy protocol link rather than a Clash configuration subscription, whether it can be imported directly depends on the client and configuration format. For a first setup, it is better to obtain a Clash- or Mihomo-compatible subscription so strategy groups and rules load with the configuration. You can review the glossary after setup for nodes, strategy groups, rule modes, DNS, and TUN. For now, just confirm that the client opens, the subscription URL is complete, and the underlying network is working.

Step 1

Import the subscription and make it active

Open Clash Nyanpasu and select Subscription in the left navigation. Some versions label this page Configuration or Profiles; the function is the same: managing remote subscriptions and local configurations. Find Add, New, or the plus button in the upper-right corner, then choose Import from URL. You will usually see fields for a name and an address. Enter a label you can recognize, paste the complete subscription link you prepared into the address field, confirm it has not been truncated, and click Save, Import, or Submit.

The client will request the subscription content. Normally, the new configuration appears in the subscription list after a few seconds, along with its name, an update action, or an options menu. A successful import does not mean the configuration is active yet. Click its card, select it, or use Set as Active so it becomes the configuration currently loaded by the client. After that, the Proxy page should show the strategy groups supplied by the configuration, and the Rules page will usually show rule entries. Strategy group names are chosen by the provider, so they may not match names used in other guides.

If the list is still empty after saving, do not keep adding the same subscription repeatedly. Return to the input field and check that you did not copy a page title, leading or trailing spaces, or line breaks, then try the update button on the subscription card. For network errors, timeouts, or parsing failures, confirm that the subscription link is still valid on the current network and check whether the service management page requires a new link. If the subscription returns a login page, the client cannot recognize it as a configuration. Content that is not Clash-compatible will also fail to parse. See Troubleshooting for a fuller diagnosis workflow; for this guide, the step is complete when the configuration appears in the list and can be selected.

Step 2

Choose Rule mode and understand the traffic scope

After loading the configuration, find the Mode option on the client’s home or Proxy page. Common choices are Rule, Global, and Direct. Rule mode is recommended for first-time setup: the client reads the rules in the active configuration to decide whether a domain or connection should use the proxy, connect directly, or follow another strategy. This sends proxy-required requests to strategy groups while keeping suitable services on their normal direct route, making it the most common choice for everyday use.

Global mode sends most traffic that the client can intercept through the selected proxy strategy. It is useful for briefly testing whether rules are preventing a site from loading. If a site fails in Rule mode but works in Global mode, the issue is more likely related to rule matching, DNS, or strategy selection than to a complete lack of connectivity. Global mode does not mean the connection will always be faster; it simply reduces routing decisions. Direct mode bypasses the proxy and is typically used to pause proxying, compare results on the original network, or determine whether a problem is related to the proxy path.

Once the mode is selected, open the Proxy page. The entries shown there are not necessarily individual nodes; the top-level items are often strategy groups such as Node Selection, Auto Select, or groups organized by service. Expand the group handling most of your traffic and choose an currently available entry. If the configuration provides an auto-select group, start with that. If selection is manual, choose an entry suitable for your network route. Avoid changing the mode, strategy group, and system proxy toggle repeatedly at the same time, or it will be difficult to tell which change affected the result.

A reliable first-time sequence is: keep Rule mode enabled, select the main strategy group, then move to the next step and enable the system proxy. If verification fails, change only one condition at a time—for example, switch strategies first, then test Global mode, and check DNS or TUN last. See the glossary for details on rule matching, strategy group types, and names such as url-test and fallback. For now, there is no need to edit the configuration file or adjust advanced parameters.

Step 3

Enable the system proxy or use TUN mode when needed

Return to the Clash Nyanpasu home or Settings page and turn on the System Proxy toggle. The client will point the system proxy address to the Clash port listening on the local machine. Browsers and desktop apps that follow system proxy settings will normally use the connection immediately. On Windows and macOS, you generally do not need to enter proxy details manually in the browser. If a browser extension controls the proxy independently, it may override the system setting, so let the browser follow the system proxy during the first verification.

After enabling the toggle, keep the client running; do not immediately quit to the tray and end the process. The system proxy only tells apps to send requests to the local client. Clash Nyanpasu still handles rule matching and forwarding. If the client exits while the system proxy remains enabled, the browser may fail because no process is listening on the local port. A normal client exit usually restores the system proxy, but turning it off first and then quitting the program makes the current network state easier to understand.

Some games, command-line tools, store apps, and software with its own networking stack do not read the system proxy. The browser may work while these apps continue using the original network. To intercept this traffic, use TUN mode. TUN creates a virtual network interface that sends more TCP, UDP, and DNS requests through the client. The first launch may require administrator permission on Windows, a network extension approval on macOS, or VPN confirmation on mobile devices. Follow the system prompts, then check that the toggle stays on. If it switches back off, permissions, the driver, or virtual interface initialization may not have completed.

The system proxy and TUN do not have to be enabled together. If you mainly use a browser and standard desktop apps, start with the system proxy because it is simpler and easier to troubleshoot. Use or add TUN when you need to cover apps that ignore system proxy settings. Do not enable every networking option at once simply to be “more thorough” before basic connectivity is verified; TUN, DNS hijacking, and routing settings add more variables. See Troubleshooting for TUN startup failures, leftover system proxy settings, and port conflicts.

Step 4

Verify using access results and connection logs

Keep the client running, close any previously opened tabs for the target site, and open a new browser window. Reopening the site reduces the effect of old connections, caches, and browser sessions. First visit a site that normally works without a proxy to confirm that the system proxy has not interrupted basic connectivity. Then visit the target site that requires the proxy. If both load normally, the basic connection and rule routing are generally working.

A loaded webpage is only the first check. Return to Clash Nyanpasu and open the Connections or Logs page. Refresh the target site and look for a new request record showing the matching rule or strategy. Log formats vary by version, but the key indicators are the same: a new connection means the app’s traffic reached the client; a Direct or proxy strategy result means the rules made a decision; no new record usually means the browser is not following the system proxy, a proxy extension has overridden it, or the request is reusing an existing connection.

If the page does not load but the Connections list shows a request, keep the mode unchanged and try another available entry in the main strategy group. If it still fails, briefly switch to Global mode for comparison. If Global works while Rule mode fails, investigate rules or DNS. If both modes fail, first check whether the subscription is valid, the selected strategy is available, and the local network is blocking the connection. Switch back to Rule mode after testing so a temporary troubleshooting state does not become your everyday configuration.

If the browser works but other apps show no change, first determine whether those apps read the system proxy. For apps that do not, use their own proxy settings or return to the previous section and enable TUN. If enabling TUN affects all network access, disable it first to restore basic connectivity, then check permissions, DNS, and the virtual interface one at a time. Reinstalling the client repeatedly is not recommended because it usually does not fix subscription formats, strategy selection, or application proxy coverage. Layered symptom-based checks are faster; see Clash Troubleshooting for the full workflow.