Clash Verge Rev troubleshooting center: isolate faults by symptom

Start with this decision order

Troubleshooting is not trying every switch. Record the symptom and narrow it across application, configuration, system, network, and external-service layers while preserving useful evidence.

1. Record the exact symptom and time
2. Confirm version, system, and active configuration
3. Read the first explicit log error
4. Change one variable and retest
5. Keep the success or failure result
6. Clean temporary settings only after recovery

Installation or startup failure

Close old instances, back up required configuration, and confirm disk space and system time. Before an upgrade, record the old version and data path so a program change can be separated from a configuration change.

Import, sign-in, or configuration failure

Import one known-good configuration, select an available endpoint or policy group, and enable the system proxy. Evaluate TUN only for applications that do not honor the system proxy.

Status looks normal but the feature fails

If the client says connected but traffic fails, check active configuration, endpoint health, system proxy, DNS, and TUN in that order. Change one layer at a time and preserve the original log error.

Only some applications or features fail

Complete one working loop on defaults, then change TUN, DNS, rule overrides, background behavior, or autostart one at a time. Record each result so the last change can be reversed.

Read logs and ask for help safely

Test one explicit outcome: the app opens, configuration loads, the required feature is enabled, and real behavior matches the status. A colored button alone is not evidence; compare logs and the target application.

Updates, backup, and rollback

Back up before updating. Afterward, check app and core versions before reusing configuration. Preserve logs and return to the last known-good state instead of deleting all data.

Security and privacy

Subscription URLs, recovery phrases, private keys, credentials, and debug logs may contain secrets. Redact them before screenshots or support requests and never paste them into unknown checkers.

Related pages