Clash Verge Offline After Sleep/Wake: Fix the Wake Hangover

Close the lid, sleep a while, open again—and Clash Verge Rev’s most common hangover is: tray icon still there, browser offline; system proxy shows green, Connections stops moving; worse, Tun is fake-alive until you fully quit the client. That is not always an expired subscription. More often the network stack, virtual NIC, or system-proxy state did not reattach cleanly after wake.

Startup issues: startup proxy. Tun: Tun mode. Service: Windows Service Mode. Builds: download center. Here: how to tell wake vs nodes, light-to-heavy recovery, Tun / service / Fast Startup habits, and when to stop resetting configs.

Wake problem or node problem?

Right after wake, test three things: (1) with system proxy / Tun off, does direct access recover; (2) with proxy on, do new Connections rows appear; (3) does switching one node help immediately. Direct OK but zero Connections rows → treat as wake / service / NIC. Rows exist but all fail → nodes or DNS (DNS, proxy on but sites fail).

Only after sleep, cold boot fine → power-state related, not "the airport dies at night." Write that into your notes; it prevents pointless resets. Do not flip modes to paper over it—confirm Rule is still selected: three modes.

Light-to-heavy recovery

1. Fully quit and reopen the client (not just the tray icon). Wait a few seconds for the core, then enable system proxy.
2. If you use Tun: disable Tun, confirm system proxy works, re-enable Tun. Still failing → verify the service is running (Service Mode).
3. Confirm mixed port still matches Settings; clear stale OS proxy digits (mixed port, system proxy).
4. Restart Clash-related services, or disable/enable the physical NIC / Wi‑Fi.
5. Still broken → reboot Windows. Note "only reboot fixes it," then target Fast Startup or sleep policy.

Do not reset everything first—wake faults rarely need wiping subscriptions. If you must clean, use a safe reset with backups. Port fights: port conflict.

Tun, Service Mode, and Fast Startup

Tun depends on a virtual NIC and the service. Sleep suspends the NIC; on wake the driver may lag while the GUI still thinks Tun is on. Connections freezes; apps look "proxied but offline." Fix: Tun off → service Running → Tun on. Recurring cases: reinstall the service and avoid stacking other VPNs. Tun will not start: Tun start failed.

Windows Fast Startup makes "shut down" closer to hybrid sleep; some drivers wake dirtier. If every cold "shut down then power on" still looks like a wake fault, disable Fast Startup in power options for an A/B test. High usage: CPU/memory. Communication failures: core communication. Half-finished in-app updates can look worse after wake: app update failed.

Habits that cut recurrence

• Before closing the lid during big downloads or Tun games, stop Tun or quit the client to avoid half-states.
• After wake, give the core 3–10 seconds before opening the browser; early hits look like "it’s broken."
• Tray "online" is not proof—Connections and real pages are.
• Aggressive corporate sleep policies: keep Service Mode healthy before stacking more startup items.
• Same day, compare "sleep 5 minutes" vs longer hibernate: only long sleeps fail → driver resume; both fail → service and stale system proxy first.

Acceptance—and when not to reset

Accept when: after wake, quit/reopen restores system proxy; Tun can toggle with Connections rows; direct fallback still works. If only cold boot is healthy and every wake needs a full reboot, log the OS build and fix service / drivers / Fast Startup—do not reinstall the client daily or wipe subscriptions. A short desk test helps: sleep five minutes on AC power, then again on battery. Different outcomes often point at power-plan NIC suspend, not at the airport.

If quit/reopen fixes it three times in one week, treat that as the standard move; do not escalate to reset. Only enter safe reset when the profile itself is tangled and ports/modes no longer stick. Keep a one-line log—wake time, Tun on/off, whether Connections moved—so the next failure is comparable. Index: common errors. Packages still from the download center.

Wake vs node—quick decide