1. Diagnose the failure before changing your profile
When Netflix stops working through Clash, the symptom matters more than the fact that a proxy is enabled. A black screen, an endless loading spinner, a playback error, a sign-in loop, and a page that will not load can point to different parts of the connection. Changing several settings at once may make the problem disappear temporarily, but it also hides the cause and makes the next failure harder to investigate.
Start with a simple comparison. In the same browser and on the same device, try Netflix with Clash enabled, then pause the proxy and test again if that is permitted on your network. Note whether the homepage loads, whether you can sign in, whether a title starts, and whether playback continues for at least a few minutes. Do not assume that a successful homepage test proves streaming is healthy: the page, account services, and video segments can use different hostnames and connection paths.
Next, record the exact error message and the time it occurred. Open Clash Verge, Clash Verge Rev, or another Mihomo-based client and inspect the connection log while you reproduce the failure. Look for Netflix-related requests and note the rule that matched, the selected proxy group, the chosen node, and whether the connection ended normally or timed out. A log entry marked DIRECT when you expected a proxy, or a request sent to an unavailable group, is a more useful lead than repeatedly switching nodes at random.
- Netflix will not open: Check the active profile, system proxy or TUN status, DNS behavior, and whether the browser is actually covered by the client.
- The page loads but sign-in fails: Look for inconsistent routing between Netflix and the account or authentication requests visible in the log. Also test a private browser window to rule out stale cookies.
- The title starts and then buffers: Compare node latency and stability, check whether video connections are using the intended group, and investigate UDP or IPv6 handling if the profile or client exposes those controls.
- Only one device or browser fails: Check that device’s proxy settings, VPN conflicts, DNS cache, browser extensions, and any per-app routing options before editing shared rules.
Keep the investigation narrow. First confirm the selected configuration and the current operating mode. Then test one candidate node, one browser session, and one playback attempt. If you change the mode, node, DNS option, and rule order together, a successful test will not tell you which change mattered.
2. Check proxy mode, rule order, and Netflix routing
In Rule mode, Clash makes a routing decision for each connection according to the rules in the active profile. In Global mode, traffic is generally sent through the selected proxy group, while Direct mode bypasses the proxy. The exact labels and controls vary by client version, but the principle is the same: the mode and the profile determine whether a request reaches a proxy group at all.
For a useful first test, choose Rule mode and watch the connection log as Netflix loads and starts a title. Confirm that relevant requests are matched by the rule you expect and that the matched rule points to a group with a usable node. A rule can be syntactically correct yet ineffective if an earlier, broader rule captures the request first. For example, a general domain or geolocation rule placed above a service-specific rule may decide the route before the Netflix rule is reached.
Netflix uses multiple service and delivery domains, and the exact set can vary by device, app version, and content delivery path. Hostnames commonly observed in traffic may include families such as netflix.com, nflxvideo.net, nflximg.net, nflxso.net, and nflxext.com. Treat these as investigation clues, not a universal list: add or change a rule only when your own connection log shows that a relevant request is being routed incorrectly. Avoid copying a large ruleset from an old forum post without checking what it matches in your profile.
If you maintain the YAML yourself, place verified, specific rules before broad catch-all rules, and make sure the proxy group name exactly matches a group defined in the configuration. A conceptual example might look like this:
rules:
- DOMAIN-SUFFIX,netflix.com,Streaming
- DOMAIN-SUFFIX,nflxvideo.net,Streaming
- MATCH,Other Traffic
This example is not a complete Netflix policy and should not be pasted blindly into every subscription profile. Providers may manage rule providers, groups, or updates automatically, and editing a generated configuration can be overwritten at the next refresh. If your client supports profile overrides or script-based patches, use the supported mechanism and retain a copy of the original configuration so you can roll back safely.
Test the rule in a controlled way. Reload the profile if your client requires it, clear only the affected connection state if the client offers that control, and start a fresh Netflix session. In the log, verify that the request matches the intended rule and group. If the rule matches but playback still fails, the routing decision may be correct while the node, DNS answer, transport path, or account-side availability remains the problem.
3. Test nodes, DNS, and connection stability
A node can pass a quick latency test and still perform poorly during video playback. A ping or URL test checks only a small part of the path; it does not guarantee steady throughput, reliable long-lived connections, or a route that Netflix can use for the requested stream. Test two or three suitable nodes from the same group, one at a time, and keep the client mode, rules, device, and browser unchanged. Record whether the title starts, whether quality changes, and whether playback stops after a repeatable interval.
Prefer a stable route with consistent performance over a node that has the lowest initial delay but fluctuates under load. If a group uses automatic selection, temporarily choose a specific node for diagnosis when the client allows it. That removes one variable: otherwise, the group may switch nodes between page loading and video delivery, making the results difficult to compare. Restore automatic selection after testing if that is your normal setup.
DNS is another common source of confusing behavior. Mihomo profiles may use fake-IP or redir-host behavior, and client interfaces can expose DNS settings that differ between profiles. A stale browser cache, operating-system cache, or resolver response can make the application connect to an address that no longer corresponds to the route you intended. As a low-risk test, restart the browser, reconnect the profile, and clear the relevant DNS cache using the operating system’s normal tools. Do not disable DNS safeguards or copy resolver addresses from an untrusted configuration simply to make one test pass.
If the connection log shows a Netflix hostname resolving or routing differently than expected, compare the result with the active DNS mode and the profile’s DNS rules. If your client provides a DNS query or connection view, use it to check which resolver handled the request. Change only one DNS setting at a time, then repeat the same playback test. If the change has no effect, restore the previous value rather than stacking several unverified workarounds.
Some networks and devices also behave differently with IPv6 or UDP-based transports. If your profile enables IPv6, compare a test with the setting temporarily disabled, provided you understand how to restore it. If the client exposes controls for UDP, QUIC, or HTTP/3, check its documentation and logs before changing them; names and behavior differ across clients and core versions. A transport change is a diagnostic step, not a guarantee that Netflix will use a particular protocol or that disabling it is always preferable.
Finally, rule out local interference. A second VPN, a browser privacy extension, endpoint security software, a custom DNS app, or an OS-level proxy can compete with Clash for the same connections. For a brief test, disable only one nonessential component at a time, following workplace or device policy. On a managed computer, do not bypass security controls; ask the administrator to confirm whether the proxy configuration is supported.
4. Use TUN mode to isolate app-level proxy gaps
A browser may follow the system proxy while the Netflix desktop application, a smart-TV app, or another device ignores it. TUN mode can help diagnose that difference because it routes more application traffic through a virtual network interface instead of relying only on applications to honor the system proxy. It is especially useful when the client log is empty even though the app is clearly attempting to connect.
Before enabling TUN, check the client’s permissions and platform requirements. Some systems require administrator approval, a network extension permission, or a restart. Save the current profile and note the existing proxy mode so you can restore it. Then enable TUN using the client’s documented controls, confirm that the client reports it as active, and repeat the same test with the same node and profile. If requests now appear in the log, the earlier problem was likely related to application proxy coverage rather than a Netflix-specific rule.
TUN mode is not automatically the best permanent setting. It can affect more applications than system-proxy mode, and DNS handling, local-network access, or conflicts with another VPN may need attention. If Netflix works only with TUN, inspect which connections are captured and whether your ordinary traffic still follows the intended rules. Do not leave broad routing enabled without understanding its effect on local services, work applications, and other devices on the network.
If the browser works but a television or streaming box does not, remember that configuring Clash on a computer does not automatically route traffic from a separate device. Device-level proxy support, a supported router configuration, or another approved network setup may be required. Verify the network path for that device rather than assuming that the computer’s successful test applies to every client on the same Wi-Fi.
Use the following sequence to isolate the problem without turning every setting into a moving target:
- Confirm the active profile and note whether the client is in Rule, Global, or Direct mode.
- Reproduce the error and inspect the log for the exact hostname, matched rule, selected group, and connection result.
- Test one known-good node in the intended group, leaving the rest of the configuration unchanged.
- Check DNS behavior and clear stale local cache only if the evidence points to a resolution problem.
- Compare system-proxy and TUN behavior if the application appears to bypass the proxy.
- Restore any diagnostic setting that did not help, then write down the one change that did.
Keep account and service availability separate from network troubleshooting. A proxy cannot repair an account restriction, an expired subscription, an unsupported device, or a temporary Netflix outage. Follow the service’s terms and your local rules, and do not use routing changes to evade geographic licensing restrictions. If the same account and device fail on a normal connection as well, check Netflix’s own help resources before continuing to modify Clash.
5. Frequently asked questions
Why does Netflix load, but a video will not play?
The homepage and the video stream may use different hosts, connections, or delivery paths. Check the Clash log while starting a title, not just while opening Netflix, and verify that the requests involved in playback match the intended rules and group. If routing looks consistent, test another stable node and check DNS or transport behavior one change at a time.
Should I use Global mode for Netflix?
Global mode can be a useful short diagnostic if you want to determine whether rule selection is involved, but it is not required as a permanent fix. It may route unrelated traffic through the same proxy. Prefer a verified rule and group for the relevant requests when that suits your profile, and return to your normal mode after testing.
Will TUN mode fix every Netflix problem?
No. TUN can capture traffic from applications that do not honor the system proxy, but it cannot fix an unavailable node, an account issue, a DNS misconfiguration, or a service outage. Use it to test whether the application was bypassing Clash, then decide whether the broader traffic capture is appropriate for your device.
Why did my Netflix rule stop working after an update?
A subscription refresh or profile update may replace manual edits, change group names, or reorder rules. Check the active configuration and connection log after updating. If the client supports overrides, use that feature instead of editing generated content, and keep a backup of the working profile so you can compare changes.
Some one-click VPN apps make it easy to switch routes, but they may offer little visibility when a streaming page loads while its video connection fails, and broad tunnel settings can send unrelated traffic through the same path. Clash takes more initial inspection, yet its connection logs, rule order, proxy groups, and optional TUN routing let you test each cause separately and keep other traffic under control. If you want to compare a compatible client with your current setup, start with the download page.
Ready to get started?
Choose a compatible client, then use its connection logs and routing controls to troubleshoot Netflix playback step by step.