Quick checklist: verify your proxy is working in Clash Verge

Turning Clash Verge on is not the same as knowing traffic is clean. Use this short checklist after you import a subscription — for example from Roxi — so you catch DNS leaks, wrong exits, and local sites that should stay direct.

Before you start

• Clash Verge is installed on Windows or macOS.
• A profile is imported and selected.
• System proxy or TUN mode is on (pick one workflow for the test).
• You know which proxy group is active.

Roxi’s free tier is 30 minutes per day at full speed; VIP is 3.57 USD per 30 days (200GB) and SVIP is 7.14 USD per 30 days (500GB). New users get an exclusive offer plus a free trial. Plans are capped — do not assume unlimited traffic when reading speed tests.

Checklist

1. Confirm the client is routing

Status shows connected / system proxy enabled (or TUN running). The Connections view should show live streams when you load a page. If it stays empty, the browser may be ignoring the system proxy — try another browser or enable TUN for the test.

2. IP check (exit node)

1. Visit a simple IP page (for example https://ip.sb or https://ifconfig.me).
2. Compare the reported IP and country with the node you selected.
3. Switch to a second node in another region and reload — the IP should change.

If the IP never changes, traffic is still direct. Re-check system proxy, browser exceptions, and whether another VPN is active.

3. DNS leak test

1. With the proxy on, open a reputable DNS leak test page.
2. Run the extended test and wait for resolvers to appear.
3. Resolvers should match the proxy path you expect, not your raw home ISP if you intended full proxy DNS.

Prefer the profile’s recommended dns block. Mixing system DNS with random DoH without rules is a common leak source. After DNS changes, restart the core and re-test.

4. Routing rules for local sites

Banks, government portals, and LAN addresses should stay DIRECT:

• Confirm rules for LOCAL, private CIDRs, and local domains if the profile ships them.
• Open a local site that must see your real IP; it should not appear under the proxy group in Connections.
• Open an international site; it should show the active proxy group.

If everything is forced through GLOBAL, switch back to rule mode for daily use.

5. Silent-failure checks

• Clock skew: wrong system time breaks TLS — sync NTP.
• Stale subscription: update the profile, then re-select a live node.
• Quota: if the free daily window or monthly GB is exhausted, tests look like random timeouts — check the dashboard.
• IPv6 leaks: if your ISP gives IPv6 and the profile ignores it, disable IPv6 temporarily or use a profile that handles it, then re-test.

6. Pass/fail summary

When something fails

Update the subscription without proxy, pick a node with a fresh delay test, re-run IP + DNS checks, then adjust routing. For Roxi account or link issues: support@roxi.cc.

Written by the small independent team behind Roxi.