Clash Verge Rev needs a provider feed: paste a Clash/Meta URL, refresh nodes, then enable system proxy. Optimize for “works,” not screenshot tourism. Import alone does not create nodes—a successful update does.
Builds: download center; overview: getting started. Get the browser path working before you obsess over auto-update intervals.
Do this, not that
| Do | Don’t |
|---|---|
| Paste a Clash Meta / Mihomo-compatible URL | Paste a Sing-box-only or marketing-page URL |
| Update immediately after import | Rely on import alone to create nodes |
| Name cards clearly (main/backup/date) | Hammer auto-update retries |
| Prefer one manual refresh before auto-update | Enable update-via-proxy with zero nodes |
Import, refresh, auto-update
New profile → paste URL → save → update immediately. Auto intervals shouldn’t hammer retries (CPU/RAM). Name cards clearly (main/backup/date). Prefer one manual successful refresh before enabling auto-update.
“Update via proxy” only when the feed host needs a proxy and you already have a working node—otherwise use a hotspot or backup URL. With zero nodes, update-via-proxy has nothing reliable to exit through.
Before pasting, confirm the URL isn’t truncated by chat apps and doesn’t include stray spaces. If the provider offers Clash, Clash Meta, and Sing-box links, prefer Clash Meta / Mihomo-compatible feeds for this client.
Imported but no nodes
Go to no nodes. Check Clash/Meta format, plan status, and filters. Failures with errors: update failed. Prefer remote URLs daily; local files only when provided—don’t mix unclear sources.
Panel shows nodes but the client card stays at 0: HTML/login responses, empty CDN payloads, or filters wiping the list. Disable filters for a comparison, and see blank groups when the total count is non-zero but a group looks empty.
Five-step acceptance
- Node count > 0 with a fresh update time.
- Latency not all timeout (latency); a few reds are fine, an all-dead group is not.
- System proxy shows connections for the site you just opened (empty Connections → system proxy).
- Tun/AI only if needed (Tun & AI).
- Back up URL + Merge (backup).
Multi-device / household
Import per device—paths, permissions, and service mode differ across machines. Shared plans: watch quotas. Choosing providers: choose a provider.
Keep work and personal profiles separate when you can, so office domains and personal routing policies don’t collide.
Don’t stack failures
Don’t change URL, UA, Tun, and reinstall together. Change one variable at a time. Updates OK but everything times out → nodes/network (slow speed).
When stuck, write down three facts: update success/error, node count, and whether Connections shows rows—then choose backup URL, network change, or provider support instead of blind reinstalls.