On screen: Connection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 68
This one genuinely goes both ways, so the first job is telling which you are looking at.
No incidents reported. Maintenance is announced for later — see the schedule
Riot maintains two registries whose numbers overlap, and 68 appears in both. VAN codes belong to Vanguard, the anti-cheat. VAL codes belong to the game. They are not the same error.
VAN 68, in Riot's current article, is Vanguard losing the connection or session it needs while starting or during play. That is on your machine.
VAL 68, in Riot's Valorant list, is CapEntitlementsFetchError — the game cannot fetch the content you own. That is on Riot's side.
Almost every page covering this number picks one meaning and presents it as the only one. That is how people end up rebuilding firewall rules for a problem on Riot's servers.
Here is the test, and it takes a second. If your skins and agents have vanished but the game is playable, it is the entitlements branch — VAL 68, Riot's side, wait it out. If the game will not start or throws you out, it is the Vanguard branch — VAN 68, your side, work the list below.
Operator documentation: support.riotgames.com. The Valorant code list, which documents the VAL 68 meaning, currently carries a banner from Riot saying it is out of date. We are reporting both meanings because the game can print either, and saying so is more useful than picking one.
Riot maintains two registries whose numbers overlap, and 68 appears in both. VAN codes belong to Vanguard, the anti-cheat. VAL codes belong to the game. They are not the same error.
This one genuinely goes both ways, so the first job is telling which you are looking at.
Start with: Reboot the PC. Riot's own first step for the Vanguard branch.