This guide addresses the practical question of how to configure v2rayN on a PC. It covers downloading and installing the app, importing nodes, enabling the proxy, and understanding how IP addresses, DNS, and browser settings interact—so you can verify that you’re connected and know where to start troubleshooting if websites won’t load.
1. Install v2rayN and prepare your nodes
v2rayN is a popular graphical client for V2Ray/Xray on Windows. It supports importing nodes and subscription links for protocols such as VLESS, VMess, and Trojan. Before you begin, make sure your system clock is accurate, as an incorrect time can cause TLS connections to fail.
- Download the Windows version of v2rayN and extract it to a path that doesn’t contain Chinese characters, such as
D:v2rayN. - Right-click
v2rayN.exeand select Run as administrator. After the first launch, you should see the app icon in the system tray. - Prepare your nodes: use a subscription link you already have, or copy an available link from our free nodes page.
- If you’re prompted to install a missing runtime, install the .NET Desktop Runtime as instructed, then reopen the app.
Note: Node availability can vary depending on your network environment. A correct configuration doesn’t guarantee that every node will connect.
2. Import a subscription or a single node
Once you open the v2rayN main window, there are two common ways to import nodes. If you have a subscription link, click “Subscription Group” or “Subscription Settings,” add the subscription URL, save it, then select “Update Subscription.” If you have a vmess://, vless://, or trojan:// link, copy it to your clipboard, then select “Import from clipboard” in v2rayN.
- Subscription: Best for regular use; refresh the subscription to update your nodes.
- Single node: Useful for a quick test; just copy the link to import it.
- QR code: If the provider supplies a QR code, scan it to import the node.
After importing, right-click a node and set it as the active server. You can use “Test latency” to find responsive nodes, but treat the results as a rough guide—they don’t necessarily reflect your browsing experience.
3. Enable the system proxy and check your IP
After selecting a node, you’ll also need to enable the proxy. Click the v2rayN tray icon, set the routing mode to “Bypass Mainland China” or “Global,” then enable “System Proxy.” Most users should start with “Bypass Mainland China,” which generally sends domestic websites directly while routing overseas sites through the proxy.
Once configured, open a browser and visit an IP lookup website. If the displayed public IP differs from the one assigned by your local provider, the proxy is probably working. If your IP hasn’t changed, first check whether v2rayN is running, the system proxy is enabled, and your browser isn’t using its own proxy settings.
4. DNS, browser settings, and troubleshooting connection failures
DNS translates domain names into IP addresses; a proxy forwards network traffic. They are not the same thing. If you can connect but some websites won’t load, the cause may be DNS pollution, your browser cache, or a problem with the node itself. Try these steps in order:
- Switch to another node to check whether the current one is down.
- Update the core in v2rayN to avoid incompatibilities with newer configurations.
- Switch routing modes and test both “Global” and “Bypass Mainland China.”
- Clear your browser cache or test in an incognito window.
- Check your browser extensions, especially proxy or privacy extensions that might conflict.
- Flush the DNS cache by running
ipconfig /flushdnsin Command Prompt.
If your browser has DoH or Secure DNS enabled, or you have another proxy extension installed, it may bypass v2rayN’s system proxy. This can make the client appear to be working even though your browser traffic isn’t going through the proxy. Temporarily disable the relevant extensions or switch to system proxy mode to test.
5. Tips for everyday use
Don’t run multiple proxy apps at the same time. Running Clash, sing-box, a browser proxy extension, and v2rayN together can cause port conflicts. When troubleshooting, use just one client at a time. Once everything is working, save your subscription and update your nodes regularly. If they suddenly stop working, try switching nodes and updating your subscription before investigating your network environment.