PuppyIP Resource Center
Network & Connection Troubleshooting 8 min Published 2026-11-17

Windows v2rayN Shows -1 or Timeout but HTTPS Works: Check the Probe Path

In Windows v2rayN, -1 ms or Timeout means a check did not produce a displayed result. First send a real HTTPS request through the selected node to see whether live traffic is affected.

v2rayN troubleshooting -1 ms latency Timeout TUN real proxy traffic

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • Record v2rayN latency, a proxy-card Timeout, and a real web request separately; they may come from different probes.
  • Confirm the tested node, active node, and running core so a successful request through another node is not mistaken for a test result.
  • If SOCKS5 works but a TUN request fails, investigate the TUN path. If both work and only -1 remains, check probe compatibility.
  • The Legacy TUN Protection setting behaves differently across v2rayN versions and core topologies; it is not a universal switch.

First check whether real traffic fails

In v2rayN, -1 ms means the current latency check did not return a value to display. It is not a complete node-health result. Timeout can also mean that one measurement endpoint did not respond within its limit; it does not by itself prove that system proxy, TUN, or web traffic is failing.

Send a real HTTPS request through the node being diagnosed and confirm that the request used that node. If HTTPS succeeds while the interface still shows -1, focus on the probe path. If the request fails, trace the connection, core, DNS, and TUN path instead of dismissing a real failure as a display issue.

These interface indicators may measure different things

The current-latency status bar, a proxy-card Timeout, and download speed can use different checks. In a dual-core setup, sing-box may provide TUN and the Clash API while Xray handles the node connection, so a panel probe and a status-bar probe may pass through different cores.

If automatic panel refresh is off, a red Timeout can remain from an earlier check. Trigger that panel’s check again and record its time, then compare it with a real HTTPS request. Do not treat a stale result as a live measurement or latency milliseconds as download speed.

Confirm the tested node, core, and system-traffic path

Confirm that the node selected for testing is the node you intend to diagnose. The active node can differ from the node selected in a test list; a request through the default local port reports the active exit and does not replace an isolated test of the selected node.

Check which v2rayN, Xray, and sing-box processes are running, when they started, and how TUN is configured. With TUN enabled, test both the explicit local proxy and an HTTPS request without an explicit curl proxy. --noproxy bypasses curl’s proxy setting only; it does not bypass Windows TUN.

Compare the local proxy with a direct request

powershell
$Port = [int](Read-Host "Local SOCKS5 port")
curl.exe --proxy "socks5h://127.0.0.1:$Port" --connect-timeout 5 --max-time 15 https://example.com/
curl.exe --noproxy "*" --connect-timeout 5 --max-time 15 https://example.com/
These GET requests do not change Windows settings. The second request bypasses curl’s proxy setting, but an active TUN may still capture it. Replace the prompt with the port shown in your local client; do not paste a node address or credentials.

Read the running client processes

powershell
Get-Process v2rayN,xray,sing-box -ErrorAction SilentlyContinue | Select-Object Name,Id,StartTime
This reads process names, IDs, and start times. It does not stop or restart a core. Compare the result with the active node and the core topology shown by v2rayN.

Read probe results separately from proxy traffic

If explicit SOCKS5 works but HTTPS through TUN fails, the node and local proxy entry may work while the system-traffic path still needs diagnosis. If both explicit proxy and TUN requests work but the interface still shows an old Timeout or -1, record each probe time, selected node, and core log, then check how that v2rayN version performs its test.

If all real requests fail, compare the node-entry TCP connection, core logs, and a direct request from the same device. A direct curl request may still be captured by TUN, so treat local networking, node entry, core startup, and system traffic as separate boundaries.

Use Legacy TUN Protection only as a controlled comparison

The Legacy TUN Protection setting can improve one probe in a given v2rayN version and core topology, yet make another probe worse. Comparisons across versions and single- or dual-core setups have shown opposite directions, so there is no basis for always enabling or always disabling it.

Consider changing it only after real proxy traffic works, the remaining symptom is limited to -1 or a proxy-card Timeout, and you have recorded the v2rayN version, node core, TUN core, and single- or dual-core topology. Change only this setting, fully exit and reopen the client, then repeat the same request with the same node and destination.

Verify the result and keep useful evidence

After a change, record the new probe result separately from the real HTTPS result. Neither replaces the other. A repeatable change in the probe under otherwise identical conditions supports a version-specific connection to that check.

If the setting does not improve real traffic or the probe, do not keep switching cores, deleting drivers, or reinstalling the client. Keep the timestamp, versions, whether the tested node matched, real-request result, and relevant core logs, then return to the earliest failing path.

Sources

Frequently Asked Questions

Does -1 ms in v2rayN mean the node is down?

Not necessarily. It means the current check did not display a latency value. Send a real HTTPS request through the node before deciding whether the issue is the probe or the connection.

The panel says Timeout, but my browser works. Which result should I trust?

They describe different checks. Confirm whether the panel result is stale, and verify which node and core handled the real request.

Should I enable Legacy TUN Protection when only the speed test fails?

There is no universal setting. Record the version and core topology, then make a one-variable A/B change only when real traffic works and the probe alone is failing. Fully restart and retest.

Does curl --noproxy bypass Windows TUN?

No. It bypasses curl’s own proxy setting only. Windows TUN may still capture the request.