Practical checklist

  1. 01

    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.

  2. 02

    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.

  3. 03

    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.

  4. 04

    Keep one network controller

    Quit the old client, browser proxy extensions and other VPNs. Two tools changing proxy or route settings often produce a connected status with no working traffic.

  5. 05

    Test with a minimal setup

    Update the imported profile, select one available node and enable only system proxy. Add TUN, scripts or overrides only after a browser test succeeds.

  6. 06

    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.

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.