This article is for users who have installed v2rayN or v2rayNG and are experiencing the "connected but pages won't open" issue. Troubleshoot in this order: nodes → time → DNS → system proxy → routing rules. Each layer has verification methods and specific fixes, so you can complete a full fault diagnosis on your own after reading.
First, Understand What "Connected" Really Means
The client showing connected only means the kernel process is running and the node handshake succeeded. Whether browser traffic actually enters the proxy channel depends on whether system proxy or TUN mode has taken over. Many people see the green status and skip the check, only to find the traffic never went through the proxy.
If any link in this chain breaks, the symptom is "connected but no internet." Start troubleshooting from the node, the most likely culprit, and work inward.
Layer 1: Node Availability and Latency
Node availability is the most common failure point. First check the latency test results on the client's main screen, then switch nodes to verify. In v2rayN, right-click a node and select "Test Real Connection Latency" to distinguish between "TCP handshake succeeded but HTTP fails" cases; in v2rayNG, use the latency test button in the top-right corner of the main screen.
Error: failed to find an available destination
Cause & Fix: Outbound server address resolution failed — check the node address spelling, change DNS, then restart the kernel.
Error: connection refused
Cause & Fix: Node port is blocked or the server isn't listening — switch to a different node; don't keep retrying the same one.
| Latency | Status | Recommended Action |
|---|---|---|
| < 100 ms | Usable | Use normally |
| 100–300 ms | Usable but slow | Usable, but video/download experience is affected |
| > 300 ms | High latency | Switch nodes, or choose a route closer to the target region |
| Timeout | Unavailable | Switch nodes immediately, no need to wait |
Layer 2: System Time Sync
Node handshakes rely on TLS certificate verification. If the system time deviates from real time by more than 5 minutes, certificate verification fails, showing as "connects then immediately disconnects" or "connects but pages won't open." Manually sync the time first, then reconnect to the node.
| System | Sync Command | Notes |
|---|---|---|
| Windows | w32tm /resync | Run Command Prompt as administrator |
| macOS | sudo sntp -sS time.apple.com | Requires internet; local time will be forcibly corrected |
| Linux | sudo timedatectl set-ntp true | Enables systemd-timesyncd for automatic sync |
| Android | Settings → System → Date & time → Automatic | Once enabled, the system syncs time from the network automatically |
Windows users who get an error from w32tm /resync can run net start w32time first to start the time service, then sync.
Layer 3: DNS Resolution and Proxy DNS
If pages still won't open after the node is fine and time is synced, the next common cause is DNS resolution. The V2Ray kernel's DNS configuration determines whether domain resolution goes local or remote. In v2rayN, open Settings → Parameter Settings → DNS Settings, check "Enable DNS Server", and enter a remote DNS address.
"dns": {
"servers": [
"8.8.8.8",
"1.1.1.1"
],
"queryStrategy": "UseIP"
}If you're using the "Bypass Mainland China" routing rule, you also need to confirm the split logic between "Remote DNS" and "Local DNS"; otherwise you may see "ping works but browser resolution fails." Use nslookup google.com to verify the resolution result. If it returns 8.8.8.8 but the browser still won't open, the problem is likely in system proxy rather than DNS.
Conclusion: Test DNS Before Touching Routing
If resolution times out, adjust DNS settings first; if resolution is normal but pages won't open, skip DNS and check system proxy and routing rules directly.
Layer 4: System Proxy and Browser Proxy
v2rayN listens on port 10808 (SOCKS) and port 10809 (HTTP) by default. When system proxy is enabled, browser requests go through these two ports. If system proxy is not enabled, traffic goes direct, showing as "node connected but pages won't open." Windows system proxy path: Settings → Network & Internet → Proxy, confirm "Use a proxy server" is enabled.
Enable System Proxy
Right-click the tray icon in v2rayN's main screen → "Enable System Proxy". When the status changes to "Clear System Proxy", it's enabled.
Check Port Configuration
Settings → Parameter Settings → Local Listening, confirm the SOCKS port is 10808 and the HTTP port is 10809.
Verify Port Connectivity
Enter
http://127.0.0.1:10809in the browser address bar. If the proxy home page appears, the port is working.Clear Browser Proxy Extensions
If extensions like SwitchyOmega are fixed to SOCKS5, they must match v2rayN's ports; otherwise traffic is taken over by the extension and still goes direct.
Layer 5: Routing Rules and Traffic Splitting
Routing rules determine which traffic goes through the proxy and which goes direct. If the rules are wrong, you may see "sites in mainland China open but sites outside China don't" or "all traffic goes through the proxy but the node itself is slow." v2rayN's default rule is "Bypass Mainland China", meaning mainland China IPs and domains go direct and everything else goes through the proxy.
- Settings → Parameter Settings → Routing Settings, view the current rule group.
- Confirm whether the "Bypass Mainland China" rule was accidentally changed to "Global".
- Check whether
domain:google.comwas mistakenly added to direct in custom rules. - After modifying rules, right-click the tray icon → "Restart Kernel" to apply the configuration.
Conclusion: Check Rules Before Adjusting Splitting
If "sites in mainland China open instantly but sites outside China all time out", switch the rule back to "Bypass Mainland China" and restart the kernel; if it still doesn't work, use process of elimination to remove custom rules one by one.
Quick FAQ
Subscription update fails with a timeout?
Connect to any available node first, then check "Update via Proxy" in subscription settings and retry.
Connected but pages won't open?
Check whether system proxy is enabled, then check the core log for port-in-use errors.
Sites in mainland China open, but sites outside China all time out?
The routing rule was changed to "Bypass Mainland China" and the node itself is unreachable. Switch nodes first, then confirm no outside-China domains were added to the direct list.
Latency is very low but download speed is only a few dozen KB?
The node's bandwidth is throttled or shared by many users. Switch to a non-oversold node, or use a v2flyNG node with the Xray kernel.
Proxy automatically fails after restart?
v2rayN's "Start on Boot" and "System Proxy" need to be checked together; otherwise the kernel starts after restart but the proxy doesn't take over.
Download a Client and Troubleshoot with This Checklist
Both v2rayN and v2rayNG support the node, DNS, and routing configuration options covered in this article. v2flyNG is suitable for Android users who need the v2fly kernel.