Directions · VFS errors

VFS Global error codes

The question worth answering first is not what the code says — it is whether the restriction is on your account or on your connection. That decides whether changing network helps or wastes your afternoon.

All codes at a glance

CodeVFS wordingRestrictsHow long
429201Permission IssueYour VFS accountAround two hours, then it clears on its own.
429202Account LockedYour VFS accountIndefinite. It does not lift on a timer the way a rate limit does.
429001Access Restricted for User IDYour VFS accountLonger than a rate limit; frequently needs VFS support.
403201Access restricted, unusual activityYour internet connectionUsually lifted within an hour.
403102Permission IssuesYour internet connectionUsually short — often under an hour.
403203Permission Issues (variant)Not clearly documentedUsually transient.
403206Session expired or invalidThis browser sessionImmediate. Signing in again clears it.
401UnauthorisedThis browser sessionImmediate.

Why the distinction matters

Account-level codes (429201, 429202, 429001) follow your login. Switching to mobile data, opening a private window or using a different laptop reaches the same restricted account and changes nothing. Waiting, or contacting VFS, is the only route through.

Connection-level codes (403201, 403102) are the opposite. Your account is untouched — VFS has stopped accepting requests from the address you are on, often because a VPN or a shared office network put you behind an address other people were also hammering. Here, changing connection is exactly the right move.

Session codes (403206, 401) are not restrictions at all. Sign in again and carry on.

Do not read these codes by their first three digits.403201 and 403102 are connection blocks; 403203 shares their wording and does not behave like one. 429201 is a two-hour pause, while 429202 is an account lock that does not lift on a timer. Grouping them by prefix is the most common mistake made about them, and it leads people to abandon a perfectly good account or connection.

Where this comes from

We watch VFS appointment calendars for a living, across several countries and over hundreds of thousands of checks. These distinctions — which code restricts what, how long each lasts, which ones are safe to wait out — come from that, not from repeating what other pages say.

What we deliberately do not publish is anything only useful for automating around these limits. That would not help you get an appointment, and it is not what this page is for.

The problem underneath

Nearly everyone who hits these codes hit them the same way: refreshing an appointment page for weeks. The limits exist because of that behaviour, and the behaviour rarely works — openings are rare and arrive at no predictable hour.

See the routes we cover