Get the build from the project
The authoritative source is the project's own repository and its release assets. Check the owner name, the release tag, the architecture and the checksum where one is published. A “portable optimised” build from a download aggregator is not the same software, even when the version string matches.
v2rayN has moved toward a cross-platform front end with a bundled core, and releases for Windows, Linux and macOS exist. Record which package you installed: it decides which core binary ships, and later errors are often core-version questions.
Three states, in order
| State | How to confirm | What it does not prove |
|---|---|---|
| A profile exists | The subscription parsed and produced entries | That any entry is selected as the active server |
| The core started | The core log shows a clean start with no field, file or port error | That Windows is using the local port |
| The local port is in use | The status bar shows the port, and a listening socket exists on it | That the node carries traffic |
Most “connected but no internet” reports fail at the second state while the interface looks healthy. The log is the only place that tells you.
Import the subscription
- Copy the subscription address from the provider's panel, not from a marketing page.
- Add it through the subscription entry, then update it explicitly.
- Confirm the node count is plausible, and that the update reported no error.
- Select a node and set it as the active server.
- Check the core log for this start.
If the update reports success and the list is empty, the fetch worked and something else did not: check what the address returned, whether the profile is active, and whether an override removed entries.
System proxy first, TUN second
The system proxy writes a local port into Windows settings. Applications that read those settings use it; many do not. TUN captures at the IP stack and covers more, at the cost of an adapter, routes, DNS handling and a service installation.
Start with the system proxy because it has fewer variables and is simpler to reverse. Enable TUN when a specific application — a game, a CLI tool, a store app — ignores the system proxy.
Before enabling TUN, record the current DNS settings, the routing table and whether another VPN is running. If TUN breaks connectivity, disable it first and confirm plain networking before changing anything else.
When it fails, use the first error
| First error | Where to look |
|---|---|
| Failed to run Core | The line above it: port in use, rejected config field, or a missing Geo file |
| Failed to import subscription content | Whether the fetch succeeded, then the response encoding and format |
| Address already in use | Which process listens on the local port |
| ArgumentOutOfRange on update | An empty or unexpected body, not a dead node |
Each of those has a separate guide on this site; they are not interchangeable, and the first line decides which one applies.
Verifying the connection
- Send one HTTPS request through the local port and confirm it returns.
- Observe the exit address and compare it against two independent sources if region matters.
- Check the core log for that request, if the log level shows connections.
- Record the time and the versions, so a later comparison is possible.
Scope
This page describes setup and verification. Interface names change between releases, and the core and client are versioned separately. Nothing here evaluates any provider or promises that a particular configuration works on your network.