← Back to blog

A ten-minute checklist when v2rayN will not connect

Check local network, profile, core, capture mode and target app in layers instead of changing DNS, routing and server parameters together.

Steps

  1. With v2rayN closed, verify ordinary internet access, correct system time and no leftover system proxy.
  2. Refresh the subscription, choose one known profile, run a TCP check and confirm the core actually starts.
  3. Test a browser through system proxy. If it works, isolate the original app; if not, inspect the first DNS or outbound error.
  4. Temporarily restore default DNS and routing. Add custom settings back one at a time after the minimal profile works.

Why this matters

Layered checks create a control case. Each step answers one question: is the network up, is the core running, is traffic captured, is the target reachable?

How to verify

You can reproduce failure by enabling one setting and recovery by disabling it, or demonstrate that the fault is server-side.

Things to watch

Do not begin by reinstalling Windows, disabling the firewall or downloading an old build. Preserve version and log evidence first.

Official references

v2rayN WikiFrequently asked questions