v2rayN: 10 Common Beginner Questions About Subscriptions, Connection Errors, and Switching Servers

Answers to 10 common v2rayN questions, from importing subscriptions and fixing startup or connection errors to switching servers and testing latency. Each answer points to the relevant setting.

At a glance

For anyone using v2rayN on desktop for the first time. Work through subscription setup, core startup, app routing, and server switching in that order, changing one setting at a time. Menu names refer to the common Chinese-language interface in the Windows desktop version; they may vary by version or appear in the system tray menu.

1. Subscriptions and importing individual servers

1. I saved a subscription URL. Why is the server list empty?

In short: Saving the URL adds a subscription source; update the subscription to fetch its servers.

  1. Open “Subscription Group” → “Subscription Group Settings,” add a group, and enter a name and the full subscription URL. The name is only for identifying the source; it cannot replace the URL.
  2. Return to the main window and select the group you just added. From “Subscription Group,” choose the option to update the current subscription. If the menu offers updates with or without a proxy, choose the route that can reach the subscription URL. If no proxy is available, don't start by relying on a proxied update.
  3. After updating, check the log and group list. If the download failed, check whether the URL has expired or is missing query parameters. If the download succeeded but no entries appear, clear any list search filters and confirm that the source returned subscription data the client can read—not a sign-in or error page.

2. I only have one server link. Where do I enter it?

In short: Import a single-server share link from the clipboard; don't enter it in the subscription URL field.

2. Core startup and connection failures

3. The core won't start. Should I check the installation or the port first?

In short: Read the first error from the current startup attempt in the main window log, then decide whether to check a file or a port. Changing servers or toggling the system proxy won't fix a local listener if the core never started.

Error snippet: address already in use

Cause: Another process is using the listening port shown in the log. Fix: Check whether a second instance is running and close it, or change the conflicting local listening port under “Settings” → “Parameter Settings.”

Error snippet: The system cannot find the file specified.

Cause: If this appears right after the core startup message, the target file or path is usually missing. Fix: Check the path in the log and the extraction folder, then follow Getting Started to add the required files. Moving only the main executable to a different folder won't solve the problem.

4. The core is running. Why do connections still time out?

In short: First determine whether one server or all servers are failing, then check the outbound connection settings.

  1. Select two servers with different addresses in the main window and test their real connection latency one at a time. If only one fails, open its settings and compare the address, port, transport, and security options with the source. Don't disable certificate verification just to make a test pass.
  2. If several servers fail, try a different test destination known to be reachable. Failure against one destination alone doesn't prove that every server is unavailable. If the error mentions a certificate date, check the system clock. If it mentions DNS resolution, determine whether the failed lookup was for the server domain or the destination.
  3. Note the time of a failure, reproduce it once, then check the log for that same time. This separates old startup errors from the current connection failure.

3. System proxy and app routing

5. The system proxy is on. Why isn't my app using it?

In short: The system proxy provides settings for apps that support it; it doesn't route traffic from every program.

App requestProxy settingsLocal inboundRoute matchRule-based outbound

6. An app asks me to enter a proxy address manually. Which port should I use?

In short: Enter the local listening address and the correct inbound port—not the remote server address. In v2rayN, open “Settings” → “Parameter Settings” to check the current listener and supported proxy types.

127.0.0.1
Loopback address for apps on the same device
10808
Common local port examples; use the values in your settings

Match the protocol first, then enter the port

If the app uses SOCKS5, enter a local inbound port that supports SOCKS5. If it uses HTTP, enter a port that supports HTTP. A mixed inbound can use one port for both; separate listeners use their respective ports. Don't guess the protocol from the port number.

4. Switching servers and testing speed

7. I clicked another server. Why am I still using the old one?

In short: Highlighting a row only selects it. Set it as the active server to switch.

  1. In the main window, right-click the server you want and choose “Set as active server” or the equivalent option. After switching, check the active indicator and the new log entries; don't rely on the highlighted row.
  2. Verify the change with a new request. Existing downloads or long-lived connections may stop or continue using the old connection, so don't use an existing session to judge the new server. Keep the routing mode unchanged during the test so you don't mistake a rule change for a server switch.

8. Does the server with the lowest latency always download the fastest?

In short: Latency measures response time; download speed measures how much data transfers over time. Compare them separately.

5. Checking routing and restoring settings after exit

9. Why do some sites connect directly through the same server?

In short: The active server determines which connection proxy traffic uses; routing rules determine whether a request uses that outbound route.

10. After I exit v2rayN, my browser can't open websites. How do I fix it?

In short: Restore the system proxy settings you had before exiting, then troubleshoot the network. A leftover local proxy address may point to a listening port that stopped when the app closed.

  1. If you can reopen the client, choose “System Proxy” → “Clear system proxy” in the tray menu, then exit normally. If you previously used a workplace proxy or an automatic configuration script, restore those settings rather than turning off every proxy option.
  2. If the client won't start, open Windows “Settings” → “Network & Internet” → “Proxy” and check whether the manual proxy still points to your own device. After restoring the settings, reopen the browser and test again. If only one app still fails, check whether it has its own saved local proxy address.
Download v2rayNChoose a package for your platform