Practical checklist

  1. 01

    Check the network in layers

    Check system time, profile update, node latency, DNS, system proxy and TUN in that order. Change one item at a time and retest immediately.

  2. 02

    Read logs instead of guessing

    Search for timeout, dns, permission and profile. The first reproducible error is usually more useful than the later cascade of failures.

  3. 03

    Keep a rollback path

    If an upgrade fails, restore the backup and previous version first. Changing version, subscription and DNS together makes the cause impossible to isolate.

  4. 04

    Verify real traffic

    Do not trust a green status alone. Load a page, test DNS, and confirm that closing the client restores the system proxy cleanly.

  5. 05

    Confirm the device and architecture

    Check the OS version and CPU architecture in system information. Most Windows PCs use x64; Apple M-series Macs use Apple Silicon; choose Universal on Android when uncertain.

  6. 06

    Record the current version

    Before an update or migration, note the client version and export local settings. Never place a subscription URL in a public screenshot, chat or ticket.

Done means

The build matches the device, the profile updates, page and DNS tests pass, and closing the client restores normal system networking.

Commonly missed

Do not change the client, subscription, node and DNS at once. One change at a time preserves the evidence.