V2Ray Help Center

V2Ray FAQ

Subscription import failing, server timing out, or system proxy not connecting? First identify where the problem occurs, then decide what to change.

Troubleshooting flow · From configuration to outbound
  1. Import configuration
  2. Connect apps
  3. Route traffic

Concepts

Understand clients, cores, servers, and connection modes.

What’s the difference between V2Ray, v2rayN, and v2rayNG?

V2Ray commonly refers to the proxy technology ecosystem developed by Project V, and sometimes to its associated core. v2rayN is a desktop GUI client, while v2rayNG is an Android GUI client. Clients import and manage configurations, select servers, and switch connection modes; the core handles protocol connections and routing. When following a guide, check that it matches your client and platform. When reading logs, distinguish a failed UI action from a core startup failure or a connection that was sent but received no response. If a core parameter causes an error, the client name alone is not enough to determine compatibility—check which core is actually in use.

Can I import a subscription URL and individual server links the same way?

No. A subscription URL usually starts with HTTPS. The client fetches it and parses the response into a server list. An individual share link usually starts with vmess://, vless://, or trojan:// and already contains the connection settings for one server. Add a subscription URL to a subscription group and update it; import a share link using the clipboard import option. A management page URL may open in a browser but still return content the client cannot parse. Both subscription URLs and share links may contain access credentials, so don’t post them when asking for help.

Are system proxy, TUN, and global routing the same thing?

They solve different problems. The system proxy provides a local proxy address to apps that read the system settings. TUN uses a virtual network interface to capture traffic covered by its routes. Global routing chooses an outbound for traffic that has already entered the core. Switching to global routing alone won’t connect apps that ignore the system proxy. If a browser works but a terminal doesn’t, first check whether the terminal reads system settings or has its own proxy configuration instead of switching servers right away. To troubleshoot devices on your local network that can’t connect, check how their traffic reaches the client and which rule matches it.

Can I switch between VMess, VLESS, and Trojan in the client?

You can’t switch protocols just by changing the protocol dropdown in the client. The server address, port, identity parameters, transport, and security settings must match the server configuration. If the logs show an authentication or handshake error after import, compare the settings with the source configuration. Check that the protocol, server name, and transport options haven’t changed, then confirm that the selected core supports those parameters. Different servers may share a domain but use different ports and settings, so don’t check the address alone. Keep the original entry and make a copy to test one change at a time, so you can identify what caused the problem.

Setup

From choosing an installer to importing your first configuration and granting TUN permissions.

Visit the download center
Which Android package should I choose: arm64 or universal?

Check which app architectures your device’s operating system supports. If the manufacturer’s specifications or device info explicitly list arm64-v8a, choose arm64. If you’re unsure, check which architectures the universal build supports and make sure it includes one supported by your device. A 64-bit-capable chip doesn’t guarantee that the operating system can install 64-bit apps. Universal builds usually include components for multiple architectures and may be larger. If the universal build still won’t install, check the required OS version, available storage, and whether an app with the same name but a different signature is already installed. If an update is blocked by a signature conflict, back up your configuration before removing the existing client.

Which v2rayN build should I use on Windows: Desktop or WPF?

For a first installation, consider the Desktop build, which has an interface similar to the versions for other desktop platforms. Choose WPF if you prefer the classic Windows interface or are following a guide written specifically for that build. Before downloading, check your system architecture and the build’s runtime requirements. To compare both builds, exit the one that’s running before opening the other. Running them together can occupy the same local listening port or repeatedly change the system proxy. Back up your subscriptions and custom routing before migrating settings. After reopening the client, check that the selected server, core, and local listening port are as expected.

I added a subscription URL. Why are there still no servers in the list?

Saving the URL only creates a subscription entry; you still need to update that group. First check that the URL is complete and contains no extra text, line breaks, or spaces, then review the update log. If the request succeeds but parsing fails, the response may be a login page, an error message, or a subscription format the client doesn’t support. Check with the subscription provider to confirm the expected format. If the log says the servers were imported, clear the list search and select the group you just updated in case filtering hid the entries. Don’t keep creating groups with the same name while troubleshooting, or you may update the wrong one later.

TUN reports insufficient permissions. What should I check?

On desktop, check the core logs first to see whether creation of the virtual interface was denied or the interface was created but route setup failed. Use a supported elevation method according to the client and platform documentation; don’t change permissions across system directories. On Android, grant VPN connection permission in system settings and check whether another app is already using the VPN connection. If a work-managed device explicitly blocks virtual interfaces, ask your administrator about the policy. If the logs indicate a missing interface component, repeatedly increasing permissions won’t help—check the platform’s installation steps to make sure the required components are present.

Tips

Test routing rules, organize subscriptions, and document reproducible issues.

Subscription groups and server filters
How can I tell which routing rule is taking effect?

Test against one specific target, such as the same domain each time. First check that the client has enabled the rule set you’re editing, then review the rules from top to bottom: typically, the first matching rule determines the outbound, and an overly broad rule near the top can prevent later exceptions from matching. If the logs show outbound tags, compare the tag selected for the request with the one you expected. If a domain rule doesn’t match, check whether the client sees a domain or an already-resolved IP address, and review the current domain resolution strategy. Change one rule at a time, then make a new connection and check the result.

Do I need to toggle the system proxy after switching servers?

Usually not. The system proxy points to an address and port where the client listens locally; switching servers changes the outbound the core uses. Make sure the new server is active, then send a new request. Apps reusing an existing connection may not show the change, so close and reopen the relevant page or app. If switching also changed the local listening port, check whether the system proxy or the app’s own proxy settings still point to the old port. If the core didn’t start after the switch, check its startup logs rather than repeatedly toggling the system proxy.

How can I manage multiple subscriptions without updating the wrong group?

Give each group a short, distinct name based on its source. Don’t use subscription URLs or access credentials as labels. Update groups one at a time initially, confirm where the servers appear, and then decide which groups need regular updates. If a subscription is maintained by its provider, avoid making lasting manual changes to its entries; an update may replace them. Save test configurations you need to keep in a separate manual group. Servers with the same name may have different settings, so compare the protocol, address, and transport before removing duplicates, and make sure you don’t delete the server currently in use.

What should I include in a log screenshot when reporting a problem?

Note the client and core versions, operating system, connection mode, and the last action before the issue occurred. Then capture only the log lines showing the error and a few lines around it. Keep the error type—such as a parse failure, connection refused, connection timeout, or handshake failure—but redact subscription URLs, share links, user identifiers, and server addresses you don’t want to make public. If you can reproduce the problem, describe its scope: one server or an entire group, a browser or a specific app. This information is more useful for troubleshooting than repeatedly posting full-screen screenshots.

Troubleshooting

Narrow down the issue based on symptoms, then check the connection logs.

Troubleshoot browsers and terminals separately
A server test timed out. How can I tell whether it’s one server or my local network?

Use the same test method to compare the current server with another one known to work. If only one times out, check its address, port, and transport settings first, and ask the provider about server status if needed. If all servers time out, disconnect from the proxy and confirm your current network works, then test one server over another available network. If the logs report a DNS resolution failure, connection timeout, or handshake timeout, investigate DNS, network connectivity, or connection settings respectively. Latency tests also depend on their test target, so one timeout doesn’t prove a server is down. Try an actual request as a comparison.

The client says it’s connected. Why won’t webpages load?

A client showing as running often means only that the core has started. In the same browser, open a page that normally connects directly and one that’s failing, and check whether the new requests appear in the logs. If there are no request entries, check whether the browser uses the system proxy or TUN. If requests appear, use the outbound tag and error type to check for a routing mismatch, DNS resolution failure, or remote connection failure. If even a normally direct page won’t load after disconnecting, restore basic network connectivity first. During troubleshooting, use just one connection mode to avoid settings interfering with each other.

Why does the v2rayN system proxy work in my browser but not my terminal?

A browser may read the system proxy settings, or an extension or custom setting may override them. Terminal programs often use their own configuration or proxy environment variables, so a working browser doesn’t prove the terminal is connected. First check the local address and port currently set in the system settings, then confirm in v2rayN that the core is listening on that port. Next, check which proxy types the terminal program supports and where its settings apply. Some settings affect only the current session, and an already-open terminal may need to reload its configuration. Check the request logs after testing each app to see whether its traffic reached the core.

My subscription used to update but now fails. Should I delete the existing servers?

Keep the existing entries for now. A failed subscription update doesn’t mean all imported servers are unusable. Check the update result: if the request timed out, confirm that your network can reach the subscription service and whether the client tried to update directly or through an existing proxy. If access was denied, ask the provider whether the URL changed or the credentials expired. If content downloaded but couldn’t be parsed, check whether the subscription format changed. If you get a new URL, test it in a separate group first. Once the update succeeds and the new entries connect, you can remove the old group without losing a working comparison during troubleshooting.