On this page
If a film’s details load but playback fails, follow the playback process when deciding what to check. Account region, authorization requests, and sustained video transfer need separate checks; one node speed test cannot replace watching through. Access settings may also differ between a computer and a television, so make the final test on the device you actually use.
Why Can the Homepage Load While Playback Fails?
Clear the connection records before pressing play, then inspect playback authorization and video-segment requests in time order. Even if the home page already matched a proxy group, check the actual outbound connection of each new request to find missing rules.
Stages of the playback process
| Stage | Common symptoms when it fails | What to Inspect |
|---|---|---|
| Account and region detection | Wrong catalog or inconsistent subscription benefits | Account region, egress region, and cookies |
| Catalog and detail pages | The home page opens, but posters or details are missing | Primary site, API, and image assets |
| Playback authorization | An immediate region or proxy error after clicking | Whether authorization requests use the same egress as the primary site |
| Video segments | Playback starts but repeatedly lowers quality or buffers | CDN path, bandwidth, packet loss, and sustained stability |
Do the Account Region and Playback Exit Match?
The lowest-latency streaming node may not have the required regional catalog or playback rights. First pin a node and confirm that the target region matches the account's benefits, then test an actual video. Frequent automatic egress changes during sign-in, authorization, or playback may trigger region detection again.
Even within one region, egress types can differ. Availability of residential, data-center, or shared nodes depends on current platform and provider policies; Clash cannot guarantee so-called “unblocking.” When the platform shows an explicit region or proxy warning, switch to a legitimate, supported egress or review the account settings instead of burying the warning under more rules.
Build Platform Policy Groups from Playback Records
After choosing a fixed node, exit the player or close the tab, clear the Clash connection records, and start playback from the detail page. In time order, check whether the primary site, authorization endpoint, images, and video CDN all enter the same streaming policy group. Only unexpected DIRECT or REJECT requests need correction.
Domain lists vary by platform and device. A TV App, mobile App, and browser may use different CDNs. Copying a complete rule set from someone else's browser log does not prove that the TV's playback requests are covered.
Record one complete playback path
Pin a node
Disable automatic switching during the test so the egress region remains fixed.
Open the detail page again
Make catalog, authorization, and video requests appear again in chronological order.
Play for at least ten minutes
Observe startup, quality ramp-up, and sustained buffering—not only the first frame.
Add rules only for anomalous requests
Place the rule before broad regional rules, then replay the same video.
For Netflix, check whether the catalog region, playback authorization, and video CDN use consistent exits. YouTube pages, the youtubei API, and googlevideo video segments make separate requests; quality may remain low if video requests miss the policy group. For Disney+, check the content available in the current region, account entitlements, and playback authorization.
Separate policy groups for the three platforms let you change egress without affecting other services and prevent one rule correction from changing all streaming traffic. If household accounts belong to different regions, they should not all be bound permanently to one automatic group. YOUR_EXISTING_GROUP below is not a policy-group name; replace it with a real group in the current subscription, such as the actual “Node Selector” or another name you can see.
# 使用前先替换每一处 YOUR_EXISTING_GROUP
proxy-groups:
- name: STREAM-NETFLIX
type: select
proxies:
- YOUR_EXISTING_GROUP
- DIRECT
- name: STREAM-YOUTUBE
type: select
proxies:
- YOUR_EXISTING_GROUP
- DIRECT
- name: STREAM-DISNEY
type: select
proxies:
- YOUR_EXISTING_GROUP
- DIRECT
rules:
- DOMAIN-SUFFIX,netflix.com,STREAM-NETFLIX
- DOMAIN-SUFFIX,nflxvideo.net,STREAM-NETFLIX
- DOMAIN-SUFFIX,youtube.com,STREAM-YOUTUBE
- DOMAIN-SUFFIX,googlevideo.com,STREAM-YOUTUBE
- DOMAIN-SUFFIX,disneyplus.com,STREAM-DISNEY
- DOMAIN-SUFFIX,bamgrid.com,STREAM-DISNEY
- GEOIP,CN,DIRECT
- MATCH,YOUR_EXISTING_GROUPWhen a TV behaves differently, check whether it uses another DNS or IPv6 path
If the browser works but the TV reports a region error, compare the devices’ gateways, DNS, and IP protocols before blaming the node. The TV may use DNS supplied by the router while the computer uses its local Clash instance. The home network may also let the TV connect directly over IPv6 while the proxy captures only IPv4.
On the router, first confirm the TV's actual gateway and DNS. Temporarily disable independent secure DNS on the device or browser for comparison. If disabling IPv6 changes the behavior, complete the IPv6 capture and direct-routing rules instead of treating disabled IPv6 as the permanent answer.
What to Do When the Catalog Is Wrong, Playback Fails, or Buffering Keeps Returning
The catalog is for the wrong region
Common cause:The account, cookies, or egress region do not match
Resolution:Pin egress in the target region, sign in again, and verify the account region.
Playback fails immediately after clicking
Common cause:An authorization request misses the rule, or the platform rejects the current egress
Resolution:Inspect the authorization domain and HTTP message at the instant of the click before optimizing bandwidth.
Playback works but buffers repeatedly within ten minutes
Common cause:Video CDN path, bandwidth, or packet loss
Resolution:Observe segment requests and compare sustained throughput across nodes in the same region.
The computer works, but the TV fails
Common cause:The devices use different gateways, DNS, IPv6 paths, or App domains
Resolution:Inspect the TV's traffic at the router; do not substitute browser results.
Change only one of the node, rule, or DNS per test, and keep playing the same content. Streaming issues are easily hidden by a working home page. A reproducible result includes the correct region, successful authorization, and a sufficiently long period of stable playback.