The short answer
This guide focuses on “A Practical Guide to mihomo Rule Providers”. Start by separating three layers: the client provides the interface, the mihomo core executes routing rules, and the network provider determines the real connection. Putting a problem in the correct layer makes configuration far easier.
For most people, stability matters more than the number of switches. Establish one working connection with the stable release and sensible defaults, then change one setting at a time and verify the result.
What to prepare
Download from the official GitHub project or a trusted portal and match the package to your operating system and processor. Export the current configuration before upgrading or migrating. Subscription URLs are secrets; never expose them in screenshots, forums or shared logs.
TUN mode, system services and auto-start may need administrator privileges. Managed work or school devices can restrict these features. Prefer the system proxy when appropriate and consult the administrator before changing security rules.
A reliable order of operations
First confirm that the client opens and the core reports a healthy state. Import an authorized configuration, select rule mode, and test one known-good endpoint. Check the browser, native applications and DNS separately. Enable TUN, automatic groups or sync only after the basic path works.
Always keep a rollback path. Know how to disable the system proxy, stop TUN and restore the previous profile. When something fails, return to the smallest working setup instead of toggling several unrelated options.
Common mistakes and diagnosis
A low latency score does not guarantee every site will be fast; it only measures a specific test endpoint. A successful subscription refresh does not prove that its endpoints work. Read the first concrete error in the log, then check time, network, firewall, DNS and syntax.
Do not leave certificate verification disabled or import unknown scripts as a shortcut. If only one application fails, it may ignore the system proxy, use private DNS, or require TUN to capture its traffic.
Security and maintenance
Keep both the client and mihomo on supported stable releases and read release notes before updating. Retain only necessary logs, protect backups, and regularly remove expired subscriptions, old profiles and unused service privileges.
System versions, client releases and networks differ. Treat this article as a durable workflow and use current project documentation when labels move. Finish by testing direct traffic, proxied traffic, DNS and behavior after a restart.