Basics
First, distinguish three states: the client starts, the node connects, and the app can access its destination.
v2rayN, v2rayNG, or v2flyNG: Which Should You Choose?
Choose v2rayN for Windows, macOS, and Linux. On Android, v2rayNG with the Xray core is usually the first option to consider; use v2flyNG if your provider specifically requires the V2Fly core. Once you’ve chosen a client, check the node’s protocol, transport, and security settings. Support for a protocol name alone doesn’t mean both clients can run every configuration for that node.
What do the graphical client and core each do?
The graphical client manages subscriptions, node lists, and settings, then starts the core with the current configuration. The core establishes protocol connections, applies routing rules, and handles the traffic it receives. Opening the client doesn’t mean the core has started. If a port is in use, a configuration field isn’t recognized, or the core exits, check the startup log first, then review the relevant settings.
What’s the difference between a subscription URL and a single-node share link?
A subscription URL periodically retrieves a set of nodes. Save it to a subscription group, then update the group. A single-node share link usually imports one server configuration and is often imported from the clipboard. The URL prefix alone may not tell you what it contains; if you’re unsure, follow the provider’s description. Either type of link may contain access credentials, so don’t post it in a public support forum.
Does a “Started” status mean the node is ready to use?
Not necessarily. “Started” usually means the local proxy component is running; it doesn’t confirm a successful remote connection or that the target app’s requests are going through the proxy. Run a connection test on the selected node, then use the app to open the target site. If the test passes but the app doesn’t work, check traffic capture and routing. If the test fails too, start with the node and your network.
Installation & Setup
Check the operating system and architecture before installing. During initial setup, confirm the core starts and the subscription imports before switching traffic capture modes.
Which Android package should I choose: arm64 or universal?
If your device runs an arm64-v8a system, choose the arm64 package. If you’re unsure which app architecture your device supports, start with the universal package; it usually includes multiple architectures and takes up more space. Don’t rely only on whether the processor is 64-bit: some devices run a 32-bit system. If installation still fails, check the Android version and possible signature conflicts.
Which Windows version should I choose: Desktop or classic WPF?
For a first installation, try the Desktop version, which uses a cross-platform interface. Choose WPF if you prefer the classic interface or are following instructions for that version. Before downloading, check the release’s system requirements and processor architecture. Back up your settings before switching versions, and exit the old instance to prevent both versions from competing for the same local proxy port.
What should I check if my first subscription import fails?
Save the full URL in the subscription group settings, then update that group. If no nodes appear, check whether the copied URL is missing query parameters or contains spaces, line breaks, or trailing punctuation. Then review the update log. If the request failed, check your network and the URL. If the download succeeded but parsing failed, make sure the response isn’t a login page or error message, and verify the subscription format.
What permissions does TUN mode require?
TUN mode creates a virtual network adapter and changes routing, so its permission requirements depend on the operating system and client. On Windows, if the log explicitly reports access denied, exit the current instance and follow the client’s instructions to run it as an administrator. On Android, approve the system prompt when the client requests a VPN connection. If it still fails, check whether another VPN or virtual network adapter tool is using the required resources.
Tips & Techniques
Keep the node and destination the same during testing, and change only one setting at a time to avoid mistaking network fluctuations for configuration changes.
Should I use system proxy or TUN mode first?
If you only need a browser and other apps that follow system proxy settings to use a proxy, start with system proxy; it’s easier to troubleshoot. Consider TUN if an app ignores system proxy settings and you need to capture its traffic. To compare the modes, keep the same node and destination and change only the capture method. TUN traffic is still processed by routing rules, so it won’t necessarily all go through the proxy.
Why does ping work when the connection test fails?
A successful ping usually means the destination responds to ICMP. It doesn’t confirm that the proxy server’s port is reachable, validate the protocol handshake or authentication, or prove that the destination site can be accessed. When choosing a node, first check that connection tests pass consistently, then compare latency. Check download speed if you need to transfer large files. For a fair comparison, use the same network, test method, and destination; don’t rank results from different tests side by side.
How can I avoid updating the wrong group when I have multiple subscriptions?
Give each subscription a clear group name. Before updating, select the intended group and verify its name and URL, then choose the option to update only the current subscription. Keep manually added nodes you want to retain in a separate group so subscription refreshes don’t replace them. If nodes share a name, compare their group, server address, and protocol rather than relying on the remark alone.
After changing DNS or routing, how can I tell which setting made a difference?
Note the original settings and choose a destination that reliably reproduces the issue. Change only one setting at a time. For DNS, identify whether the app, operating system, or core is resolving the hostname, and check whether the browser has its own Secure DNS setting. For routing, inspect the rule and outbound that actually matched; a broader rule higher in the list may match first. Start a new connection for each test to avoid reusing an existing session.
Troubleshooting
Note when the issue occurred, the selected node, and the proxy mode, then reproduce it once. Check the logs from the same time. Before sharing them, remove subscription URLs, user identifiers, and authentication details.
A subscription that used to update now fails. How can I troubleshoot it?
Check the latest update log to distinguish a request timeout, authorization failure, or parsing error. For a timeout, check your current network and whether the update request relies on a node that’s no longer available. For a 401 or 403 response, ask the provider whether the subscription has expired or access requirements have changed. If the request succeeds but no nodes appear, verify the response format. Keep your existing nodes; don’t delete the whole group just because an update failed.
When a node test times out, should I switch nodes or networks first?
On the same network, test a known-working node as a comparison using the same method. If only one node times out, check its address, port, and transport settings. If several time out, first confirm that your local network works, the system clock is correct, and the core is running. If possible, test the same node on another network. Note the test time and log details; one timeout isn’t enough to conclude that a node is down.
The node test passes, but I still can’t access the internet. What should I check first?
First determine whether the issue affects one site, one app, or all apps. Reproduce it once and check the log for the same time. If there’s no matching request, check whether the app’s traffic is entering the proxy. If a request appears but uses an unexpected outbound, check the routing rules. If the log shows a DNS resolution or handshake failure, check DNS, the system clock, and the node’s security settings. A passing connection test only means its test destination was reachable at that time.
Why do some apps bypass the proxy even when system proxy is enabled?
Some apps ignore system proxy settings or prioritize their own network settings. First confirm that the client applied the system proxy, then check that the address and port in system settings match the local proxy listener. Compare with a browser that follows system proxy settings. If only one app is affected, check its built-in proxy settings. If it has no such option, consider whether TUN is needed.