Streaming platforms are far pickier about IPs than ordinary sites: Netflix serves a per-IP regional catalog and blocks datacenter IPs; YouTube keys ads and quality to the IP. The standard solution is binding streaming traffic to dedicated "unblock" nodes.
Step 1: a streaming group
Append a manual group via Parsers (or by editing the profile):
append-proxy-groups:
- name: "Streaming"
type: select
proxies: ["HK 01", "SG 01", "US 01"]
Fill it with nodes your provider marks as "streaming" or "Netflix".
Step 2: point streaming domains at the group
prepend-rules:
# Netflix
- DOMAIN-SUFFIX,netflix.com,Streaming
- DOMAIN-SUFFIX,nflxvideo.net,Streaming
- DOMAIN-SUFFIX,nflximg.net,Streaming
- DOMAIN-KEYWORD,netflix,Streaming
# YouTube
- DOMAIN-SUFFIX,youtube.com,Streaming
- DOMAIN-SUFFIX,googlevideo.com,Streaming
- DOMAIN-SUFFIX,ytimg.com,Streaming
# Disney+
- DOMAIN-SUFFIX,disneyplus.com,Streaming
- DOMAIN-SUFFIX,disney-plus.net,Streaming
For full coverage (CDN domains especially), use a community streaming RULE-SET instead of hand-maintaining the list.
Step 3: verify
- Select an unblock node in "Streaming" and play a non-Netflix-original title (originals play from any IP and prove nothing).
- Confirm on the Connections page that
nflxvideo.netconnections use the Streaming group. - Changing region = switching the node in the Streaming group and refreshing.
Troubleshooting
- "You seem to be using an unblocker": that node's IP is flagged - try another in the group.
- Wrong subtitle/audio language: region follows the IP; account language is a separate profile setting.
- 4K stutters: the unblock node lacks bandwidth. Consider separate "unblocks-but-slow" and "fast-but-no-unblock" groups for different tasks.