v2rayNG First Connection: Choose a Node, Test Real-Connection Latency, and Verify Your Exit IP

A practical guide to choosing a node after importing a subscription, comparing real-connection tests with TCPing, and confirming traffic exits through the proxy.

At a glance

Seeing nodes in your subscription only confirms that the configuration was imported; a VPN icon in the status bar doesn't mean your browser is using the proxy. On your first v2rayNG connection, use a real-connection test to find a node that can reliably complete a request. Then start the VPN and compare your public IP in the same browser before and after connecting. If something fails, troubleshoot that layer rather than changing the node, routing, and network all at once.

First Connection: From Subscription List to VPN

These steps assume your v2rayNG home screen already shows nodes. v2rayNG uses the Xray core on Android, and the nodes in the list are connection profiles, not connection statuses. For testing, stick to either Wi-Fi or mobile data. If your device might switch between them automatically, first check which network is actually in use.

  1. Check the Node List

    Tap the subscription group tab on the home screen to open the group you just imported. If the list is empty, first make sure you selected the right group, then tap ⋮ in the top-right corner and choose Update subscription. If it’s still empty, check the subscription URL and response instead of repeatedly tapping the connect button.

  2. Run a Real-Connection Test

    On the home screen, tap ⋮ in the top-right corner, then Test all configurations (real connection). Some versions put this option in a submenu; look for “real connection” and don’t confuse it with TCPing. Wait for the results to refresh, then pick two candidates with successful results. Keep any one-off failures in mind and retest later.

  3. Select a Node

    Tap a candidate node’s row and confirm the selection indicator moves to it. Batch testing reports results for each profile; it won’t automatically switch to the node with the lowest latency. Note the selected node’s name so you know which connection you’re checking if verification fails later.

  4. Connect and Authorize

    Tap the connect button in the bottom-right corner. The first time you enable VPN mode, Android displays a connection request. Confirm that v2rayNG initiated it, then tap OK. If the VPN icon appears briefly and disappears, or the button immediately returns to the disconnected state, check Android Settings → Network & internet → VPN for another VPN that may be taking control. On some devices, you can find the VPN settings by searching for “VPN.”

  5. Check Your Current Exit IP

    After connecting, you can tap the connection test prompt at the bottom of the home screen to check whether the current connection can complete a test request. Then open a public IP lookup page in your usual browser. An in-app test and a browser check aren't the same: per-app proxy settings or routing rules may send them along different paths.

Real-Connection Latency vs. TCPing: Check Success Rate Before Milliseconds

TCPing checks whether a TCP connection can be made to the node’s address and port. It isn’t an ICMP Ping and doesn’t verify proxy authentication. A real-connection test attempts to use the node configuration to access a test URL, making it better suited to answering, “Can this profile forward a request?” The two timings cover different steps, so don’t compare them as if they were the same measurement.

Real-Connection Test

Recommended

Checks whether a node can complete a proxy request. Results depend on the protocol handshake, the remote network, and the test URL’s response. A successful test doesn’t mean every website is reachable or that the connection can handle video streaming.

Best for: Finding usable nodes when getting started and checking whether a profile can forward requests.

TCPing

Primarily checks whether the node’s TCP port is reachable. Even a quick response can be followed by failure during the TLS handshake, protocol authentication, or traffic forwarding. If the node doesn’t use a TCP entry point, this test can’t tell you whether the service is usable.

Best for: Telling whether the TCP entry point is unreachable or the proxy request fails after connecting.

3 runs
Suggested retests on the same network
180 ms
Example: median of three successful results
443
HTTPS default port—not the port used by every node

Example: Node A returns 165 ms, 180 ms, and 195 ms across three tests. Node B returns 90 ms once and times out twice. For your first connection, use A; don’t choose B based on a single low reading. These figures are illustrative only—not measured rankings or pass/fail thresholds.

Verify Your Exit IP: Compare Connected and Disconnected in the Same Browser

Your exit IP is the public address seen by the lookup service. It isn’t the local address shown in Android’s Wi-Fi details, and it may not match the server address in your subscription. To confirm that the proxy caused the change, keep the browser, lookup page, and network fixed; change only v2rayNG’s connection status. If your browser has its own proxy enabled, note that too so you don’t confuse two different traffic routes.

Baseline While Disconnected

Connection status
Stop v2rayNG and make sure no other VPN is taking over
Lookup conditions
Use the same browser, lookup page, and network
What to record
Public IPv4 or IPv6 address, and lookup time
Example result
192.0.2.24 (documentation example address)

If the baseline lookup fails, troubleshoot the basic network first. Don’t treat a blank result as an unchanged address.

Compare While Connected

Connection status
Connect to the selected node without changing Wi-Fi or mobile data
Lookup step
Reload the same lookup page to avoid an old screenshot or cached result
How to compare
Compare IPv4 with IPv4 and IPv6 with IPv6
Example result
198.51.100.38 (documentation example address)

Disconnect and check again. If the address returns to the baseline, that’s stronger evidence the connection caused the change.

A different address means the exit changed for that lookup request; it doesn’t prove every app uses the same exit. If the address hasn’t changed, first check whether the VPN is covering that browser, then check whether a routing rule sends the lookup domain directly. Lookup pages that support dual-stack connections may show IPv4 one time and IPv6 another, so those addresses can’t be compared directly. To verify a specific address family, run a separate check that explicitly reports it.

First Connection Problems: Troubleshoot by Symptom

TCPing returns a number, but why does the real-connection test still time out?

On the same network, try another node with the same test URL. If only one node fails, check the protocol, transport, and security settings in the original subscription profile first. Don’t change the transport or security settings just because the port is 443. If several nodes fail only with the same test URL, check whether that target is available before assuming the entire group of nodes is down.

The real-connection test passed. Why is my browser still showing the same IP?

First check the Android VPN screen to confirm v2rayNG is connected. Then open v2rayNG’s ⋮ → Settings and check whether per-app proxy is enabled, whether the list is set to proxy or bypass apps, and whether your browser is included. If the browser is covered, check whether the current routing preset sends the lookup domain directly. Change one setting at a time and run the lookup again.

The VPN icon is on, but no websites load. What should I check first?

Stop v2rayNG and try opening a website that normally works directly on your current network. If it still won’t load, check for a Wi-Fi sign-in page, mobile data availability, or system network settings. If it works while disconnected, reconnect to the node that passed the real-connection test, reproduce the issue, and check the client log. timeout only means a step timed out. If the log specifically reports a DNS resolution or TLS handshake failure, check the corresponding DNS or node security settings.

Wi-Fi works, but mobile data doesn’t. Do I need to reimport the subscription?

Not yet. Disconnect the VPN and confirm ordinary websites load over mobile data. Then rerun the real-connection test with the same node and start the VPN again. If it repeatedly fails only on mobile data, compare it with a second candidate node. Note the network, node, time, and exact error. Before sharing logs, redact the subscription URL, credentials, and full node configuration.

Connection Checklist: Test the Apps You Actually Use

For a first connection, the goal is to confirm that a specific app can reach its intended destination through this node on the current network—not that all traffic goes through the proxy. Repeat the same checks whenever you change networks, nodes, or routing presets.

Download the Client