V2Ray Connected but No Internet? Check Proxy, DNS, and Routing

If the client says connected but websites won't load, check the system proxy, local port, DNS, routing rules, and browser extensions.

At a glance

Using v2rayN on Windows as an example, test the same failing URL step by step: check whether the browser sends requests to the local proxy, whether the proxy receives them, where the hostname is resolved, and which outbound route the request takes. Change one setting at a time, and keep a rollback path.

First, identify what “connected” actually means

Browser requestLocal inboundRoute matchOutbound connectionSite response

This flow describes a single web request using system proxy mode; it does not mean DNS always happens at a fixed stage. A connected status or successful node test does not prove that the browser used the same entry point or that the current domain matched the same outbound route. Conversely, if the system proxy still points to a client that has exited, the browser may fail before it ever reaches a node.

  • Note the failing URL and the time. Then try a site you've already confirmed can be reached directly to tell a single-site issue from a broader outage. Don't test by submitting information on a sign-in page.
  • Record the current node, routing profile, system proxy mode, and TUN status. The steps below cover system proxy mode; enabling TUN at the same time changes the traffic path. Record its status, then test each mode separately.
  • If direct access is allowed, temporarily clear the system proxy set by the client, then open a known-good site normally. If direct access also fails, first rule out a disconnected network, a Wi-Fi sign-in page, or an upstream network issue. On organization-managed devices, don't override a managed proxy without permission.

Check the system proxy and local listening port

The system proxy is a setting that individual apps may choose to follow; it does not route all traffic from the device. The menus below refer to the v2rayN 7.x interface on Windows. Menu locations or field names may differ between minor versions; use the current configuration and startup logs to confirm the actual listener values.

127.0.0.1
Example loopback address
10808
Example mixed inbound port
15 seconds
Maximum total timeout for the commands below
  1. Note the inbound port

    In v2rayN, open “Settings” → “Parameter Settings” and check the local listening port. If you're using a custom configuration, confirm the actual inbound address, port, and protocol in the core startup logs. Don't enter the remote node port as the system proxy port.

  2. Set the system proxy

    Right-click the v2rayN tray icon and select “System Proxy” → “Automatically configure system proxy.” In Windows 11, go to “Settings” → “Network & internet” → “Proxy” and check the current address and port. Also check whether an existing setup script is still enabled.

  3. Check the local listener

    Run the first command below in PowerShell. If TcpTestSucceeded is False, check whether the core started successfully. If it's True, the port accepted a TCP connection—but that doesn't confirm the expected core is listening.

  4. Specify the proxy explicitly

    Run the second command to bypass the browser's proxy selection and test the local HTTP proxy directly. Use it only if the port supports HTTP or mixed inbound. If your port differs from the example, replace it in both commands.

Test-NetConnection -ComputerName 127.0.0.1 -Port 10808
curl.exe -v --max-time 15 --proxy http://127.0.0.1:10808 https://example.com/

If the command succeeds but the browser fails, the test URL is reachable through this entry point; that doesn't prove every route is working. Test the same failing URL again, then compare the browser settings. If the local listener check fails, start with the startup logs. If the port is already in use, identify the process using it before changing the local port and reapplying the system proxy. Don't terminate an unfamiliar process.

Tell system, browser, and core DNS apart

A browser connecting directly, a browser using Secure DNS, and a core handling requests by domain name may follow different DNS resolution paths. In particular, when HTTPS uses an HTTP proxy to establish a CONNECT tunnel, the browser can pass the destination hostname to the proxy. Resolving the domain locally doesn't mean the proxy can resolve it too.

  • In PowerShell, run Resolve-DnsName example.com -Type A to see whether a local lookup returns an address. For troubleshooting, replace the hostname with the one from the failing URL—omit the scheme, port, and path. This result is not a substitute for the core DNS logs.
  • If the core logs explicitly report a lookup failure, first determine whether the failed lookup was for the node hostname or the website hostname. A node hostname may need to resolve before the outbound connection can be established. If that lookup depends on an outbound connection that isn't up yet, startup can stall.
  • If only one browser fails, check its Secure DNS settings. If device policies allow, temporarily restore the default and compare; then restore the original setting. Don't change both system and core resolvers at once, or you won't know which change made a difference.

net::ERR_NAME_NOT_RESOLVED

Cause and fix: The browser reports a name resolution failure, but that message alone doesn't identify which resolver failed. Compare a local lookup, the browser's settings, and core logs from the same time. Adjust settings only after pinpointing the failing stage.

curl: (28) Operation timed out

Cause and fix: The request didn't finish within the allotted time, which doesn't necessarily mean DNS failed. Check where the detailed output stops: connecting to the local proxy, waiting for a CONNECT response, or handshaking after the tunnel is established. Then check logs for that stage.

Check which outbound route the request actually takes

In the v2rayN main window, check the selected option under “Routing,” then reproduce the issue once. If access logging is enabled in the configuration, use the timestamp and destination hostname to check the outbound tag. Receiving a connection at the inbound, selecting an outbound route, and successfully connecting through it are three separate things. Missing log entries alone don't prove the request never arrived; first confirm that access logging is enabled.

Observed resultNext step
A request that should use the proxy goes directCheck whether a broader direct rule appears before the domain-specific rule, and whether the inbound received a hostname or an IP address.
The request matches a block outboundCheck whether the blocking rule is meant to cover this domain, and whether the failure affects the main page or a domain used by one of its resources.
The request matches the expected proxy outbound but failsCheck outbound errors from the same time. If the logs show a handshake failure, verify the node's transport settings and your device's clock; there's no need to keep changing the system proxy.

With Xray routing rules, a request usually uses the first matching rule in order. Keep a copy of the current profile and change just one rule at a time. If the home page loads but images or sign-in content don't, use the browser developer tools’ Network panel to identify the domain for each failed request. Don't assume every resource request belongs to the main domain in the address bar.

Rule out browser extensions and stale proxy settings

If the same URL works with an explicit proxy command but fails in the browser, check how that browser selects a proxy. Proxy-switching extensions, browser-specific connection settings, and organization policies can all prevent it from using the system proxy you just configured.

  • In Edge, open edge://extensions/, temporarily disable extensions that can manage proxies, and try again. You can also compare with a temporary profile that has no extensions installed; an InPrivate window doesn't necessarily disable every extension.
  • In Firefox, go to “Settings” → “General” → “Network Settings” → “Settings” and confirm the expected mode is selected. Manual proxy settings and using the system proxy are separate options; an old setting may still point to a different port.
  • If internet access fails only after you exit v2rayN, use the tray menu “System Proxy” → “Clear system proxy” before exiting to remove the setting applied this time. Then check whether Windows still points to a local listener that's no longer running. If you had an organization proxy or setup script before, restore its original values rather than disabling it outright.
Client downloads