Nodes, groups and chains

To add sources first, see individual third-party nodes, subscription imports and combining them with managed nodes.

Illustrated steps

English interface simulation · Fictional data · Click to enlarge

Select a node

In Proxies, open the group responsible for your destination and select a node. Under Rule mode, a streaming service may use a different group from the default one. Verify the actual chain in connection records.

Automatic groups

↔ Swipe left or right to see all columns

Group in the profile	How members are chosen
Manual selection	Follows your choice
URL-test, fallback or load balancing	Follows the group's own strategy

Test a small set of nodes on the same network. Latency is not bandwidth or proof of streaming access. If every test fails, check the test URL and local networking too; see diagnostics.

Personal groups

Add a group with valid members in a profile's Override settings, then point personal rules to it. Read Overlay versus Custom mode first. Avoid empty groups and circular references.

Proxy chains

English interface simulation · Fictional data · Click to enlarge

1. In Profiles, open Proxy chains from the current profile's menu, add a chain and give it a recognizable name.
2. Add at least two different members in forwarding order: entry first, exit last. Drag their handles to reorder them. Any hop can be a node or a listed Select, URL-test, Fallback or Load-balance group.
3. Save, make sure the chain is enabled and wait for the profile to apply successfully. The maintained version creates a group named after the chain. Use it in Proxies or select the chain name as a rule target. Check your installed version if this entry is missing.
4. Make a new connection and verify the entry, hops and exit in connection records.

Use a chain name distinct from nodes, groups, proxy providers, Tailscale networks and built-in policies. Avoid MATCH and commas.

↔ Swipe left or right to see all columns

Last hop	How to use it after saving
Node	Prefer the chain name; the derived Node name (via Previous hop name) entry remains available. The original node keeps its original route
Policy group	Select the chain name or the corresponding group; its strategy chooses the actual node

A chain ending in a node joins subscription manual groups that already list that exit, under the chain name. Groups used by the chain and their dependencies are excluded; personal groups need explicit members. If the name is missing from a selector, you can target it directly with a personal rule. Selecting the original exit node does not test the chain.

Groups after the first hop

With Entry A → Exit group saved and applied, a rule targeting Exit group directly, or another group referencing it, also sends its concrete nodes through A. Tests use each actual derived route. Original nodes elsewhere keep their routes. Nested groups, DIRECT and REJECT do not inherit the preceding path; DIRECT skips earlier hops.

Avoid group members that loop back to chain hops or a group following conflicting preceding paths. Saving or enabling a new chain can disable conflicting older chains. After a related-chains-updated notice, check every chain's switch and verify a new connection.

If the saved chain does not work

Check the current profile, chain switch, apply result, rule target and manual selection of the chain name. Resolve missing members, cycles or dialer conflicts as reported. A group with no usable nodes does not silently bypass its preceding hops. Per-hop latency does not prove the complete chain works: test nodes separately, then verify the full path.

Test each member independently. A chain forwards through several stages; load balancing distributes different connections across members. If a chain fails, compare a single node, then check each segment.