Clash Verge logo Clash VergeOpen-source cross-platform proxy client

Troubleshooting

Clash Verge Error Reference

Published · Updated · 2 min read

Bookmark this page. Left column: what you see. Right column: why, and the fix — with the detailed guide linked when the topic deserves one.

Most errors have fixed causes — look them up instead of reinstalling
Most errors have fixed causes — look them up instead of reinstalling

Startup and interface

Symptom / errorCause and fix
Blank / white windowWebView2 runtime missing or broken. Install the Evergreen runtime or use the fixed_webview2 installer — Windows guide
SmartScreen "Windows protected your PC"Normal for unsigned open-source builds: More info → Run anyway. Valid only for official downloads — verify the source
macOS "damaged, can't be opened"Gatekeeper quarantine flag; remove with xattr — macOS guide
Doesn't start with the systemStartup entry disabled by the OS or a security suite — autostart guide

Core and config

Symptom / errorCause and fix
Port xxxx is already in useAnother process owns the port — port conflicts
yaml: unmarshal errors / profile won't loadYAML syntax error, usually Merge indentation — extend config
unsupported proxy typeCore too old for a new protocol — switch/upgrade core
rule-provider ... initial errorRule set fetch failed or wrong behavior type — rule providers
Core crash-loopingSwitch to the stable core first; if it persists, empty Merge/Script and bisect

Network features

Symptom / errorCause and fix
TUN switch grey / errors on enableService mode missing or broken — service fix
Subscription 401/403/timeoutExpired token or blocked domain — subscription guide
Proxy on, nothing loadsFive-step diagnosis — full checklist
Store (UWP) apps offlineLoopback restriction — UWP exemption
Tip

Error not listed? Copy the raw message from the Logs page into the GitHub repo's issue search — odds are someone already solved it.

Don't have Clash Verge yet?

Windows 64-bit installer · v2.5.1 · free & open source

Download v2.5.1