Troubleshoot a connection

Work through these checks in order. After each change, retry the same app or website so you can tell what fixed the problem.

1. Open the dashboard and check the core status.
2. Confirm that a configuration is active. If you just imported one, open Profiles and subscriptions.
3. Open Logs and look for the first core or configuration error around the time it failed.
4. If the message names a missing field or unsupported option, check that the configuration matches the selected core. See Choose and manage a core, then ask the profile provider or author about compatibility.

1. Open Proxies, select the group used by your configuration, and choose an available node. Run the group’s delay test if one is available.
2. Check that the proxy mode is not Direct if you expect traffic to use a proxy.
3. Check the Connections and Rules pages while retrying the request. They can show whether the request reached the core and which rule handled it.
4. If the request is missing from both pages, confirm that System Proxy or TUN is enabled for the traffic you are testing.

Some applications ignore the operating system’s system proxy setting or use their own proxy configuration. See System Proxy and TUN to choose a mode that covers the application. Check the app’s own proxy settings before changing the global routing mode.

Check that the local file is a supported configuration, or that the remote URL is current and reachable. Some subscription services choose the response using the request’s User-Agent; if the downloaded file has no usable proxy nodes, ask the provider whether it supports Clash Nyanpasu. Never include the full subscription URL in a public report.

Follow the platform-specific steps in System Proxy and TUN. If the app reports that a service is missing or incompatible, open Settings and review the service status before reinstalling anything. Avoid changing core file ownership or permissions manually unless a current official guide specifically instructs you to do so.

Use Help → Collect Logs to gather diagnostics. Before sharing them, check for private domains, addresses, subscription URLs, tokens, or other account details and redact anything sensitive. Include your app version, operating system, selected core, the steps that reproduce the problem, and the first relevant error message.

If the checks above do not resolve the issue, search existing GitHub issues before opening a new report.