Material checked on 2026-11-14. Error strings are quoted verbatim so you can match them against your own log.
What the error actually tells you
set system dns failed: exit code 1 means Clash Verge Rev did not succeed at the step where it modifies the system DNS configuration. It does not prove that the subscription, the nodes or the Mihomo configuration are broken, and it does not follow that swapping in 1.1.1.1 will fix it.
Two things have to be established before you change any setting: whether the failure sits in the system proxy path, in the TUN path, or in basic networking underneath both; and whether another tool that also takes over networking is running at the same time.
The one public case that names this error is Clash Verge Rev issue #8328: macOS 27.0.1, Clash Verge Rev 2.5.8, configuration validation succeeded, and the error appeared when enabling the system proxy. The reporter then pointed at a Tailscale/WireGuard type conflict, and a project collaborator noted that Mihomo supports WireGuard and Tailscale outbounds directly. The issue was closed on 2026-10-17. It is one case on one platform — it does not establish that every error with this string comes from Tailscale.
Route by symptom before anything else
| What you see | More likely stage | Do this first | Do not do this |
|---|---|---|---|
Validation succeeds, then set system dns failed: exit code 1 | System DNS write, or a network-takeover conflict | Record OS, client version, and every VPN or virtual adapter running | Do not delete the subscription |
| System proxy fails but TUN still works | System proxy and DNS write path | Turn TUN off, build a direct baseline, reproduce system proxy alone | Do not treat working TUN as proof that DNS recovered |
| No connectivity only after enabling TUN | TUN service, routing, or DNS takeover | Switch to a TUN-specific checklist | Do not apply the system-proxy conclusions here |
| Name resolution fails even with direct connection | OS, router, ISP or managed-network DNS | Restore ordinary networking first | Do not stack more client settings on top |
| Only one site will not open | Site-specific DNS, certificate, region or account policy | Compare against another domain and a resolver query | Do not reset the whole device network |
Step 1 — Capture the first error and the reproduction conditions
Record these before you touch anything:
- Full Clash Verge Rev version, OS name and version.
- Whether the error appears when enabling the system proxy, enabling TUN, switching profiles, or starting the app.
- Whether configuration validation succeeded, and the first
ERRORline before the failure. - Whether Tailscale, WireGuard, another VPN, a network filter or corporate security software is running.
- Whether ordinary networking and name resolution come back after you close Clash Verge Rev.
Redact subscription URLs, tokens, node addresses, UUIDs, usernames, device names and your real public IP before posting a log or a screenshot. Do not upload a full configuration file just to report an error.
Step 2 — Build a baseline that does not pass through the proxy
- Turn off both TUN and the system proxy in Clash Verge Rev.
- Quit the client normally. Do not leave a second proxy client running.
- Before pausing another VPN or virtual network tool, confirm what it is for and how to bring it back. On a company-managed device, do not remove it yourself.
- Confirm that ordinary HTTPS sites and name resolution work on a direct connection.
- Reopen Clash Verge Rev and enable only the system proxy. Watch whether the same error returns.
If name resolution is broken even on a direct connection, fix basic networking first; this page does not apply yet. Avoid one-click network-reset scripts of unknown origin, and do not delete system network services blindly.
Step 3 — Look for duplicate network takeover
Issue #8328 points at Tailscale/WireGuard type tools, but that is single-case evidence. Check each of these:
- Is another VPN connection still listed in the menu bar or system settings?
- Are Tailscale, WireGuard, ZeroTier, a corporate VPN, a packet filter or security software installed?
- Is a background service or network extension from an older proxy client still present?
- Are Wi-Fi, Ethernet and virtual interfaces being given DNS settings by different programs at the same time?
Pause one known tool at a time, then repeat the same action. Once a conflict is confirmed, decide which tool you actually need — do not uninstall a corporate VPN that your work depends on just to make Clash Verge Rev start. WireGuard and Tailscale outbounds inside Mihomo are an advanced setup; never paste a configuration you found online into a private subscription.
Step 4 — Test system proxy, TUN and DNS separately
The system proxy and TUN are different takeover paths, so they have to be tested in isolation:
- Enable only the system proxy. Check that the core is running and that the browser honours the system proxy.
- Then test TUN on its own. Do not change the subscription, the rules and the DNS settings in the same attempt.
- If the system proxy throws
set system dns failedwhile TUN works, still record that the system DNS write failed. Do not write it up as "resolved". - If the system proxy enables cleanly but names still fail, compare the OS resolver output with the client log, then move to a general DNS checklist.
- If only TUN fails, use a TUN-specific checklist instead of this page.
The Mihomo DNS documentation lists separate fields for default-nameserver, nameserver, proxy-server-nameserver, respect-rules and Fake-IP. Their existence shows that the DNS chain has several layers; it does not prove that any one field is the cause of your exit code 1. If you do not know the override order of your subscription, do not replace an entire DNS block in one edit.
Step 5 — Safe recovery and stop conditions
- Change one variable per attempt, and keep the error text from before and after.
- To exit: disable TUN first, then the system proxy, then quit the client normally.
- Restore the system's original automatic DNS or the administrator-assigned settings, then verify a direct connection.
- Install the client only from the official Clash Verge Rev project and its Releases page.
- If the error reproduces reliably, report OS version, client version, the action that triggers it, the first error line, and a redacted log.
- Stop and escalate if the device is managed, if an unknown network extension is involved, or if administrator rights are needed.
Sources and evidence boundary
- Clash Verge Rev issue #8328 — one macOS 27.0.1 / 2.5.8 case; validation succeeded, then the system DNS write failed, and the discussion points at Tailscale/WireGuard type conflicts. Closed 2026-10-17.
- Mihomo DNS configuration reference — used only to show that the DNS configuration has multiple layers, not to claim that one field fixes every
exit code 1. - Clash Verge Rev official project — used to check the project, issue and release entry points.
This page assembles a diagnostic order from public material. It was not reproduced across every macOS, Windows, Linux, VPN and network-extension combination, and it does not promote a single closed issue into a universal cause.
Frequently asked questions
Does this error mean my nodes are broken?
No. In issue #8328 the system DNS error appears only after configuration validation succeeds, so the failure happens earlier than any judgement about node health. Test the nodes separately once connectivity is restored.
Can I just set the DNS to 1.1.1.1 or 8.8.8.8?
Not as a general answer. The conflict may sit in a system network extension, another VPN, the TUN path, or the client's override layer. Swapping resolvers can mask the problem and may also break a corporate network requirement.
TUN works, so do I still need to fix the system proxy error?
Yes — record it and treat it separately. Working TUN only shows that a different takeover path happens to function; it does not mean the system DNS write succeeded.
Must I uninstall Tailscale or WireGuard?
Not necessarily. First confirm that the conflict reproduces and decide which tool you actually need. On a managed device or a work VPN, hand this to your administrator instead of uninstalling based on one public case.
Will reinstalling Clash Verge Rev fix it?
There is no evidence that guarantees it. If the conflict comes from another network extension or from system policy, reinstalling the client does not remove the conflict. Keep the log and finish a single-variable comparison first.
What should I include when I open an issue?
OS version, Clash Verge Rev version, the exact action that triggers it, the configuration validation result, the first error line, whether another VPN was running, and the minimum redacted log. Never include subscription URLs, node credentials or your real IP.
Continue reading
Invalid YAML when importing a remote profile · Full error string index