Updated July 2026 · 6 min read
Choose and test a proxy node
The proxies page has two levels: groups, and the nodes inside them. Click the wrong level and nothing changes. This covers reading that layout, why a switch seems to do nothing, and keeping spare nodes in rotation.
Work out which group you are in
The proxies page is stacked: a row of proxy groups, and under whichever group you open, the nodes that group can choose from. Clicking a node changes the current selection of that one group only. Nothing else on the page moves.
So the real question is which group your traffic is handed to. If the rules send it to a group for foreign traffic and you keep swapping nodes inside a streaming group, the interface looks fine while the exit never changes. Check the group name on the rules or connections page first.
Where clicking does not stick
A select group obeys you: the node you pick is remembered across restarts. Automatic latency groups do not, and your manual pick is overwritten on the next test round. The details live in the guide on group types; here it is enough to know that pinning an exit means using a select group.
The other case is groups inside groups. If the list shows group names rather than server names, that level only hands traffic on and the real exit sits one layer deeper. Keep opening until you see actual nodes.
Do not judge a node right after switching. Connections that already exist keep using the old exit — close them on the connections page and let the app reconnect.
Why the switch looks ignored
A TCP connection picks its exit the moment it is established, and no amount of clicking moves it afterwards. Right after you switch, a running download, an idle chat client and every open tab are all still travelling the old route.
Open the connections page and close the relevant entries. The applications reconnect on their own and pick up the new node. Browsers are stubborn about keeping sockets alive, so closing the tab, or restarting the browser, is often quicker than waiting it out.
Keep two or three in rotation
Do not stake everything on one node. Pick two or three with different routes from your subscription, say one direct line and one relayed, landing in different regions, and move to the next one when the current one starts to drag.
After a while you learn their habits: one is always congested at eight in the evening, another is quick by day and starts dropping packets late at night. That knowledge beats staring at the millisecond column, because a low number says nothing about the evening peak.
What is the project?
Clash Verge Rev is a Tauri-based GUI for Mihomo with profile management, system proxy, TUN mode, rule editing and WebDAV backups.