For when the client is running but your browser shows an error or keeps loading. This guide walks through v2rayN troubleshooting on Windows, with a comparison method for Android VPN apps. Change one setting at a time and retest the same URL to determine whether requests are missing the local proxy, the server is unreachable, or only certain domains are routed incorrectly.
System proxy: Are browser requests reaching the core?
A connected status usually means only that the local service or VPN session has started; it doesn’t prove that a webpage request successfully passed through the server. Pick one URL that fails and one HTTPS URL that normally works without a proxy. Test both in the same browser window and note the exact error and time. Don’t treat content already loaded in an old tab as proof that the connection is working.
Confirm the active server
In the v2rayN main window, right-click the server you want to test and select “Set as active server.” Confirm the name of the current server. Selecting a row or updating subscriptions does not switch the outbound server. Note the original active server so you can restore it after testing.
Check the system proxy
If TUN is not enabled, open the v2rayN tray menu and select “System proxy” → “Automatically configure system proxy.” In Windows, go to “Settings” → “Network & internet” → “Proxy” and check that the address and port under “Manual proxy setup” match the local proxy listener. Do not enter the remote server’s port.
Check where requests are going
Reload the failing URL and watch the v2rayN main window logs. If access logging is enabled, look for the destination domain at the same time. If there’s no matching entry, check whether the browser has its own proxy settings or a proxy extension. If access logging is disabled, an empty log does not prove the request missed the proxy.
Local port: listener, protocol, and actual requests
In v2rayN, go to “Settings” → “Parameter settings” and check the local listening port. Use the inbound protocol shown in the core startup log as the source of truth. Depending on the version and core, the client may use a mixed port or separate listeners. The example below uses 10808; replace it with a port that supports SOCKS before running the command.
Test-NetConnection 127.0.0.1 -Port 10808
curl.exe --proxy socks5h://127.0.0.1:10808 --noproxy "" --max-time 15 -I https://example.com/
The first command checks only whether a TCP port is listening in PowerShell. TcpTestSucceeded: True does not tell you whether the listener belongs to the current core or whether the remote server is reachable. The second command explicitly uses a SOCKS proxy and sends the destination domain through it. An HTTP response means the request passed through the local proxy listener, but you’ll need to check the routing rules to see whether it went through the proxy server or directly. If the example site rejects HEAD requests, remove -I and try again.
Takeaway: compare with an explicit proxy request first
If the explicit proxy request reaches the same URL but the browser doesn’t, check how the browser is being intercepted and which HTTP proxy it uses. Don’t switch servers yet: the two requests may not be using the same local listener.
Server and time: use logs to pinpoint the failure
Once the local port is working, reproduce the issue and find the destination address and underlying error for that request in the logs. First identify whether the error refers to 127.0.0.1, the server address, or the website you’re trying to reach. The same timeout message can call for different next steps depending on which address it names.
bind: address already in use
Cause and fix: The local listening address and port are already in use. Run Get-NetTCPConnection -State Listen -LocalPort 10808 in PowerShell to find the process, check OwningProcess, then close the duplicate instance or change the port and update the proxy settings to match.
connect: connection refused
Cause and fix: The destination refused the TCP connection. If it’s your local machine, check that the core started successfully. If it’s a remote server, verify the server address and port in your subscription. If you administer the server, check that its service is listening.
i/o timeout
Cause and fix: A read, write, or connection operation did not finish in time. Use nearby log entries to determine whether the timeout happened during dialing or the handshake, then compare against a known-working server on the same network. If only one server fails, troubleshoot that server rather than resetting the entire client.
x509: certificate has expired or is not yet valid
Cause and fix: The system time falls outside the certificate’s validity period. Sync your system clock first. If the error persists with the correct time, check the validity period of the certificate for the failing connection. Do not disable certificate verification.
In Windows, go to “Settings” → “Time & language” → “Date & time,” turn on “Set time automatically,” then select “Sync now.” Certificate checks use the system clock, not the time zone label shown in the interface. VMess authentication also requires the client and server clocks to be in sync. If only VMess servers keep failing after syncing, check the server time and authentication logs if you have server access.
DNS and routing: tell lookup failures from routing problems
- First, identify what’s being resolved. If the server address is a domain name, the core must resolve it before it can connect. A website’s domain, on the other hand, may be resolved by the browser, the operating system, the core, or the remote server. If the logs show that the server domain can’t be resolved, check the server address and its DNS resolution path first. Changing DNS settings for website domains won’t fix a failure to connect to the server.
- Compare with system DNS. Run
Resolve-DnsName example.comin PowerShell, then try again with the domain that’s actually failing. A successful result only confirms that Windows can resolve the domain through this DNS path; it doesn’t mean the browser’s secure DNS or the resolver configured in the core can do the same. If only one app fails, check its DNS and proxy settings first. - Check the actual outbound route. In v2rayN, go to “Settings” → “Routing settings” and check which rule set is active. If access logs show the outbound route, confirm whether the failing domain is going direct, through the proxy, or being blocked. Check whether an earlier, broader rule is matching before the rule for that domain. If the page redirects to another domain, check how the redirected request is routed too.
- Change one thing at a time. Note the current rule set and DNS settings. If changing a rule fixes the same URL, restore the original setting and test again to see whether the issue returns. Once the fix and failure reproduce consistently, update the specific rule and document the change. This helps avoid mistaking a temporary server issue for a configuration fix.
TUN and Android VPN: use only one interception method at a time
- Test the system proxy first on desktop. Turn off “Enable Tun” in the v2rayN main window and confirm the logs no longer show startup messages for that mode. Then select “Automatically configure system proxy” and retest the browser. If it works, the system proxy path is fine, so focus on the TUN path.
- Then test TUN on its own. In the tray menu, select “System proxy” → “Clear system proxy.” Confirm there are no leftover manual proxy settings before enabling TUN. Check the logs for virtual network adapter creation or route setup failures. If a managed VPN is already running, check your organization’s policy first; don’t force it off just to test.
- On Android, check which apps are included. A VPN icon in v2rayNG or v2flyNG only means Android has established a VPN connection. If just one browser can’t connect, open “Per-app proxy” under the client’s settings and check whether that browser is included or excluded, and whether reverse selection is enabled. Save your changes, disconnect and reconnect, then test again in the same browser.
Retesting and common questions
The latency test shows a result. Why won’t websites load?
A successful latency test only shows that the specific test target responded using that test method. Try an explicit proxy request to the URL that won’t load, then check the access logs. A latency result cannot replace checks of the browser’s proxy, destination DNS resolution, and routing.
Why can’t my browser connect after I close the client?
First, check Windows “Settings” → “Network & internet” → “Proxy.” If the manual proxy still points to a local port that is no longer listening, restart v2rayN and select “Clear system proxy,” or restore the proxy settings you noted before testing. On a managed device, restore the settings required by your organization’s policy.
The same server works on my phone but not my PC. What should I check?
Connect both devices to the same network and visit the same URL. If only the PC still fails, compare the results of an explicit proxy request and the browser on that PC. If both fail, compare the server settings, system time, and core logs. When sharing diagnostic details, include the exact error and when it occurred, but remove subscription URLs, credentials, and private domains.