Disclaimer

1. About This Site and Its Services

This site is a guide to the official Clash website, published under the Clash Tutorial Hub name. It provides client setup guides, download links, and configuration troubleshooting resources. Guides cover mihomo and various graphical clients, including installation, subscription imports, traffic rules, and DNS settings.

Download links do not provide proxy nodes, subscription accounts, or network access. Each software project has its own license, terms of use, and maintenance schedule. Our guides do not replace a project's license or guarantee how long it will be maintained.

2. Software Installation and Configuration Risks

Check that the software and instructions are compatible with your operating system, processor architecture, and network environment. Installing or updating software, switching cores, or importing a configuration may interrupt your connection, cause port conflicts or app connectivity issues, or overwrite existing settings. Back up a working configuration first, and keep instructions for restoring your system proxy, DNS, and routing settings.

Before enabling TUN, service mode, or LAN access, understand the required permissions and listening address. Never expose a management interface directly to the public internet or import scripts or configurations from unknown sources. Keep subscription URLs, node credentials, and sensitive log data secure, and remove them before sharing troubleshooting materials.

Losses caused by a user's device environment, conflicts with third-party software, incorrect configuration, or exposed credentials are the responsibility of the relevant parties under applicable law. We do not guarantee that software will work on every device or in every scenario. Nothing in this disclaimer excludes liability that cannot legally be excluded.

3. Guide Accuracy and Version Differences

Guides reflect the software versions and reproducible environments available when they were written or last revised. Client interfaces, menu names, default ports, configuration fields, and permission requirements may change between versions. Support for the same field may also vary by core. Examples explain how settings work and should not be treated as complete configurations suitable for every subscription.

Before applying an example, check your client, core type, and runtime logs. If the interface or messages differ from the guide, pause bulk changes and consult the documentation for your version. We correct issues we find, but cannot guarantee that every page will reflect upstream changes immediately or that a troubleshooting step will resolve a particular issue.

4. External Links and Third-Party Services

Pages may link to app stores, software project websites, or other reference materials. The operators of those external pages control their content, availability, pricing, and data handling practices, which may change without notice to us. A link on this site does not endorse or guarantee all external content or service quality.

After leaving this site, verify the destination address and the permissions requested. Before registering, paying, purchasing a subscription, or submitting personal information, read the destination service's terms. Direct disputes about third-party services to their operators. Our instructions do not guarantee transaction outcomes or connection quality.

5. Lawful Use and Getting Help

Follow the laws that apply where you live, your organization's network policies, and the terms of relevant services. Rules, commands, and network settings in these guides are for lawful network administration, development testing, and technical learning. They do not authorize bypassing access controls or infringing anyone's rights.

For configuration issues, start with Frequently Asked Questions or check the steps in the quick-start guide. For platform-specific installation differences, see the cross-platform guide. When reporting an issue, note the client name, operating system version, and error message. Test changes on a backed-up configuration, and avoid changing multiple settings at once so you can identify the cause.