This guide explains how to configure v2rayN on a PC. It walks you through installing the Windows client, importing a node or subscription, enabling the system proxy, and checking your exit IP, DNS, and browser settings. Menu names may vary slightly between versions, so use the equivalent options rather than relying on screenshots from older versions.
1. Download the client and get ready
Download the Windows archive for your computer’s architecture from the Releases page of the official v2rayN GitHub project. Most PCs use x64; ARM devices use ARM64. Check the release notes and choose a package that includes the required runtime components. Extract it to a permanent folder before launching it; don’t run it directly from the archive. If you’re prompted to install a missing runtime, follow the official instructions to install the required components.
Prepare a working node link or subscription URL. Node links often begin with vless://, vmess://, or trojan://; subscription URLs are usually HTTPS links. A subscription URL may contain access credentials, so don’t share it publicly or submit it to unfamiliar checking websites. If you use free nodes, check their source and last-updated date as well.
2. Import a node and enable the proxy
- Copy the entire node link, then select the clipboard import option from v2rayN’s “Servers” menu. If you have a QR code, use the scanning feature provided by the client.
- If you’re using a subscription, add a group through the relevant option, such as “Subscription Group Settings.” Enter a name and the subscription URL, save, then update the subscription. If the first update fails, check whether the URL is accessible over your current network.
- Select a node in the server list, then set it as the active server using the right-click menu or the corresponding button. Run a latency or availability test. Treat the results as a guide, and verify the connection by opening a website.
- In the system proxy menu, choose an option such as “Automatically configure system proxy” to enable it. For your first connection, keep the default routing rules. Once the connection works, choose a split-routing mode, such as bypassing mainland China, if needed.
Importing a node doesn’t mean the proxy is already active. You also need to select an active node, make sure the core is running, and enable the system proxy. To test regular browser traffic, start with the system proxy; there’s no need to enable TUN mode right away. Some apps that don’t follow the system proxy may require another method to route their traffic.
3. How IP, DNS, and browser settings interact
An IP-checking page shows the exit address used for that visit. With the proxy enabled, websites routed through it will usually show the node’s exit IP. Sites routed directly may still show your local ISP’s IP, so you can’t determine how all traffic is routed from a single page.
DNS translates domain names into addresses. The route for DNS requests depends on the client’s rules, Windows settings, and the browser’s secure DNS settings. A changed exit IP does not mean that all DNS requests are going through the proxy. Start with the client’s default DNS configuration. If domains won’t load or direct and proxied connections behave differently, check the logs rather than layering on settings at random.
Browser proxy extensions may override the system proxy, and secure DNS may change the resolution path. To troubleshoot, first disable proxy extensions and test in a private window. If you suspect secure DNS, temporarily turn it off and compare. Cookies, signed-in accounts, and location permissions can also affect the region a website displays, so don’t treat the page language as proof of your exit IP.
4. Troubleshoot connection failures in order
First check your computer’s time, basic network connection, and whether the node is still working. Then check the active node and system proxy status. Next, open the client logs and look for messages about timeouts, authentication failures, or port conflicts. If the problem occurs only in one browser, check its extensions and settings first. If all apps are affected, check for conflicts with other VPN or proxy software. Change one setting at a time and test before making another change. Clear the system proxy before exiting the client. If you can’t get online after closing it, check Windows proxy settings and turn off any leftover manual proxy.