Discord Update Stuck at 0% on Windows? Split CDN and RTC Traffic in Clash

1. Symptoms that point to split routing, not “Discord is down”

Outage trackers spike whenever Discord hiccups globally, yet many Windows tickets are local pathologies. Listen for asymmetry: text channels hydrate, GIF previews load, yet the in-app updater never advances past zero percent, or voice works in direct messages but degrades in crowded servers. Another pattern is TLS or HTTP stalls that appear only after you switch to a strict domestic-direct subscription, because a geo rule snagged a CDN hostname the updater still needs on the same exit as the REST gateway.

Voice adds a second axis. Users describe robotic audio, twenty-second reconnect loops, or disconnects when screen sharing starts. Those issues correlate with UDP-heavy voice RTC paths, MTU friction on certain tunnels, or nodes that reorder packets aggressively. Before you blame Discord’s voice region, confirm whether the failure tracks a profile swap rather than a Discord status page.

If YAML still feels opaque, skim our subscription import tutorial so you know where provider bundles end and where your personal rule section should live. The rest of this article assumes you can append suffix rules without breaking schema validation.

2. A Windows-first checklist before you rotate nodes

Changing exit nodes feels decisive, yet it wastes time when Update.exe or Discord.exe never hit Clash in the first place. Work through this sequence while watching your client’s live connection view.

1. Decide whether you are in system proxy mode or TUN mode, then confirm the Discord processes actually inherit that path. Some security suites strip OS proxy flags for selected binaries.
2. Reproduce the stuck updater or flaky voice session, then read the policy column per hostname in the log. Stray DIRECT rows next to proxied Discord hosts are the usual culprit for HTTPS shells; missing UDP visibility points to TUN or driver issues for voice RTC.
3. Audit DNS: upstream reachability, fake-ip expectations, and whether campus or corporate resolvers special-case Discord domains.
4. Expand CDN split routing to cover updater hosts, gateway APIs, static delivery, and any redirectors you observe—not only discord.com.
5. After routing is coherent, pick a stable node for long-lived voice sessions and avoid ultra-aggressive auto failover that reconnects mid-call.

For port collisions, invalid rules, and core startup failures, keep the general Clash troubleshooting guide open. Here we focus on multi-endpoint desktop clients where one missing CDN suffix mimics a platform outage.

3. Why Discord breaks when only the “main” domain is proxied

Discord deliberately separates concerns. The Chromium-derived shell talks to gateway and REST endpoints, while attachments and installer payloads often ride high-volume CDNs. A minimal profile that proxies discord.com but leaves a static delivery hostname on DIRECT can still strand the updater if that hostname is unreachable on the direct path your ISP offers.

Voice complicates the graph because interactive media is sensitive to jitter and packet loss, not just raw download throughput. A rule that forces aggressive domestic-direct behavior for “generic CDN” patterns may still be wrong for Discord if the same provider edge serves both static objects and authenticated fetches your client expects to co-locate on one exit.

Updater failures exaggerate the mismatch. The Windows client may download a large blob from a hostname class that your subscription labels differently from the small JSON calls that gate version checks. Users perceive that as Discord update fail behavior even when partial traffic still moves—another hint that policy selection is inconsistent rather than universally blocked.

4. System proxy versus TUN for Discord on Windows

System proxy is the lighter-touch option when Windows honors the OS proxy and Discord’s networking stack respects it for HTTPS. The familiar failure mode mirrors browsers: the primary document succeeds, yet secondary hosts bypass the proxy, leaving embedded views or updater widgets empty.

TUN mode pushes routing deeper so fewer executables can silently skirt Clash. That matters twice for Discord. First, it reduces stray TCP flows that never appeared in the proxy log. Second, many voice RTC implementations rely on UDP; a pure HTTP CONNECT proxy on localhost does not magically carry UDP the same way a routed tunnel can. If you already walked through our TUN mode guide, repeat the experiment while sorting connections for Discord process names. TUN is not mandatory for everyone, but it is the right lever when evidence shows voice disconnects correlate with UDP taking a different path than HTTPS.

Regardless of mode, confirm the GUI is using the profile you edited. Editing one YAML while another snapshot remains selected manufactures phantom regressions that have nothing to do with Discord’s infrastructure.

5. DNS, fake-ip, and resolver conflicts for Discord

Clash’s fake-ip mode answers quickly with synthetic addresses, yet it tightly couples DNS to rule evaluation. When the resolver and the rule engine disagree about what a Discord hostname “means,” you can observe TLS retries, stalled embeds, and updater panes that never leave the loading state.

A practical mitigation has two parts. First, ensure upstream DNS servers are reachable through the policy path you expect for general browsing, and avoid resolver chains that intermittently drop international queries. Second, consider targeted policies—commonly nameserver-policy in Mihomo-compatible cores—for suffixes you see repeatedly in Discord traffic. Always verify keys against the documentation bundled with your exact core build instead of copying aged forum snippets.

When DNS fixes clear most symptoms without changing proxy groups, you have strong evidence the bottleneck was resolution, not bandwidth. That distinction tells you whether to invest in resolver hygiene or in node stability next.

6. How to collect Discord hostnames you can defend in a ticket

Static rule posts decay because CDNs and feature flags shift. Build a fresh inventory whenever Discord updates or your subscription provider rearranges geo rules.

On Windows, open Resource Monitor or your Clash client’s live connections while reproducing the stuck updater or broken voice state. Sort by image name to isolate Discord.exe, Update.exe, and related child processes, then note every remote hostname. Cross-check with the Clash connection table: if a name appears in Resource Monitor but never in Clash, you still have a visibility problem rather than a rule-depth problem.

For browser-only comparisons, you can load discord.com in a regular browser tab with developer tools open, but remember that the desktop client may not issue identical requests. Prefer evidence from the actual Discord binaries when possible.

When you document fixes for a community server, paste the hostname list with a capture date. Future you will appreciate the timestamp when a CDN cutover suddenly invalidates yesterday’s YAML.

7. Domain buckets from gateway to CDN edges

After collection, group hosts so your configuration stays readable. Names drift; verify each suffix against your own logs before you paste.

Treat the table as a hypothesis checklist, not a frozen vendor contract. Your subscription may already inject broad “gaming” or “social” lists; reconcile overlaps so your explicit lines still win on precedence.

8. Rule snippets: explicit coverage and clean ordering

The YAML fragments below illustrate steering traffic to a proxy group named PROXY. Rename that token to match your real policy label and insert these lines before broad provider rules that might prematurely return DIRECT for “domestic” CDNs that Discord also uses.

# Example only — replace PROXY with your policy group name
rules:
  - DOMAIN-SUFFIX,discord.com,PROXY
  - DOMAIN-SUFFIX,discordapp.com,PROXY
  - DOMAIN-SUFFIX,discordapp.net,PROXY
  - DOMAIN-SUFFIX,discord.gg,PROXY
  - DOMAIN-SUFFIX,discord.media,PROXY
  - DOMAIN-SUFFIX,discordcdn.com,PROXY

Prefer DOMAIN-SUFFIX when you can express intent precisely. Reserve DOMAIN-KEYWORD for noisy vendor patterns you cannot enumerate, because substring matches are powerful and easy to overfit.

If your subscription injects aggressive geo rules, duplicate critical Discord lines in a user-controlled section that loads with correct precedence, or merge providers thoughtfully so your exceptions win. The same structural advice appears in our GitHub Copilot CDN split article, which walks through multi-vendor hostname graphs with a similar debugging mindset.

9. Updater-specific behavior: why 0% is often a CDN stall

The updater is not a single GET request. It negotiates versions, follows redirects, and may fan out across multiple CDNs. When one leg is proxied and another is not, the UI can sit at 0% because the orchestration step never completes even though a background socket shows bytes moving elsewhere.

When experimenting, clone your proxy group as PROXY_DISCORD and point Discord-related suffixes there, leaving unrelated bulk traffic on DIRECT if policy requires. Document the choice: aggressive auto-switching on huge flows can starve interactive HTTPS sessions if the same pool backs both.

If downloads eventually complete but the UI still looks stuck, capture timestamps from logs and compare with Discord’s release notes. Occasionally the failure is cryptographic trust or disk permissions; routing evidence still matters because mis-proxied OCSP or CRL endpoints can masquerade as CDN stalls.

10. Voice RTC: UDP, stability, and why “same node” matters

Voice RTC punishes flappy tunnels. A node that looks great in a speed test but reconnects every minute forces session rebuilds that users hear as dropouts. Pin voice-heavy traffic to providers that hold steady, reduce auto failover on those destinations, and avoid stacking multiple VPN-class products that re-encapsulate the same flow.

UDP visibility is the subtle part. If your log shows clean HTTPS policies yet voice still disconnects, broaden diagnostics beyond domain rows: confirm whether TUN is active, whether Windows Firewall prompts were dismissed, and whether another product owns the filter driver stack. Enterprise TLS inspection can also break long-lived secure websockets even when downloads succeed.

For background on transports under loss, read Shadowsocks vs Trojan vs Hysteria2. The goal is to match protocol behavior to your packet-loss profile for realtime media, not to crown a single global winner.

11. GUI workflow: logs are the source of truth

Desktop clients such as Clash Verge Rev expose live connections, DNS panes, and rule editors side by side. When Discord misbehaves, filter connections for discord substrings and read the chosen policy per row. If anything sensitive shows DIRECT while similar hosts use PROXY, fix precedence before swapping servers.

If the baseline install still feels unfamiliar, follow the Clash Verge Rev setup guide to confirm ports, subscriptions, and first launch before you chase Discord-specific ghosts.

12. How this differs from Steam or Microsoft Store guides

Our Steam CDN split article targets Valve’s depot and storefront graph—similar CDN split routing instincts, yet Steam does not emphasize browser-grade voice in the same way Discord does. Likewise, UWP loopback guidance for the Microsoft Store addresses sandboxed apps that block localhost proxies by default; Discord is a different executable model, yet the lesson about partial visibility still rhymes.

Enterprise readers should remember that split-horizon DNS can make international Discord surfaces look broken even when Clash is perfect. If only Discord-facing domains fail while unrelated HTTPS succeeds, involve the network team with connection logs rather than assuming the proxy core is misconfigured.

13. Antivirus, game overlays, and dual VPN stacks

Third-party “game boosters,” HTTPS-filtering antivirus suites, and aggressive browser extensions sometimes reorder traffic in ways Clash cannot see. Disable them briefly during triage. Running two VPN-class products simultaneously invites routing loops that masquerade as application bugs.

If you also use WSL or containers alongside Discord, remember those environments inherit none of your Windows YAML unless you explicitly bridge them—our WSL2 host-proxy guide covers the Linux side, which can confuse diagnostics when you test with curl from Ubuntu while Discord runs natively.

14. Open source and trust

If you want to inspect upstream source, review issues, or contribute patches, visit the community repositories linked from our docs. Keep that separate from day-to-day install paths: the primary way readers should fetch maintained desktop builds remains this site’s download flow, not a raw release asset buried in a thread.

15. Close with evidence, not superstition

Discord update fail spinners and brittle voice RTC are maddening because the client still looks authoritative even when the network path is fractured. Treat every frozen percentage as a prompt to open the log, read policies row by row, and reconcile DNS with the hostnames the Discord binaries actually contacted. CDN split routing coverage for Discord’s graph, calm resolver settings, and deliberate Discord Windows proxy choices are the mechanical layer; stable nodes and honest UDP paths are the polish once TCP is honest.

Compared with toggling random VPNs, a maintained desktop client with Mihomo integration keeps diagnostics visible and reduces YAML foot-guns when Discord ships quiet infrastructure changes. → Download Clash for free and experience the difference