These are connection and sync errors between the client and Vanguard or Riot's servers. Restarting and clearing the network path fixes most. Jump to your situation below or work through the methods in order.
VAN 0, VAN 1, VAN 6 and VAN -102 are connection and sync errors between the game client and Vanguard or Riot's servers. They usually come from an unstable internet connection, DNS problems, a firewall blocking the client, or a transient Riot server issue. The reliable fix is to restart everything and clear the network path: restart the Riot Client and your router, flush the DNS cache with ipconfig /flushdns, and make sure VALORANT and the Riot Client are allowed through the firewall. A quick check of Riot's service status rules out a server-side outage. Because these codes reflect the connection rather than your PC, restoring a clean, unblocked network path resolves the large majority.
VALORANT keeps a live connection to Vanguard and Riot's servers. VAN 0, 1, 6 and -102 mean that connection failed or fell out of sync, so the client could not talk to the platform when it needed to.
The causes are network-side: a flaky connection, DNS trouble, or a firewall in the way, and occasionally Riot's own servers. Restarting the client and router, flushing DNS, and allowing the game through the firewall restores a clean path and clears the error.
“The low VAN numbers, 0, 1, 6, -102, are all connection gremlins. The client could not reach Vanguard or Riot's servers cleanly. I restart the Riot Client and the router first, because that alone fixes it more often than people expect. Then I flush DNS with ipconfig /flushdns and make sure the firewall is letting VALORANT and the Riot Client through. And I glance at Riot's status page, because sometimes it genuinely is their servers, not you.”
ipconfig /flushdns
VAN 0, 1, 6 and -102 are connection errors. Restart the Riot Client and router, flush DNS with ipconfig /flushdns, and allow VALORANT and the Riot Client through the firewall. Check Riot's service status to rule out a server-side outage.
If the connection errors persist after restarts and DNS flush, resetting the Windows network stack (Winsock and TCP/IP) clears a corrupted network configuration that commonly underlies stubborn VAN connection codes. You can also submit your error to us for a tailored fix.
