CAPTCHAs protect websites from automated access, but validation often fails for reasons unrelated to what the user enters. Token expiration, conflicts with the browser cache, server-side verification failures: there are many possible causes. Here are seven practical ways to fix the problem, organized by issue type.
1. Reload the page to get a valid CAPTCHA token
An invalid CAPTCHA doesn’t always mean you entered the code incorrectly. Anti-bot systems set a validity period: if the page stays open too long before you submit the form, the token expires silently. No specific message warns you that it has expired.
The quickest fix is to reload the entire page (Ctrl + F5 on Windows, Cmd + Shift + R on macOS) to make the browser fetch a new token. Then fill out the form and submit it right away. This simple step resolves many issues, especially on government websites where reading the terms and conditions can take a while.
If you’re looking to fix an invalid CAPTCHA on Koatch, checking for an expired token is the first thing to do before trying any technical fixes.
2. Clear your browser’s cache and cookies
The cache stores outdated versions of scripts, including those that handle CAPTCHAs. A conflict between the cached version and the one expected by the server can cause repeated rejections, even when you enter the code correctly.
The steps vary by browser:
- In Chrome: Go to Settings, then Privacy and security, then Delete browsing data. Check “Cached images and files” and “Cookies”.
- In Firefox: Go to Settings, then Privacy & Security, then Cookies and Site Data, then Clear Data.
- In Edge: Go to Settings, then Privacy, then Choose what to clear.
After clearing the data, restart your browser and return to the form. An outdated cache is the second most common cause of invalid CAPTCHAs, after token expiration.
3. Try private browsing to identify extensions
Ad blockers, privacy extensions, and some password managers can interfere with CAPTCHA scripts. They may block requests to verification servers (Google’s for reCAPTCHA, Cloudflare’s for Turnstile) or modify the page’s DOM.
Opening a private browsing window disables most extensions by default. If the CAPTCHA works in private mode, an extension is causing the problem. Disable your extensions one at a time in your regular session to find the one blocking validation.
“Anti-fingerprinting” extensions are particularly suspect: they modify the data sent to the verification server, which can cause the assessment score used by reCAPTCHA v3 or Turnstile to fail.
4. Update your browser to the latest version
Modern CAPTCHAs use recent JavaScript APIs. An outdated browser may not run validation scripts correctly, causing a silent failure. The form appears to work, but the token generated is invalid on the server side.
Chrome, Firefox, and Edge update automatically, as long as you restart your browser regularly. A computer left in sleep mode for weeks can fall behind on updates. Check manually: in Chrome, go to “About Google Chrome”; in Firefox, go to “About Firefox”.
Keeping your browser up to date also fixes security vulnerabilities that can cause websites to trigger more aggressive CAPTCHA checks.
5. Tell apart ambiguous characters in visual CAPTCHAs
Text-entry CAPTCHAs are still used on many websites, and their main challenge is distinguishing between similar-looking characters. It’s not a matter of carelessness: some distorted fonts make the characters genuinely difficult to tell apart.
The most common mix-ups:
- Lowercase “l”, uppercase “I”, and the number “1” look almost identical in some fonts
- Uppercase “O” and “0” (zero) can sometimes be distinguished only by a slight diagonal line
- “5” and “S”, and “8” and “B”, can be hard to tell apart at low resolution
If you’re still unsure, use the CAPTCHA refresh button (often a circular arrow icon) to get a more readable combination. Getting a new CAPTCHA is faster than guessing an ambiguous character.
6. Check whether the problem is with the website itself
A CAPTCHA can be rejected even after you solve it correctly if server-side verification fails. The token sent by the browser must be validated by the website’s service: a configuration error, a token that has already been used, or a mismatch between the domain and the CAPTCHA API key can result in a rejection the user can’t fix.
There’s one telltale sign: the CAPTCHA fails every time, regardless of what you enter or which browser you use. If you’ve tried several browsers, cleared the cache, disabled extensions, and the issue persists, the problem is on the server side.
At that point, the only option is to contact the website’s support team or try again later. For French public services, the Services Publics+ page lists similar reports from users blocked by malfunctioning CAPTCHAs.
7. Switch networks or restart your internet router
CAPTCHA systems analyze your connection’s IP address. An address shared by many users (a corporate network, public Wi-Fi, or a consumer VPN) may be associated with a history of suspicious traffic. The CAPTCHA may then become more demanding or even reject every attempt.
Restarting your internet router often assigns a new IP address with most French internet service providers. If you’re using a VPN, temporarily turn it off: consumer VPN IP addresses are frequently flagged by anti-bot systems.
Switching from Wi-Fi to a mobile connection (using a hotspot) is also a quick way to check whether the network is the problem. If the CAPTCHA works on another network, the block is tied to your original IP address.
A CAPTCHA that doesn’t work is rarely caused by just one thing. An expired token, an outdated cache, or a misconfigured extension can be enough to cause a block. Trying these seven fixes in order can help you identify the problem in minutes, without any particular technical skills.
