Clash Dashboard Guide: Visual Proxy Management

What Can a Dashboard Do?

When the Clash core is running, it exposes a RESTful API. The Web Dashboard is a graphical management interface built on top of that API. Compared to clicking through nodes in a desktop client, the dashboard provides richer information and more powerful controls – making it especially useful for advanced users who need to diagnose issues or fine-tune their configuration.

With a dashboard, you can:

• Graphically switch nodes, view the currently selected node for each proxy group, and check latency at a glance;
• Run one-click speed tests to compare performance across all nodes intuitively;
• Monitor the live connection list (domain, destination, matched rule, and traffic);
• View the running log to pinpoint connection failures and rule-matching anomalies;
• Edit parts of the configuration online (depending on the dashboard; MetaCubeXD, for example, supports rule editing).

Most modern Clash clients (such as Clash Verge Rev and Clash Meta for Android) include a built-in dashboard entry point. You can also use a standalone web dashboard that connects via the API.

Enabling the External Controller

The dashboard communicates with the Clash core through the external-controller interface. You need to enable it in your configuration file:

127.0.0.1:9090 means the interface is accessible only from the local machine, which is appropriate for local dashboard connections. secret is the API access key that dashboards must supply when connecting; it prevents unauthorized access. If no secret is set, any process that can reach the port has full control over Clash – a significant security risk.

After making changes, reload the configuration. Clients like Clash Verge Rev typically provide an "External Controller" toggle in their settings that writes the config automatically, so you do not need to edit the YAML by hand.

Popular Web Dashboards

Yacd / Yacd-meta

The classic lightweight dashboard with a clean interface, compatible with both Clash and Clash Meta. Supports node switching, speed tests, connection monitoring, and rule display. Can be used as a hosted online version (e.g., yacd.haishan.me) or downloaded locally and opened in a browser, then connected to local Clash via the API address.

MetaCubeXD

Optimized specifically for the Clash Meta core, with a complete feature set and modern UI. Supports connection details, rule editing, configuration management, and log filtering. Clash Verge Rev's built-in dashboard is based on MetaCubeXD and offers a smooth experience.

Zashboard

A newer dashboard project with excellent interaction design, rich information display, and dark mode support. Well suited for users who prefer a modern UI; it also connects via external-controller.

Choosing a dashboard comes down to personal preference and client integration. If you use Clash Verge Rev, simply click the "Dashboard" button – no extra configuration needed. Yacd-meta suits users who prefer a lightweight online interface, while MetaCubeXD and Zashboard are better for advanced users who need deep connection diagnostics. Try a few and stick with whichever feels most comfortable; there is no single "best" option.

Connecting to the Dashboard

1. Confirm that Clash is running and that external-controller is enabled in the config.
2. Open the dashboard (via the client's built-in entry, or by navigating to the dashboard's online or local URL).
3. In the connection settings, enter the API address, e.g. 127.0.0.1:9090 or http://127.0.0.1:9090.
4. If a secret is configured, enter the same value in the secret field.
5. Click Connect. Once connected, you can speed-test and switch nodes on the Proxies page, and inspect live connections on the Connections page.

If the connection fails, check: Is Clash actually running? Is the port already occupied by another process? Is a firewall blocking it? Does the secret match? On Android, if the dashboard and Clash are on different devices, change external-controller to 0.0.0.0:9090, ensure both devices are on the same local network, and always set a strong secret.

Key Dashboard Features

Proxies Page

Displays all proxy groups and the nodes within each group. You can click to switch nodes or run batch speed tests. url-test groups show the currently selected node and its latency, making it easy to verify that the automatic strategy is working correctly.

Connections Page

Lists all active connections, including source address, destination domain/IP, matched rule, node in use, and upload/download traffic. Extremely useful for diagnosing "which rule did this site match?" or "which node is being used for this connection?"

Rules Page

Some dashboards (such as MetaCubeXD) provide a rule list view showing all currently loaded rules in their matching order. When troubleshooting why a domain is going direct, cross-referencing the matched rule shown on the Connections page against the Rules page lets you quickly identify whether the problem is rule ordering or an outdated rule set. Mastering this feature can drastically reduce the time spent blindly editing config files.

Security Considerations

The external-controller interface has full authority to control Clash, including switching nodes, modifying the configuration, and viewing all connections. If exposed to the internet without authentication, it can be exploited maliciously.

For everyday use, keep the binding set to 127.0.0.1 – local-only access is both safe and simple.

Mobile and Remote Access

The Android version of Clash Meta typically includes a simplified built-in panel for switching nodes directly within the app. If you want to manage Clash on your phone from a PC browser, set the phone's external-controller to a LAN address (e.g., 0.0.0.0:9090), then access http://<phone-IP>:9090 from the PC and supply the secret. Only do this on a trusted local network – never expose the control interface to the public internet.

Desktop clients like Clash Verge Rev open their dashboard locally with no extra network configuration required, making them the most convenient option. Advanced users can deploy a dashboard on a NAS or VPS and access it securely via Tailscale or WireGuard. Regardless of the approach, always prioritize security and avoid exposing the control interface to untrusted networks.

Troubleshooting Tips

If you cannot connect to the dashboard, start by running curl http://127.0.0.1:9090 in a terminal to test whether the API is responding. A 401 response means a secret is required. A "connection refused" error means Clash is either not running or using a different port. Large numbers of DNS or rule-related errors in the Logs page usually indicate a configuration syntax issue – review the documentation and check each setting systematically. Making it a habit to regularly review the Connections and Logs pages lets you catch and resolve problems before they escalate, keeping Clash transparent and under control.

Summary

The web dashboard transforms command-line proxy management into an intuitive graphical experience, making speed testing, node switching, and troubleshooting significantly more efficient. The setup is straightforward: enable external-controller, set a secret, and connect your preferred dashboard. For everyday use, the built-in dashboard in your client is the most convenient option; for in-depth diagnostics, the Connections and Logs pages are indispensable tools for pinpointing routing and connectivity issues. Always protect your API with proper access controls to avoid the risks that come with an exposed interface. Once you are familiar with what each dashboard page offers, your Clash management efficiency will improve noticeably – many operations that previously required editing config files can be done with a single click. The dashboard is the bridge between you and the Clash core, and it is well worth investing time to learn all of its features.